Why this matters
A practical approach to delivery checklist.
A checklist is useful when it prompts a decision, not when it repeats tasks no one owns.
What to write before the work moves
Use it before delivery to confirm the files, access, instructions, reviewer and next action.
The boundary to keep visible
Keep the completed checklist with the version actually sent to the client.
Operational example
Delivery checklist: the final check before sending
Before the final link, check at least: correct version, promised formats, working access, clearly stated exclusions and a clear approval request. This takes minutes and avoids many “I cannot find the file” follow-ups.
- Open the link from a session other than your own when possible.
- Check folder names and organisation from a third party’s point of view.
- Keep a copy of the version actually handed over.

Dealokr