Runthru Instruction Capabilities
Runthru Instruction provides a set of capabilities for capturing, rendering, maintaining, and governing instructional content for software at scale. The sections below describe what the system supports in practice and how those behaviours fit together.
Capturing procedures
Runthru Instruction captures procedures as a sequence of steps paired with real application screens. Steps and screenshots are captured while a task is performed, preserving instructional intent without requiring authors to manually recreate screens or layouts.
Procedures are captured as structured steps rather than continuous recordings, allowing them to remain editable and maintainable over time.
Authoring and editing steps
Procedures remain editable after capture. Authors can merge steps, reorder instructions, and update text or screenshots without recreating the procedure.
Changes are applied at the procedure level rather than to individual outputs, allowing updates to propagate consistently wherever the procedure is rendered.
Rendering instructional outputs
A single procedure can be rendered into multiple instructional outputs. Runthru Instruction generates different formats from the same underlying procedure, adjusting layout and presentation according to system rules rather than manual design decisions.
Rendering is deterministic: the same procedure produces consistent outputs across formats without relying on author formatting effort or discipline.
Video generation from procedures
Runthru Instruction generates instructional video as a rendered output. Video is produced from captured screenshots and procedural steps rather than from live screen recording.
Generated video remains aligned with documents and presentations and can be regenerated when procedures change without requiring separate video editing workflows.
Screenshot management and protection
Screenshots are not handled as independent files. They are part of the procedure.
Sensitive information can be selectively blurred without retaking the capture, allowing the same procedure to be used across different environments.
When a screenshot changes, it is updated once and reflected wherever the procedure is used.
Publishing to existing platforms
Rendered outputs can be delivered into platforms where teams already work. Runthru Instruction acts as an authoring and rendering layer rather than a standalone content destination.
Published outputs remain linked to their source procedure, allowing regenerated versions to replace earlier outputs as systems change.
Keeping content up to date
Procedures can be updated and regenerated as applications evolve. Authors update the procedure once and regenerate all outputs, reducing drift between documentation, training, and video content.
This approach helps organisations keep instructional materials aligned with the current state of their software without repeated reauthoring.
Governance and consistency
Layout, presentation, and output structure are controlled by the system. Authors focus on instructional intent, while Runthru Instruction applies consistent rules for how content is rendered.
This separation supports consistency at scale without increasing authoring complexity or relying on manual enforcement.
Specialist capabilities
Runthru Instruction also supports the requirements that arise in real operational environments.
As procedures are used across teams, systems, locations, and audiences, they need to adapt without being duplicated or fragmented.
These capabilities support managing that variation while keeping procedures structured, consistent, and maintainable.
Next steps
Now that you've explored the capabilities, you can continue with any of the following.