You promised a short information leaflet by Wednesday afternoon. The approved transport details have not arrived, and checking the final text will take longer than you planned. “Could I have a bit more time?” tells the recipient that something is wrong, but gives them little to plan around. A concrete proposal explains the state of the work, names a revised delivery and shows what the other person can do while the decision is being made.
Check the remaining work before proposing a date
List what is complete, what remains and what depends on someone else. The leaflet’s introduction and layout may be ready, while the transport section needs confirmed information and the whole document still needs proofreading. Separate work you can continue from work that is genuinely blocked. Waiting for transport details does not prevent you from checking the contact names already approved. Use this inventory to estimate a new delivery, including the final review rather than promising to send the moment you finish typing.
Check whether your proposed date relies on an uncertain input. “Thursday at noon, provided the details arrive by Wednesday at four” is a conditional proposal, not a firm guarantee. State the condition clearly and offer a check-in if it is missed. If you cannot estimate responsibly yet, propose a specific time when you will provide an updated plan. Do not select an early-looking date only to make the request easier to accept; another missed promise creates another planning problem.
Find out what the current deadline supports
The recipient may need Wednesday’s file to book printing or obtain approval before an event. Ask which part of that sequence is fixed and whether partial work helps. You may already know the printer’s confirmed submission time; if not, do not assume it. Your revised delivery has to be assessed against the recipient’s real next step. An extra day that seems small to you may remove their review time or make the planned printing unavailable.
Consider alternatives that you can actually deliver. One option is a complete, checked leaflet on Thursday at noon. Another may be Wednesday’s checked text without the transport section, clearly labelled for review, followed by a final version once the information is approved. A partial document is useful only if its status and limitations are clear. Do not put invented transport details in it or call it ready for printing. If the missing section is essential to approval, say that partial delivery may not solve the problem.
Write a short request with a usable choice
A request might say: “The introduction and layout are complete. The transport section still needs approved details, and I need time to check the final file. May we move delivery of the checked file from Wednesday afternoon to Thursday at noon? That estimate assumes the details arrive by Wednesday at four. I can send the checked sections on Wednesday for review if that helps. Please let me know whether either option fits the printing schedule.” The message names the current state, proposed change, dependency and practical alternative.
Give the necessary reason without turning the request into a long defence. If your estimate was too short, acknowledge that directly. You can protect private information while still explaining the operational consequence: “I am unavailable this afternoon, so the review cannot be completed today.” The recipient needs enough information to assess the proposal, not every detail of your circumstances. When a problem becomes known early enough to affect planning, raise it then rather than waiting until the original deadline has already passed.
Treat the proposal as pending until it is agreed
Send the request through the channel used for the work and ask for a response by a useful point when necessary. A sent message does not change the agreement. Continue the work that remains feasible, and avoid telling other people that Thursday is confirmed before the authorised recipient accepts it. If you do not receive a reply, follow the agreed contact route and flag the uncertainty. Do not interpret silence as permission or mark the task complete simply because you made the request.
If the answer is no, ask which available option best protects the required result. That might mean reducing the agreed scope, involving another qualified person or reporting that the full deliverable cannot responsibly be completed at the original time. Scope changes and new contributors need the appropriate agreement; you cannot solve the deadline by secretly omitting required checks. Describe the trade-off accurately so the person responsible can decide. Sometimes no acceptable change is available, and the limitation still needs to be communicated plainly.
Confirm both the new delivery and its consequences
Once a decision is made, record the exact date, time, deliverable and any remaining condition. Confirm who will review it and whether another handover or booking must change. Update the calendar while preserving a record of the agreement where the work requires one. If the input later misses the condition, raise that at the promised check-in. A useful deadline request does more than ask for relief: it creates a plan the affected people can understand, approve and use.
