The mug is still hot at 9:01 and the calendar already shows a “quick question” over the first deep hour. You tap the calendar event, see it’s from a teammate who regularly extends 10-minute asks to 45, and your jaw tightens before you remember you prepped for this exact scenario last night. Your chat tab glows faintly in the background, already piling with unread messages you promised yourself you wouldn’t check until 11. The notebook open to your focus block priorities sits directly under your mouse, so you don’t have to hunt for what you’re actually supposed to be doing right now.
Map the two valid responses to unplanned pre-block requests
You don’t waste time brainstorming new ways to handle the request, because you already have both acceptable options printed on a laminated sticky note stuck to the bottom of your monitor, so they’re always in view when you log on. The first option is to shift the request to your scheduled 11:05 am check-in window, the 15-minute slot you reserve every single weekday for unplanned non-urgent asks from teammates, clients, and stakeholders. The second option is to use the 10-minute pre-block buffer you intentionally built into your schedule from 8:50 to 9:00 am for time-sensitive requests that genuinely can’t wait two full hours. You have a hard rule that you never take time out of the core 9 to 11 focus block for unplanned asks, so these are the only two choices you ever have to weigh when a request lands right before or during your deep work time. This eliminates the decision fatigue that usually leads you to cave and take the meeting just to avoid awkward conversations.
Sort the request by its actual impact on other people’s work
You don’t make the call based on how urgent the sender makes the request sound, or how guilty their message makes you feel; you run it through three simple, pre-defined checks to sort it into the right response bucket. First, ask if the request blocks anyone else from completing their own scheduled work before 11 am. Second, ask if the request is tied to a hard deadline that lands before the end of the workday today. Third, ask if delaying the response would cause material harm to a project, client, or teammate that can’t be mitigated with a 2-hour wait. If all three of these are no, you use option one and shift the request to your 11:05 am window. If any of the three are yes, you use option two and address it during your remaining pre-block buffer time if you have it left, or flag it for your pre-defined backup teammate if the request lands mid-block. For the calendar request you just opened, the quick question is about feedback on a report draft that isn’t due until Friday, no one is blocked waiting on your input to move forward with their own work, so you know immediately which option to pick.
Document the choice and send your response in 60 seconds or less
You keep a single table on the first page of your work notebook to log all unplanned requests that hit your focus block, so you can track patterns over time and adjust your process as needed. You also have pre-written responses saved to your keyboard shortcuts, so you don’t have to type out a new message every single time a request comes in.
| Request type | Response to send | Log note for your records |
|---|---|---|
| Non-urgent, no blocked work before 11 am | “Got this! I’m in a focused work block until 11 am, and I’ll respond to you first during my 11:05 check-in window. Let me know if this genuinely can’t wait that long and I’ll loop back earlier.” | Scheduled for 11:05 check-in, no action needed until then |
| Time-sensitive, blocks other work before 11 am | “Got this, I have 10 minutes right now to address this before my focused work block starts. Let’s hop on a quick call or I’ll send a full response by 9 am.” | Addressed pre-block, no core focus time lost |
| Time-sensitive, arrives mid-block | “I’m in focused work until 11 am, I can address this right at 11 or hand it off to [teammate name] right now if that works better for your timeline.” | Escalated to backup if needed, scheduled for 11 if no escalation requested |
You pull up the pre-written response for non-urgent asks, paste it into the calendar event comment thread, and jot the log note in your table in 20 seconds flat. You take 10 extra seconds to confirm your chat do-not-disturb setting is turned on, which auto-responds with the same 11 am check-in note, so anyone who pings you for the next two hours gets the same message without you having to lift a finger. You close the calendar tab, move your mouse back to the open project you planned to work on, and take a sip of your still-warm coffee before you dive in, no guilt lingering.
Adjust your process when you spot a misaligned request response
Three days later, you’re flipping through your request log during your weekly 15-minute admin check-in, and you notice that the quick question you moved to 11:05 am ended up requiring a 20-minute fix that pushed back your team’s shared deadline by half a day. You dig into the details and realize you didn’t know the teammate was waiting on your input to run a time-sensitive data pull that only works before 1 pm each day, even though the final report deadline is Friday. That’s the only sign you need that your sorting criteria missed a key detail for that specific ask. The small fix is easy: you add a fourth check to your sorting list, confirming if the request ties to a time-sensitive process that only runs during specific daily or weekly windows, even if the overall deadline is later in the week. You add that line to your monitor sticky note right after you spot the issue, so you don’t miss that detail again. You don’t beat yourself up for the misstep, you don’t throw out your entire focus block plan, you just update your criteria and move on, no guilt attached. If a request ever does break through your focus block on a given day, you don’t abandon the rest of the week’s blocks, you just log the misstep in your table, adjust your criteria if needed, and reset the block for the next morning.
Prep your focus block defense before you log off for the day
You run through this quick 5-minute routine every evening before you close your laptop, so you never walk into work and slip into reactive mode by 9:10 am the next day. First, you double check that your 9 to 11 am focus block is marked as busy on your shared calendar, with a note in the description that unplanned asks will be addressed at 11:05 am unless they are genuinely urgent. Second, you confirm that your chat auto-responder is set to turn on automatically at 8:55 am every weekday, so you don’t have to remember to toggle it on when you get to your desk. Third, you jot down your top two priorities for the next morning’s focus block on the first page of your notebook, so you have a clear reminder of what you’re protecting that time for if you feel guilty when someone pings you “got a sec” during the block. If you need help aligning your focus block priorities with your team’s shared goals, you can find prompts to walk through that exercise on Find Core Insight. You don’t overcomplicate the routine, you just make sure all the pieces are in place the night before, so when you sit down with your hot coffee the next morning, you can dive straight into your work instead of fighting off last minute requests before you even get started.