THE DIRECT ANSWER

When two or more requests compete for the same hours, list each one’s remaining effort, its deadline, and the hours you actually have before that deadline. Test whether any order finishes all of them. If none does, take one comparison to the person who can rank both requests instead of telling each requester their work comes first. Prioritizing is an explicit, recorded decision about what waits; it is not a quiet choice to drop something.

Count the hours before each deadline, not only in total

A total can look nearly sufficient while the order still fails. Write each request with its remaining effort, its deadline, and the person who owns it. Then count the working hours you can actually use before each deadline, after existing commitments. Use remaining effort rather than the original estimate once work has started.

In the fictional example on this page, you have eight focused hours before Thursday 13:00: four on Wednesday afternoon (13:00–17:00) and four on Thursday morning (09:00–13:00). Thursday afternoon is an existing workshop you cannot move. Rana needs a proposal revision for a client call at Thursday 10:00: four hours of rewriting plus a one-hour pricing check, five hours in total. Tomas needs a vendor summary for a finance cutoff at Thursday 13:00: three hours of summary plus a one-hour reconciliation, four hours in total. Nine hours of work meet eight hours of capacity.

  • Proposal first: it uses all of Wednesday afternoon and 09:00–10:00 on Thursday, so it is ready for the call. The summary then has 10:00–13:00, three of its four hours, and misses the cutoff by one hour.
  • Summary first: it is finished on Wednesday, but the proposal has one hour before the 10:00 call and needs five.
  • No order finishes both. The one-hour gap is a capacity fact, not a sign that anyone is working too slowly.

Ask each owner for the minimum usable outcome

Before ranking, ask each requester what must be usable at their deadline. You are not asking them to justify urgency; you are checking whether the full estimate is what the event actually needs. A pricing section that the client will discuss is different from a fully rewritten document the client will never see during the call.

Keep the answers with their owners. Rana can change what the proposal must contain for the call. Tomas can describe what finance needs, but the finance cutoff may not be movable. You can clarify, but you cannot shrink either request on your own.

  • What must be usable at your deadline, and by whom?
  • Which part could follow later without affecting that event?
  • Who else would need to agree to a smaller version?

Take one comparison to the person who owns both priorities

Two requesters can each reasonably believe their work comes first. If you negotiate with them separately, you can end up making two incompatible promises. Bring the comparison to the person who can decide across both requests, in the example Mei, the team lead. Share the effort, the deadlines, and the gap; share confidential content only if it is needed for the decision.

Make the request narrow: which request gives up the missing hour, or which other change Mei can authorize. Sequencing your own work toward the earliest deadline is usually within your authority, and you can say that you are doing it. That sequencing does not settle which request is reduced or delayed, so do not present it as the decision.

Replay: one changed condition, one message to send now

Change one fact and keep the rest. Mei, who ranks both requests, puts the vendor summary first. The summary takes all of Wednesday afternoon, 13:00–17:00, and is ready well before Tomas’s 13:00 finance cutoff. The proposal now has one hour before Rana’s 10:00 call, Thursday 09:00–10:00, and it needs five. Four of its five hours will not be ready for the call.

Do not quietly squeeze five hours of work into one or hope the call slips. Tell Rana now, while Rana still has options: “Mei ranked the summary first. By 10:00 I’ll have 1 of the 5 hours. Move the call, or present the current version?” What happens with the call is Rana’s decision, not yours; you only sequence your own work. Whatever Rana chooses, record where the remaining proposal hours go rather than letting them disappear.

Adjust the queue to your role

Employees usually need a manager or project owner to rank work from different requesters. Freelancers working for two separate clients may have no shared owner; in that case you own your own capacity, so offer each client a date or scope you can actually keep rather than promising both the earliest slot. People working across several roles should keep one honest capacity view, even if each client or employer sees only the part relevant to them.

Revisit the queue when an estimate changes materially, a dependency fails, or new work arrives. Report the change against the agreed order instead of reshuffling after every new message.

AUTHORED FICTIONAL EXAMPLE

A conversation you can rehearse

Authored fictional example, not one of the playable cases. You have eight focused hours before Thursday 13:00. Rana needs a five-hour proposal revision for a Thursday 10:00 client call. Tomas needs a four-hour vendor summary for a Thursday 13:00 finance cutoff. Mei, the team lead, sets priority across both. Rana and Tomas each know only their own request.

A first reaction

To Rana: “Yes, it will be ready for your call.” An hour later, to Tomas: “Sure, you will have it before the cutoff.”

A more specific response

To Mei: “Rana’s proposal needs five hours and Tomas’s vendor summary needs four; I have eight before Thursday 13:00. The proposal has to come first to be ready for the 10:00 call, which leaves three of the summary’s four hours before the finance cutoff. Can you decide which gives way: the summary’s reconciliation hour, a smaller proposal for the call if Rana agrees, or another change you can authorize? I am starting the proposal now because its deadline is earlier; that does not settle which request loses the hour.”

The better message makes one person responsible for one visible conflict. It counts hours against each deadline, offers options without choosing on anyone’s behalf, and separates your own sequencing from the priority decision.

Before you act

  • List each request with remaining effort, deadline, and owner.
  • Count your usable hours before each deadline.
  • Test the possible orders before promising either one.
  • Ask each owner for the minimum usable outcome.
  • Bring one comparison to the person who owns both priorities.
  • Record what waits, who decided, and tell both requesters.

Common questions

What if every stakeholder says their work is first?

Put the requests in one short comparison with effort, deadlines, and the gap, and bring it to the shared manager or project owner. Ask for a ranked decision. Continue only work that is compatible with the eventual choice, and do not promise first place to everyone.

What if nobody owns both requests?

Ask each requester who resolves conflicts between their work and other commitments. If there is genuinely no shared owner, as with two separate clients, the capacity decision is yours: offer each a date or scope you can keep, and tell them before the conflict becomes a missed deadline.

Should I tell one requester about the other’s work?

Share what the decision needs: that another commitment uses the same hours, how many hours each needs, and when. Leave out confidential content. The aim is a feasible queue, not a comparison of whose work matters more.

Original practice guidance with an authored fictional example that is not one of the playable cases. Estimates are stipulated for the exercise. Priority authority varies by workplace and agreement. This guide is general practice material, not legal advice.

Source basis: an original scenario-based practice framework. The example is fictional, and no external research finding or measured effectiveness is claimed. Read the editorial method.