How to Tell a Truly Urgent Request from Someone Else’s Urgency
When someone says “I need this now,” pause long enough to check what happens if you wait. A request is genuinely urgent when a real deadline or near-term consequence makes delay costly. A forceful message, repeated follow-ups, or an unexpected request may call for a quick reply, but they do not by themselves establish that the work must come first. Ask for the deadline, the consequence of missing it, and what your current work would have to give way to.
What makes a request genuinely urgent?
Urgency comes from the situation around a task, not from the volume or speed of the request. Look for a specific deadline, a time-sensitive dependency, or a consequence that will occur if nobody acts soon. For example, a colleague may need your approval before a scheduled meeting begins; a supplier may need a decision today to keep a delivery date. In each case, the clock matters because something concrete changes when it runs out.
By contrast, “ASAP,” “quickly,” and “this is a priority” are incomplete information. They tell you how the sender feels about the request, but not when it is due or what delay would affect. The distinction is useful in project work, too: Atlassian’s deadline-management guidance recommends considering urgency, impact, competing priorities, and dependencies when deciding what comes first. [Atlassian’s guide to deadline management](https://www.atlassian.com/agile/project-management/deadline-management)
Urgent and important are also different questions. A request can be important but have room for careful scheduling; another can be time-sensitive but have little lasting impact. Check both before you reorder your day.
Use a three-question check before changing priorities
When a request arrives with pressure attached, get the facts in this order:
1. **What is the actual deadline?** Ask for a date and time, or the event that sets the cutoff. “Today” may mean before lunch, before close of business, or simply sometime soon to the sender.
2. **What changes if it is late?** Identify the person, deliverable, or next step affected. A real dependency is more informative than a general statement that the work is important.
3. **What should move to make room?** Compare the new request with your existing commitments. If the requester wants it first, ask which current task can wait and who needs to know about that change.
These questions do not assume the requester is exaggerating. They turn a vague demand into a decision that both people can understand. They also reveal when urgency is real but the proposed timing is not feasible.
A practical decision path
Use this short sequence when you need to decide what to do next:
**There is a near deadline and a concrete consequence.** Check whether you are the person who can prevent that consequence. If so, handle the smallest action that protects the deadline, then confirm what happens to your other work.
**There is a real deadline, but it is not immediate.** Put the work against your calendar and current commitments. Agree on a start time or delivery time rather than treating every reminder as a fresh emergency.
**No deadline or consequence is clear.** Ask for both before interrupting your current task. If the requester cannot supply them, offer a reasonable time when you can review it.
**Two valid deadlines collide.** Make the conflict visible to the people who own those commitments. Do not silently accept both as top priority; ask them to choose the order or reduce the scope.
This is a decision aid, not a universal ranking system. A deadline imposed by an external event may matter more than a flexible internal target, but context can change the answer. For work with dependencies, check what other people are waiting on and whether a brief handoff or partial answer would keep their work moving. Atlassian’s guidance similarly calls out task dependencies and the need to consider competing priorities when setting realistic timelines. [Deadline management: dependencies and competing priorities](https://www.atlassian.com/agile/project-management/deadline-management)
What to say when someone is pressing you
A useful response is short, neutral, and specific. It acknowledges the request without agreeing to a deadline you have not checked.
“What time do you need this, and what is waiting on it?”
“I can take this on today. Which of my current deadlines should move?”
“I’m finishing the report due at 2. I can look at your request at 2:30 unless the cutoff is earlier.”
“I can send the key figures now and the full review tomorrow. Would that keep your next step on track?”
If the requester says everything is urgent, ask them to name the first consequence that will occur and the latest useful time to act. This gently replaces urgency labels with information. If they do not know, agree on a check-in or a realistic response time instead of letting repeated messages set your schedule.
Example: a last-minute request beside a fixed commitment
Imagine you are preparing a presentation due to a client at 3 p.m. A teammate messages at 1:30: “Can you review my slides ASAP? They’re urgent.” Before dropping the presentation, ask when the slides must be ready and what depends on your review. If the teammate has a 2 p.m. meeting and needs only three figures checked, a ten-minute review may prevent a real delay. If the slides are for next week and “ASAP” means the teammate would simply prefer feedback today, the client deadline probably stays first.
If both deliverables truly need attention by 3, state the trade-off plainly: “I have the client presentation due at 3. I can review the slides now, but that will delay the presentation. Which commitment should take priority?” This makes the capacity limit visible and gives the people responsible for the commitments a chance to decide. The example is illustrative; the right choice depends on the actual deadline, impact, and authority to change either commitment.
When urgency is real but you cannot take the work
A real deadline does not automatically make you available. Be clear about what you can do, what you cannot do, and what decision is needed. Offer a smaller contribution if it helps: a quick status, a key fact, or a handoff to someone available. If another task must slip, tell its owner early and agree on a revised expectation. Do not promise two incompatible delivery times just to end a tense exchange.
When the same person regularly labels requests urgent, keep returning to the same questions: deadline, consequence, and displaced work. Patterns may become clearer over time, but each request still deserves a concrete check. The aim is not to judge someone’s motives. It is to make a sound choice with the information available.
The quick test
Before reacting to pressure, ask: **What is due, what happens if it waits, and what moves if I do it now?** A specific answer to those questions is evidence of urgency. A louder message alone is not. Once you know the deadline and the trade-off, you can respond quickly when speed matters—and set a clear boundary when it does not.
Sources: [Atlassian’s deadline management guide](https://www.atlassian.com/agile/project-management/deadline-management) discusses urgency, impact, dependencies and competing priorities; [Asana’s task prioritization guide](https://asana.com/resources/how-prioritize-tasks-work) discusses due dates, dependencies and communicating delays; and [PMI’s article on conflicting expectations](https://www.pmi.org/learning/library/managing-conflicting-expectations-6893) describes making stakeholder conflicts visible and reconciling them. The decision questions and scenarios here are an editorial aid, not a formal standard.