Work cannot proceed responsibly until a missing decision is resolved and the team needs a bounded pause.
The useful bits
- Reason and affected scope
- Work that can continue
- The decision should state the paused scope, continuing work and owner of the next review.
Before you write
Use this example when work cannot proceed responsibly until a missing decision is resolved and the team needs a bounded pause. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Reason and affected scope
- Work that can continue
- Review date and decision owner
An email you can adapt
The subject “Proposed pause for [project work]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Proposed pause for [project work] Hi [name], I propose pausing [specific work] because [missing decision or dependency]. Continuing now would risk [practical consequence]. [Unaffected activity] can continue within its existing approval. Please confirm whether to pause the defined scope and set [date] as the review point, or provide another authorized direction. We will preserve current records and clearly mark the status so no one assumes the work is complete or cancelled. Best, [sender]
Check the boundary
A pause should not silently cancel obligations, delete work or leave stakeholders without a next checkpoint.
What a useful reply should settle
The decision should state the paused scope, continuing work and owner of the next review.
At the checkpoint, explicitly resume, extend or change the plan rather than leaving an indefinite hold.
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