When Every Request Says Urgent: A Two-Day Filter for a Full Diary

In many UK offices, the problem is not a shortage of requests but their timing. A Tuesday morning email can arrive with the word urgent in the subject line, a meeting invite can appear for the same afternoon, and a colleague can ask for 'a quick favour' that quietly consumes half a day. None of these requests is necessarily unreasonable. The difficulty is that they arrive while the week is already full, and the fastest responder often becomes the default route for every new piece of work.

The 48-hour request rule is a way out of that pattern. It is not a policy of ignoring people, and it is not an excuse to sit on a decision. It is a short, defensible triage window that lets you establish the facts before you commit capacity. Used properly, it protects your existing deadlines, gives requesters a clear answer date, and reduces the chance that you become the bottleneck you were trying to avoid.

Why a full week needs a filter, not a faster yes

When a diary is already committed, speed of response is not the same as good service. A quick yes to every new ask creates three problems. First, it hides the trade-off: the new work has to come from somewhere, usually from an existing deadline, a review step, or the end of the day. Second, it trains colleagues to route work through you because you are responsive, not because you are the right owner. Third, it makes your committed work less visible. If the calendar is full but the commitment log is not, people will assume there is room.

A triage window does not remove urgency. It separates genuine urgency from polite but movable asks. A regulatory filing, a safety issue, a payroll deadline, or a contractual obligation may need immediate attention. A request to review a document that is not due until Friday, or to join a planning call that could happen next week, usually does not. The rule gives you time to tell the difference and to say so clearly.

The 48-hour request rule in practice

When a new request arrives, acknowledge it within one working day. Do not commit to delivery in that first reply. Instead, record the request and state when the requester will hear your decision. The window is for triage, not delay. If the request is a genuine emergency, escalate it immediately through the agreed route rather than waiting for the two-day point.

A simple holding reply is enough: 'Thank you for flagging this. I am checking capacity against existing commitments and will confirm by Wednesday at 11am.' That message does three things. It acknowledges the request, it sets an expectation, and it buys the time needed to make a considered decision rather than a reactive one.

A decision tree for yes, no, and not yet

Use the following questions in order. Stop as soon as the answer is clear.

• Is there a legal, regulatory, safety, or financial control deadline that requires action today? If yes, escalate through the urgent route and record who is handling it.
• Does the request require your specific authority, knowledge, or sign-off? If no, route it to the capable owner and tell the requester who has it.
• Can the request wait until after your current critical path is complete? If yes, give a specific decision date or start date and mark it as not yet.
• Does saying yes displace a committed deadline or a promised deliverable? If yes, state the trade-off and ask the requester to choose which commitment moves.
• Is the request small enough to absorb without affecting any committed deadline? If yes, say yes with a clear completion time and log it.

This tree produces four outcomes: yes, no, not yet, and escalate. The important discipline is that yes must always include the trade-off. If there is no trade-off to state, the request is probably small enough to absorb. If there is a trade-off, the requester should see it.

Scripts that keep the relationship intact

For a not-yet decision: 'I can take this on, but not before Monday 16 November. If that date does not work, please tell me what deadline you are working to and I will see whether a shorter piece can be done sooner.'

For a no: 'This is not something I can take on this week without moving the year-end report, which is committed for Friday. The earliest I could start is 23 November. If that is too late, the best route is to speak to Priya, who has the same authority to approve this.'

For a yes with a trade-off: 'I can turn this around by Thursday, but that means the supplier review moves to Monday. Please confirm that is acceptable before I rebook the review.'

For an escalation: 'I am treating this as urgent because it affects the payroll run. I have alerted the finance team and will confirm the action plan by 2pm today.'

Formal but human language works best in UK workplaces. Avoid phrases such as 'I will try' or 'leave it with me' unless you also give a date. Vague reassurance is what creates the bottleneck, because it keeps the request open and the requester dependent on you.

Log commitments so existing deadlines stay visible

A triage rule only works if your existing commitments are visible. Keep a simple commitment log with seven fields: request, requester, date received, true deadline, estimated effort, impact on existing work, and decision or next action. Review it at the start and end of each working day. A spreadsheet is sufficient; a shared planner or project board is better if others need to see it.

The log does two jobs. It stops new requests from disappearing into email, and it gives you evidence when a week is full. When a colleague asks for something, you can see immediately whether it displaces a committed deliverable. When your manager asks why a deadline slipped, you can show the trade-offs that were made. At the end of the week, publish a short capacity note to the people who rely on you: what is committed, what is at risk, and when new work can be accepted.

The 48-hour rule is not about becoming slower. It is about becoming deliberate. A busy week can absorb new work, but only if the cost is stated and the existing deadlines remain in view. That is how you protect delivery without becoming the person every request has to pass through.