Protocol
Checkpoint the task before a planned interruption
The cheapest resumption work is done before you leave.
When it fits
- You know you must switch away from a cognitively demanding task and will return later.
When to avoid it
- Unexpected interruptions may prevent a checkpoint; use the existing restart-note practice afterward when needed.
Why it matters
Before switching, capture the current state, the exact next action and any fragile intermediate value or question. Stop at a stable boundary when possible. This differs from a generic to-do: the checkpoint preserves the mental state needed to resume the specific task.
Steps
- After the interruption, you can restart from the checkpoint without reconstructing the whole task history.
An example
Before a meeting, note 'IDoc filter confirmed for channel 10; next compare channel 20 source records; query saved in tab 3.'
Check your result
After the interruption, you can restart from the checkpoint without reconstructing the whole task history.
Keep this limit in mind
- Unexpected interruptions may prevent a checkpoint; use the existing restart-note practice afterward when needed.
Connected ideas
Use beforeResume from the saved state before rereading everything
Evidence and sources
Supports
A systematic review and meta-analysis found that interruption-management interventions can reduce resumption lag and improve primary-task accuracy, with effectiveness varying by task and intervention type.
Most included studies were laboratory-based; workplace effects and implementation costs vary.
Supports
A 2026 programming-task study found interruptions increased task-completion costs and additional information checking during resumption.
The sample was small and one task domain was studied.