The optional workshop invite is a yes at 4:50 p.m., which is when most optional yeses get typed. Late-afternoon fatigue, a desire to appear cooperative, and eagerness to wrap up the workday make even overloaded workers commit to tasks they’ll groan about when their alarm goes off the next morning. These reversible yeses—commitments you can back out of without material harm to a team or customer—often slip through capacity checks because they feel low-stakes in the moment. Internal tracking of knowledge work workflows from Find Core Insight finds these impulsive late-day yeses eat up 10 to 15 unplanned work hours a month for the average individual contributor, with zero measurable impact on performance reviews or promotion outcomes.
Same-day yeses you will regret after sleep
The most common impulsive yeses fall into a narrow set of categories that almost never deliver on their initial perceived value. These include last-minute networking mixers hosted by people you have no ongoing professional relationship with, optional cross-departmental brainstorming sessions for projects outside your core remit, extra work tasks offered by colleagues who are swamped but have no authority to reassign work to you, guest speaking slots for small, unvetted audiences that require 4+ hours of prep for no career benefit, and beta testing requests for tools your team has no formal plans to adopt. All of these feel good to agree to in the moment, as you get a small hit of satisfaction from being helpful or sought after. But when you wake up the next day and review your existing commitments, you’ll often realize you already have a client deadline that week, a medical appointment during the mixer, and zero extra capacity to take on uncompensated, unrecognized work. Most people who send same-day yeses end up either bailing on the commitment last minute, which erodes trust, or pushing their own core work to later dates, which increases their stress levels for weeks.
A cooling slip: hold, send, or shrink the yes
The 24-hour cooling slip is a simple, actionable template you can use the second you receive an optional request, to avoid shooting off an impulsive yes before you assess your capacity and priorities. It standardizes your reply process, removes the pressure to respond immediately, and gives you time to evaluate the request when you are rested and focused. The full slip with send, hold, and shrink rules is below:
| Step | Action Rule | Hold Condition | Send Condition | Shrink Condition |
|---|---|---|---|---|
| 1 (0-1 hour after request receipt) | Send a neutral holding reply to the requester: “Thanks for sending this over! I’m reviewing my current capacity and will get back to you by EOD tomorrow.” | No holding reply needed if you already have conflicting high-priority work explicitly logged on your shared calendar | Send the holding reply only if you have no obvious conflicting commitments already scheduled | N/A for this step |
| 2 (12 hours after receipt, ideally first thing next workday) | Review the request against your documented core quarterly priorities and existing committed time blocks | Mark as a no if the request does not align with at least one core priority, or would require cutting time from a previously committed task | Flag for a confirmed yes if it aligns with a core priority and fits fully into open, unassigned time blocks | Flag for adjustment if it aligns with a core priority but requires more time than you have available to allocate |
| 3 (22-24 hours after receipt) | Send final response to the requester | Send a polite no: “Thanks again for thinking of me! I don’t have the bandwidth to contribute to this right now, but I’d love to be considered for similar opportunities in the future.” (No reply is only acceptable for unsolicited cold outreach from people you have no professional relationship with) | Send a confirmed yes: “I have capacity to take this on, and I’ll follow up with next steps by [specific date].” | Send a modified yes: “I don’t have time to take on the full request, but I can [specific small contribution, e.g. review the 2-page draft for 15 minutes this week] if that would help.” |
You can save this slip as a note in your task manager, or create a canned email reply for the holding message, to cut down on manual work when you receive requests.
Holds that become silent noes
A common concern people have when using the cooling slip is that delaying their reply will come off as rude, or that the requester will fill the spot before they get back to them. If a requester fills the role or spot in less than 24 hours, that is not a loss for you—it means the request was low-stakes enough that they did not need you specifically to fill it, and you would have been a last-minute filler contributing no unique value anyway. Silent noes, where you do not reply to the request at all, are only acceptable for unsolicited cold outreach, such as random requests to speak at unvetted events or promote third-party products you have no interest in. For all requests from colleagues, managers, or people you have an existing professional relationship with, you should always send the polite no outlined in the slip, even if you are declining the request. This is far more respectful than saying yes and bailing last minute, which is the default behavior for most people who regret impulsive same-day yeses. Example timing: if a colleague sends you a request to join their optional brainstorm on Wednesday at 3pm on Monday afternoon, you can send the holding reply on Monday, check your calendar on Tuesday morning, see you have a scheduled performance review during that time, and send the polite no on Tuesday afternoon, well before the event.
Using the slip on optional work only
The cooling slip is explicitly designed for optional work only, and should never be used for required work that is part of your formal role responsibilities. Required work includes any task assigned to you by your direct manager, any work tied to a customer commitment you or your team have already made, and any mandatory training or meetings outlined in your job description. Optional work is any request that you have no formal obligation to accept, and for which there are no material professional consequences for declining. To run a quick check, ask yourself: would I receive formal negative feedback in my performance review for declining this request? If the answer is yes, the request is not optional, and the cooling slip does not apply. If the answer is no, the request is eligible for the 24-hour hold. Using the slip for required work will delay critical tasks, create unnecessary friction with your team, and lead to negative performance outcomes, so it is critical to draw a clear line between optional and required work before you apply the slip rules.
Customer outages this slip must not delay
Any request tied to an active customer outage, a customer escalation, or a time-sensitive customer commitment that requires your specific input is explicitly exempt from the cooling slip rule. These requests have material consequences for both your team and the customer if you delay replying, so you need to respond immediately, even if that means saying no to other optional work later. Illustrative example: if you get a request at 4:55pm to join a call for a customer whose entire product instance is down, you do not use the cooling slip—you join the call immediately, because a 24-hour delay would mean the customer is without service for a full day, which could lead to them canceling their contract, and your team would have to handle far more fallout in the long run. Note that non-time-sensitive customer requests, such as a customer asking if you can do a 30-minute optional training for their team next month, are eligible for the cooling slip, as there is no immediate harm in waiting 24 hours to reply.
Save a copy of the cooling slip to your desktop or pin it to your team’s shared workflow doc, so you can pull it up the second you get an optional request you’re tempted to agree to immediately. You’ll cut down on unplanned low-value work without damaging professional relationships, and free up hours each month for the work that actually moves the needle for your role and long-term goals.