Practical working guide
A project pause and restart checklist that preserves context
When a project pause has been authorised, record the current state, work still in progress, protected materials and conditions for restarting. Reconfirm scope, access and resources before resuming. A paused task is not cancelled work, and this checklist does not itself authorise suspension.
Capture a restartable snapshot
| Before the pause | Restart evidence |
|---|---|
| Completed work and unfinished tasks | Inspection or review of the actual current state |
| Current approved documents | Confirmation that revisions remain applicable |
| Materials and temporary access | Condition, availability and authorised access rechecked |
| Restart decision owner | Named person confirms the conditions are met |
Worked example: do not restart from an old diary entry
Fictional example: a website project pauses while the customer obtains approved photographs. When they arrive, the assigned designer is on another project and the text has changed. The restart owner checks the new assets, confirms the current copy and agrees a revised delivery slot. The old planned date remains in history; it is not silently presented as a current commitment.
Send one shared restart note
State why the work can resume, what remains unchanged, any approved changes, the next milestone and the responsible person. Reopen only tasks that should restart and retain links to unresolved blockers. Check actual terms separately for commercial or contractual effects; do not use an operational status change to imply new fees or a right to stop work.
Nominate a contact during the pause so new customer information reaches the restart owner instead of remaining in an unattended inbox.