What to Do First When Every Client Says It’s Urgent

When several clients say their work is urgent, first ask when each result will actually be used and what is waiting for it. Compare those answers with your existing promises and the time you have available. Then confirm a sequence you can deliver. If the requests cannot all fit, propose a specific change in scope or timing and get agreement from whoever it affects.

You can make this decision from the messages and calendar already in front of you. You do not need to build a priority matrix before answering a client.

Clarify the request before making a new promise

“Urgent” may mean a meeting starts at noon, a colleague cannot continue, or the client would simply like the work soon. Ask for the missing detail without dismissing the request:

When do you need to use this, and what needs to happen with it? I’ll check the work involved and confirm when I can deliver.

If you need time to investigate, say when you will come back with an answer. Acknowledging a request does not require promising immediate completion. Equally, an unclear deadline is a question to resolve; it does not prove the work can wait.

Put the competing requests beside each other

For each request, identify three things:

• The needed-by time: when will someone use the result, and what delivery have you already agreed?

• What waits without it: a handoff, a decision, another person’s work, or something that can be rescheduled?

• The work still required: what would make the result usable, how long do you estimate that will take, and are the necessary inputs ready?

Use the actual work time left after meetings and other commitments. Include checks and handoff in your estimate. A request that sounds small may involve a file search, a review, and another export before it is ready to send.

A worked example: three requests, one morning

Imagine a fictional freelance designer with a three-hour work block from 9 a.m. to noon and a booked afternoon commitment. At the planning point below, the necessary files are ready and the estimates include checking and sending the result:

• Supplier files: two hours to prepare final brochure exports, already promised for a confirmed 3 p.m. supplier handoff today.

• Presentation: two hours to polish the full deck. The client has marked it urgent but has not said when it will be used.

• Asset question: 15 minutes to check and answer a specific question. A collaborator is ready to continue today once the answer arrives.

Before committing to the presentation, the designer asks about its use time. The client confirms a 3 p.m. meeting tomorrow and agrees to delivery tomorrow morning. The designer checks that a two-hour block is available then.

Today’s plan can now be: answer the asset question from 9 to 9:15, then prepare the supplier files from 9:15 to 11:15. That is two hours and 15 minutes of work within the three-hour block. The presentation has an agreed place tomorrow.

Answering the short question first makes sense here because it releases someone who is ready to work and still leaves time for the existing handoff. It is not a rule to finish every small request first. If the answer required an hour of investigation, or the supplier needed files earlier, the sequence would need another check. The remaining 45 minutes also do not guarantee that the estimates will hold.

What changes if the presentation is needed at noon today?

Change one fact in that same example: the presentation client confirms a fixed noon meeting today. The full requests now need four hours and 15 minutes before the designer’s noon stop. Three hours are available. Changing their order cannot make all that work fit.

The useful question becomes what can change. Suppose the client confirms that two priority slides would be enough for the meeting, and the designer checks that those slides can be prepared and sent in 30 minutes. This smaller deliverable needs explicit agreement; the designer cannot quietly substitute it for the full deck.

With that agreement, one possible schedule is:

• 9–9:15: answer the asset question.

• 9:15–9:45: prepare and send the two agreed slides.

• 9:45–11:45: finish and send the supplier files.

The work totals two hours and 45 minutes. That fits the stated estimates, with only 15 minutes left. Agree a separate delivery for the remaining presentation work before treating that part as scheduled.

If the client needs the complete deck, the smaller version is not an answer. Contact the people whose commitments would be affected and discuss a realistic change. Until a change is agreed, the conflict remains; moving an item on your own calendar does not resolve it.

Offer a clear choice without exposing another client’s work

Explain your capacity and the proposed result. You can do that without naming other clients or sharing their project details:

I can prepare the two priority slides by 9:45 for your noon meeting. The full deck needs about two hours, which does not fit alongside work already committed this morning. Would those slides meet the immediate need? If so, let’s also agree a delivery for the rest.

Only offer times and alternatives you have checked. If two fixed commitments still collide, say that you cannot currently confirm both and identify the decision needed next. Avoid accepting every request while hoping one deadline will disappear.

This reflects a narrow principle in Atlassian’s project trade-off guidance: discuss what can change and revisit the decision when new information changes the priorities. The example here is an illustration, not a guarantee that a particular order will work for every client.

Keep the agreement easy to find

Record the result, the agreed delivery, and any condition attached to it where you already keep the work. If the decision is still pending, retain the time you promised to return with an answer. For help keeping that promise visible, use this routine for remembering client follow-ups.

If the same collisions keep appearing, use your next weekly review to compare upcoming commitments with available time before accepting another delivery.