Quick overview

Step 1

Create

Start a new work instruction and add content (text, images, videos, checklists).

Step 2

Save

Save drafts as you go. Drafts are only visible to managers.

Step 3

Publish

Publish when ready. The published version is available to end users.

Step 4

Update & Retract

Editors can create a new version. Retract to prevent execution while managers can continue editing.

Frequently asked questions

Version control tracks every change to a work instruction. Each published update becomes a new version with a timestamp and author, creating a clear audit trail while ensuring users always access the correct, most recent guidance.

  1. Create: Add a new instruction and insert your content.
  2. Save: Save your draft as you refine it. Drafts are not visible to Execute users.
  3. Publish: When ready, publish the instruction so authorized end users can execute it.

Editing a published instruction produces a new version. The prior version remains available in the history for audit and rollback. End users will see the latest published version.

Retract removes a work instruction from execution. Managers can still view and edit a new version of the retracted instruction. However, users with an Execute subscription cannot run it until it is published again.

Yes. Retraction is ideal for pausing execution while you fix issues or make improvements. Managers can keep iterating and publish a new version when the instruction is ready again.

No one. Retracted instructions are not executable by users with an Execute subscription. Only managers can access them for review and editing.

Yes. You can restore or republish an earlier version if needed. Version history provides visibility into who changed what and when, supporting audits and compliance.

Execute users only see the latest published version. Drafts and retracted instructions are hidden from execution to prevent using outdated steps.

  • Use clear titles and summaries when publishing a new version.
  • Retract if safety, quality, or compliance is in question.
  • Bundle minor edits into one publish to reduce noise.
  • Review version history regularly to ensure traceability.