Capturing Procedures

Procedures form the foundation for all outputs, so capture is designed to produce something that can be edited, reused, and kept up to date.

Creating procedures

Procedures can be created in different ways, depending on the task and the environment.

This may involve capturing actions as a task is performed, or capturing screens and describing the steps directly.

In all cases, the result is the same: a structured procedure that can be edited, maintained, and used across formats.

Capturing in context

Procedures are captured while a task is performed in a real application. Actions are translated into discrete instructional steps, each supported by relevant screenshots.

Each step represents what needs to be understood rather than everything that happened.

Structured instead of recorded

Runthru Instruction does not capture continuous video. Procedures are stored as ordered steps.

This allows procedures to be reorganised, simplified, and reused without needing to repeat the original task.

Reducing noise

Not all actions are instructionally useful. Captured steps can be consolidated so that unnecessary detail does not appear in the final procedure.

This keeps procedures focused and readable while remaining accurate.

Screens as part of the procedure

Screenshots are associated with steps and remain part of the procedure structure. They can be updated or replaced without recreating the whole procedure.

This allows procedures to remain current as applications change.

Editable after capture

Procedures can be refined after capture. Steps can be merged, reordered, or updated without affecting the underlying structure.

Changes are applied to the procedure itself, rather than to individual outputs.

Designed for reuse

A captured procedure is not tied to a single output. It can be used across documents, presentations, and video without being recreated.

This makes the procedure a durable asset rather than a one‑off capture.