Process Capture
Process capture records how a task is actually performed, preserving observed actions and context as input to a reviewed procedure or training guide.
Process capture records an actual execution of a task: the actions taken, their sequence, and the context available to the observer. It gives a reviewer evidence to inspect when creating instructions or explaining how work happened.
Scribe, for example, turns screen activity into an editable screenshot guide. Scribe work instructions.
Capture, procedure, and process mining
A capture describes one observed path. An SOP describes how an authorized executor should perform the task, including prerequisites, branches, and stopping conditions. Moving from the first to the second requires owner review; a captured click does not establish that everyone may take that action.
Process mining asks a different question: what patterns are present across recorded events from a process? A single demonstration can help explain steps, but it does not establish how frequently a branch occurs across the organization's work.
Illustrative fictional fixture: a creative-asset request capture shows a complete brief being routed. An owner note says requests without a brief must be returned, but that branch was not demonstrated. Preserve the note's locator and ask the owner to confirm the return action instead of presenting it as an observed step.
A useful capture record distinguishes screen evidence, narrated rationale, and later additions. It also marks what is missing: access permissions, offline decisions, rare exceptions, or the result after the recording ended. Those gaps are inputs to the AI SOP workflow.
Use Scribe when visual documentation fits the task. For supplied local records, process-to-sop drafts the procedure, while the procedure exception reviewer inspects unsupported branches. The procedure graph check tests prerequisite structure; a teammate walkthrough still checks whether the instructions can be followed.
Filed under
process-capture · knowledge-work
Related
- Check Procedure GraphCheck explicitly recorded SOP step dependencies with Python: validate IDs and prerequisite references, compute deterministic execution layers for acyclic graphs, and report steps blocked by a cycle without executing the procedure.
- Create Standard Operating Procedures with AI from a Real WorkflowCreate an SOP with AI from captured steps, explicit prerequisites, exception paths, and a teammate walkthrough that checks the procedure.
- Procedure Exception ReviewerReview a drafted workplace SOP against captured walkthroughs and supplied exception cases: identify absent branches, unmet prerequisites, unclear stop conditions, and unsupported recovery steps without executing or editing the procedure.
- Process to SOPConvert supplied workplace walkthrough notes or readable process captures into one draft SOP with sourced steps, explicit inputs and outputs, observed branches, stop conditions, and an owner review queue. Use after a real process has been captured; do not invent policy or write an incident runbook.
- ScribeScribe captures on-screen workflows into editable visual guides and adds AI drafting features for titles, descriptions, and process documentation.