Traditional version control processes manage change by saving a new copy of a document, making edits to that copy, and then sharing the updated file. This works to satisfy an audit, but it creates disconnected snapshots with no clear record of how those procedures interact, what changed between them, or whether operators are always seeing the current version.
Threaded uses a different model. Work Instructions and the Map are versioned independently within your organization, each with its own draft and published states and a complete history of every change. Each improvement builds on the last, creating a traceable record of how your process documentation and value stream have developed over time.
#Two Versioned Surfaces
Version control in Threaded applies to two main areas:
Work Instructions — Each Work Instruction in the Instructions Library is its own versioned document. Editors work in a draft, review changes on the Diff and Review tabs, and publish when ready. Operators and the Training matrix see only published versions.
The Map — The org-level value stream map uses a Draft / Published commit model. Editors make changes in Draft, then publish a commit from the Map toolbar when the updated value stream is ready to publish.
Work Instructions and the Map are related conceptually — both describe your process — but they version independently. Publishing a Work Instruction does not automatically publish Map changes, and vice versa.
#Work Instructions: Draft → Review → Publish
At any moment, a Work Instruction exists in one of two states:
- Published: The approved, active version operators see and the Training matrix references.
- Draft: An in-progress editing environment where changes are made before they go live.
When you’re ready to improve a Work Instruction, you edit the draft without affecting the published version. Operators continue following the current published document while you work.
With the Builder plan, the Work Instruction detail page adds formal review tooling:
- Diff — visual comparison of all changes since the last published version
- Review — run Process CI checks, request approval, and publish
On Starter, editors can publish directly without a formal review step. In either case, operators always see only the published version until you explicitly publish a draft.
#The Map: Draft → Publish
The Map follows a similar two-state model at the org level:
- Published — the approved value stream operators and reports reference
- Draft — the active editing environment for process nodes and grouping on the Map canvas
Use the version selector in the Map toolbar to switch views or browse history. When your edits are ready, click “Save” to create a new Published view.
#Reading Version History
Work Instructions: Version History in the Instructions section shows the org-wide timeline of published Work Instruction releases — who published, when, and what changed.
The Map: The commit selector and history list show prior published Map commits with timestamps and publishers.
You can open previous versions to review them, compare against the current published state, and restore a draft from an earlier point when needed.
#Why This Matters
The traditional “save as” model creates a collection of snapshots with no connection between them. Finding out what changed between two PDF revisions means opening both and manually comparing them.
Threaded keeps your process documentation connected. Every Work Instruction improvement and every Map publish is traceable. Changes are reviewable before they go live. Operators always see the current approved version, and compliance frameworks like ISO 9001 get a built-in audit trail — not a separate documentation exercise after the fact.
The goal isn’t just documentation for compliance. It’s giving your team a reliable, low-friction way to collaborate and keep improving without losing track of where you’ve been.