When a customer asks, “Can you have this by Friday?”, it is tempting to give the most hopeful answer. But a target is not the same as a confirmed delivery date, and guessing can leave both sides planning around a promise you cannot keep. A better response is still useful: say what is known, identify who will verify the schedule, and give the customer a specific time when you will update them. That next update is a commitment you can control; the delivery date may not be.
The useful bits
- Label estimates and targets clearly; call a date confirmed only after the schedule owner verifies it.
- Name the person or role responsible for checking dependencies and capacity.
- Give a specific time for your next update, without implying the work will be delivered by then.
Separate the date you hope for from the date you can stand behind
Start by describing the status of the date, not just the date itself. A target is a planning aim: the team is working toward it, but dependencies or capacity may still change the timing. A confirmed date means the person responsible for the schedule has checked the relevant work and is prepared to communicate that date as current. If that check has not happened, do not present the target as settled.
Be precise about uncertainty. “We are targeting Friday, but I have not confirmed that date” is clearer than “It should be ready Friday.” If you do not yet have a useful estimate, say that directly rather than inventing one. You can explain what remains unknown without listing every internal complication.
Find the person who can verify the schedule
The person replying to the customer may not own delivery planning. Identify the individual or role that can check the work’s status, dependencies, and available capacity—for example, the project lead or the team responsible for the next step. Assign one person to obtain and relay the answer, even if that person needs input from others.
Ask a focused question: “Can you confirm whether Friday is a committed date, and what dependency could change it?” This is more useful than asking a group for a general update. If no schedule owner is clear, say who will find the right contact and by when. Do not imply that checking has happened until you have the answer.
Offer an update time you can control
Choose a specific checkpoint for your next message, such as a day and time with the relevant time zone. Pick a time that gives the schedule owner a reasonable opportunity to respond and gives you time to contact the customer. The checkpoint is a promise to communicate, not a promise that the delivery date will be settled or that the work will be finished.
If the check is still underway at the checkpoint, send the update anyway. Explain what has been verified, what is still open, and when you will check again. Avoid leaving the customer to chase you, and do not quietly move the update time without telling them.
Make the reply useful without overexplaining
A strong response has four parts: acknowledge the question, state the current status, name who is checking, and give the next update time. If the customer needs to make their own plans, invite them to share the decision they are waiting on. That may help you understand what information matters most, but it does not make an uncertain date more certain.
Keep internal uncertainty factual and brief. You might mention that a dependency still needs confirmation, but avoid blaming another person or presenting an unverified explanation as fact. If there is a confirmed alternative, explain it as an option only if it is genuinely available.
Subject: Timing for [work item]\n\nHi [Customer name],\n\nWe are targeting [target date] for [work item], but I cannot confirm that date yet. [Schedule owner or role] is checking [specific dependency or schedule question]. I will update you by [day, time, time zone], even if the timing is still being checked. That update will not mean the work is complete; I will distinguish any confirmed date from a planning target.\n\nIf you are making a decision based on this timing, please tell me what you need to plan around.\n\nBest,\n[Your name]
If the date changes, reset expectations clearly
When the schedule owner responds, report the date’s status accurately. If a date is confirmed, state who or what has confirmed it and whether it refers to completion, handoff, or another milestone. These are not interchangeable. If the original target is no longer realistic, say so plainly and provide a replacement only when it has been checked.
If you still cannot confirm a delivery date, do not turn a revised guess into a new promise. Tell the customer what remains unresolved and set another specific update checkpoint. A short, timely status message is more dependable than silence while waiting for a perfect answer.
Check that the communication loop is closed
Before sending, verify that your wording labels the date as a target or confirmed date, names the schedule owner or the person finding one, and includes a specific next update time. Then check the calendar and time zone, and make sure the update task has an owner. After sending, confirm that the message went to the intended customer and record the checkpoint where your team will see it.
The loop is closed when the customer has received the update you committed to—not necessarily when the delivery date is confirmed. If the checkpoint arrives without an answer, send the promised status, explain the remaining uncertainty, and set the next checkpoint. That keeps your communication reliable without claiming control over a schedule you do not control.
- Before replying: target or confirmed? Schedule owner identified? Update time and time zone stated?
- At the checkpoint: send the update even if the delivery date remains unconfirmed.
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