A downstream task cannot safely start until another team confirms a prerequisite is actually complete.
The useful bits
- Dependency identifier
- Evidence needed to begin
- A useful reply distinguishes completed work from outstanding conditions and provides the agreed proof.
Before you write
Use this example when a downstream task cannot safely start until another team confirms a prerequisite is actually complete. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Dependency identifier
- Evidence needed to begin
- Owner of the downstream task
An email you can adapt
The subject “Completion check for [dependency]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Completion check for [dependency] Hi [name], Before we start [downstream task], we need to confirm that [dependency] is complete. Could you share [test result, approved file or other evidence] and identify any remaining limitation? The tracker currently says [status], but that alone does not establish readiness for our use. If the dependency is still in progress, please give the next checkpoint so we can plan an alternative without creating duplicate work. Best, [sender]
Check the boundary
Request proportionate evidence through an authorized channel, without demanding confidential material unrelated to readiness.
What a useful reply should settle
A useful reply distinguishes completed work from outstanding conditions and provides the agreed proof.
The receiving owner should confirm that the evidence satisfies their prerequisite before starting dependent work.
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