A deadline that says “by Friday afternoon” can mean different things to people reading from different places. Even a precise time may be unclear if the time zone is missing or the date changes for someone elsewhere. Make the request easy to act on by naming the calendar date, clock time and time zone, then stating how much response time you are allowing. A little care also helps you avoid setting a deadline that lands outside a recipient’s normal working hours. Here is a practical way to write one and check that it is clear.
The useful bits
- Write the weekday, full date, clock time and named time zone together.
- Check the deadline against recipients’ local working hours and the time available to respond.
- Ask for a specific action by the deadline and confirm the date and time are unambiguous.
Start with the decision you need
Before choosing a deadline, identify exactly what recipients must do: approve a draft, send figures, or confirm availability. Then decide how much time that action reasonably requires. A quick confirmation may need less time than reviewing a document or gathering information from colleagues.
Separate the response deadline from any later event. “Please send comments by [date and time] so I can revise the proposal before [meeting or delivery date]” tells readers both what you need and why the timing matters. Avoid making people infer whether the deadline is for an initial reply or a completed decision.
Put the date and time zone in the same sentence
Use a weekday, the full calendar date, a clock time and a named time zone. For example: “Please send your approval by Thursday, January 14, 2027, at 3:00 p.m. GMT.” Naming the zone is more useful than writing only “3 p.m.” or relying on an abbreviation such as “ET,” which can be interpreted differently or shift with daylight saving time.
If recipients are in several locations, include a second local equivalent when you can verify it for that specific date. Label each time clearly and keep one time zone as the authoritative deadline. Do not assume a location’s offset stays the same throughout the year; daylight saving transitions can make a familiar conversion wrong. When uncertain, use a reliable calendar or time-zone converter and check the date as well as the hour.
Make the working-hours check
Think about the deadline from the recipient’s local perspective, not just your own. A time near the end of your day could fall overnight for someone elsewhere. Where possible, choose a time that falls within ordinary working hours for the people whose response you need, and allow for reasonable time to read, discuss and reply.
When schedules or locations are unknown, avoid treating an after-hours deadline as routine. Offer an earlier option, ask what timing works, or explain why the timing is constrained. If a recipient is not expected to work in your time zone, say whether a response at the start of their next working day is acceptable. A clear request is more useful than an urgent-sounding message with no explanation.
State the response window plainly
Tell recipients when the clock starts and what to do if they cannot meet the deadline. If you are sending the email on Tuesday, “Please reply by Thursday at 3:00 p.m. GMT” leaves the calendar dates visible; “within two days” may be unclear if the message is read later or crosses a weekend. For a response window that depends on when someone receives the message, specify whether you mean business days and whose local working calendar applies.
Give a simple fallback: ask recipients to flag a conflict by an earlier point, suggest a workable alternative, or send a partial response if that would help. Do not imply that silence means approval unless that is an agreed process. If the deadline is flexible, say so; if it is fixed, explain the consequence without exaggerating it.
A message you can adapt
For a small group in two locations, show the main deadline and a checked local equivalent. The example below uses a January date, when GMT is UTC+0 and Eastern Standard Time is UTC−5. The times match for that date; confirm any conversion for your actual deadline before sending.
Keep the request concise, but include enough context that a reader can act without replying just to ask which date or time you meant. Replace the bracketed fields with the real task, contact details and verified deadline. Do not leave brackets in the message you send.
Subject: Approval requested by Thursday, January 14 Hi [Name], Please review [document or decision] and reply with your approval or requested changes by Thursday, January 14, 2027, at 3:00 p.m. GMT (10:00 a.m. Eastern Standard Time). That gives us time to [next step] before [event or delivery date]. If you cannot respond by then, please let me know by Wednesday, January 13, at [time and time zone] and suggest when you can reply. Thanks, [Your name] [fictional.name@example.com]
Confirm before sending
Read the draft as if you were a recipient in each location. Check that the weekday matches the date, every clock time has a time zone, and the local equivalent is correct for that date. Confirm that the requested action and the response deadline are unmistakable, and that the available window is reasonable for the task.
A final checklist: Is the deadline within or considerate of recipients’ working hours? Is it clear whether you need a reply, approval or completed work? Have you said what to do if someone needs more time? After sending, check the message in your sent mail and make sure the date, time-zone labels and recipient list appear as intended. If someone asks for clarification, answer directly and restate the deadline with the full date, time and zone.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction