How the problem develops
A draft is sent to several people with “please review”. One responds to an old copy, another assumes silence means approval. The coordinator keeps asking who is still outstanding without knowing which decision is actually required.
What to check first
- Separate optional comments from required approval and identify who has authority for each.
- Check whether a document change invalidates a previous approval.
A better process
- Send one versioned draft with a clear approval question.
- Record approved, rejected and changes-requested outcomes explicitly.
- Define a backup approver and a revision rule rather than treating no reply as acceptance.
What a system can do
Route a draft to the authorized approver, remind within agreed limits and record the decision against that version.
Where people stay in control
The workflow must not approve on behalf of a person or publish a revised document using an approval for an older version.
Benefits and tradeoffs
The useful outcome
The coordinator can see the remaining decision instead of reconstructing email replies.
The tradeoff
Formal routing can slow minor edits. Define which changes need fresh approval before automating the process.
Test before going live
Change the draft while approval is pending, reject it, then use the backup approver. The final release should reference the correct decision and version.