A customer says, “Please hold off while we get internal approval.” That sounds simple, but a vague pause can leave both sides unsure whether work has stopped, what decision is pending, or whether the original deadline still applies. A useful response turns the request into a shared record: what is paused, what approval or information will restart it, and what happens to the schedule meanwhile. Keep the tone neutral and make it easy for the customer to correct your understanding. Do not treat silence as approval or quietly revise a deadline on their behalf.
The useful bits
- Confirm the exact work being paused and that the pause is at the customer’s request.
- Name the approval or information needed to restart, and who should provide it if known.
- State whether the current deadline remains tentative, needs review, or is unchanged by agreement.
Confirm the pause in concrete terms
Acknowledge the request and identify the specific task, deliverable, or next step that will stop. If the request concerns only one part of a larger project, say which work will continue and which will wait. “We’ll pause the draft review” is clearer than “We’ll put this on hold,” especially when several items are in progress.
Record that the pause is being made at the customer’s request, without implying blame or adding a reason they did not give. If the scope is unclear, ask a brief clarifying question before treating all work as paused. This prevents a narrow request from being interpreted as permission to stop unrelated work.
Make the restart condition observable
Describe what must happen before work resumes. That might be a named approval, a decision between stated options, or receipt of specific material. Avoid wording such as “when you’re ready” if the team needs a particular sign-off or document to proceed.
If you know who will send the approval, name that person or role; if you do not, ask the customer to confirm. A restart condition should be something both sides can recognize in a later email. For example, “We’ll restart the layout once you confirm the approved version” is more actionable than “We’ll wait for the go-ahead.”
Address the existing deadline directly
Do not silently replace the original deadline with a new date or imply that it automatically moves. State the current position plainly: whether the date remains the working target, whether its feasibility needs to be reviewed after approval, or whether the customer has agreed to a revised date.
When the pause may affect timing but the impact is not yet clear, say so and identify when you will revisit the schedule—for example, after the approval arrives. Do not promise a new delivery date before confirming what remains to be done and when it can resume. If the customer expects the original date to hold, ask for explicit confirmation rather than assuming.
Put the agreement in one reply
Send a concise recap in the existing conversation so the request and your understanding stay together. Include the item paused, the restart condition, the deadline status, and any agreed check-in. Invite correction on the parts that might otherwise be ambiguous.
Use neutral language such as “Please reply if I’ve misunderstood the scope or schedule.” That makes it easier to resolve a mismatch before anyone acts on it. Avoid presenting an internal approval as complete unless the customer has actually confirmed it.
To: [customer contact] <[contact]@example.com> Subject: Confirming pause on [work item] Hi [name], Understood that you’d like us to pause [specific task] while your team seeks internal approval. We’ll hold that work and restart once you confirm [specific approval or information]. The current target of [existing date] remains the date we have on record; we have not agreed to a new date. Once approval arrives, we’ll review the remaining work and confirm whether that target is still feasible. Please let me know if you intended a different scope or schedule. Thanks, [Sender]
Keep the pause visible and follow up carefully
Make a short record in the place your team uses to track customer work: note who requested the pause, what is on hold, the restart condition, and the deadline status. If that system supports reminders, set one for an agreed check-in or a reasonable point to ask whether there is an update. A reminder is not approval and should not trigger work automatically.
If the customer replies with approval, acknowledge what was approved and confirm the next step and timing before restarting. If the reply is incomplete, ask for the missing decision or information. Where there is no response, send a courteous status check that refers to the agreed condition; do not describe the work as resumed unless the condition has been met.
Check that both sides have the same record
You can confirm the pause was handled clearly by checking that the email states the paused scope, the exact restart trigger, and what is—and is not—known about the deadline. The customer should have a straightforward way to correct any of those points. Keep the confirmation with the project record so another team member can understand the status without guessing.
If the customer does not confirm a schedule change, preserve the distinction between the existing target and a newly agreed commitment. This protects clarity without making the exchange adversarial: the goal is a shared understanding of what happens next, not to assign fault for the delay.
- Paused work is identified precisely and attributed to the customer’s request.
- The required approval or information is specific enough to recognize when received.
- The existing deadline is described accurately, with no unapproved replacement date.
- A follow-up point or next step is recorded, and approval is not inferred from silence.
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