Capture, distill and use workflow: practical guide
Capture, distill and use workflow is a three-stage way to save a source, record why it matters and bring that note into a current task.
Quick answer
Capture the source URL or document identifier alongside a short statement of the question it answers.
What this guide is best for: readers who need to make a concrete decision about capture, distill and use workflow.
How do you put this into practice?
Use the following sequence as a starting plan, then adjust it to the work you are responsible for.
- Capture the source URL or document identifier alongside a short statement of the question it answers.
- Distill only enough context to recover the meaning and use it in the next relevant deliverable.
- Record the action you chose, its intended result and the next occasion on which you will check it. Keep the record in a place you can return to without rebuilding your setup.
How do the options compare?
| Checkpoint | Record |
|---|---|
| Failure to avoid | Do not retain a summary without the original source when factual verification matters |
What would this look like in practice?
An analyst captures a published specification, records the relevant constraint, and uses it to check a proposed design. This is an illustrative scenario, not a customer result or evidence of a measured improvement.
Which planning principle supports the method?
The National Cancer Institute’s archived implementation-intentions resource describes if–then plans that connect a situational cue with an intended action. Spry’s examples here are editorial applications of that planning idea, not evidence that this particular guide or product produces a measured outcome. The source is retained for reference and is no longer maintained.
Source reviewed 2 November 2026.