Acknowledge the new preference
ManyRequests documents client queue prioritization. Treat a client’s rearrangement as useful information about what matters now. It does not by itself establish that an already-started job can stop without consequences. Confirm which work is affected before promising a new delivery sequence. Clients usually want clarity, not a lecture about the board, so explain the practical effect in terms of the deliverables they recognize.
Compare the two unfinished jobs
For example, a campaign graphic may already be awaiting final review when a new sales deck becomes urgent. Finishing the graphic could release a slot quickly, while stopping it might leave a nearly complete asset unresolved. Ask which deadline is fixed and what material is ready. The sensible order depends on actual remaining work rather than simply on the newest message or the position of a card in a list.
Record the accepted tradeoff
A useful note might read: “We will pause deck polishing to complete the event banner; the deck review moves to the newly agreed date.” This is an illustrative communication template, not a claim about automatic scheduling. Preserve the previous commitment and the reason it changed. Avoid deleting an earlier due date without explanation, because the client and a backup teammate may otherwise see different versions of the agreement.
Check the handoff after reordering
Make sure the assigned person, request status and client-facing update tell the same story. A reordered queue with an unchanged producer brief can cause the wrong work to continue. Keep the original request identity and related files together. If the new priority cannot fit the service, state the available choices honestly: wait, reduce scope or discuss a separately agreed arrangement. Do not imply that changing software settings creates additional human capacity.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests request queue — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19