Most teams manage process changes through a mix of emails, paper forms, and manual approvals — leaving the request, the change, and the approval disconnected from each other and from the system itself. In Threaded, review and publish workflows are built into the Work Instruction and Map surfaces, capturing the who, what, and why of every change directly inside the platform.
#Work Instruction Review
Each Work Instruction has its own draft → review → publish lifecycle. When a change is ready for Production, editors use the Review tab on the Work Instruction detail page (available with the Builder plan and Version Control).
#What Review Includes
- Diff — a visual comparison of all changes since the last published version: procedures, steps, media, parts/tools references, and metadata
- Process CI — automated completeness and quality checks run from the Review tab before publish
- Approval — optional reviewer sign-off when your organization requires it (configured under Instructions > Configuration)
- Publish — releases the draft as the new published version, visible to operators and reflected in the Training matrix
#Who Can Review and Publish
Editors can edit Work Instruction drafts, run Process CI checks, and publish (or submit for approval when required). Operators cannot edit drafts, access the Review tab, or publish. If someone on the floor has feedback, they create an Issue that an Editor can review and act on.
#The Audit Trail
Every publish creates a version history entry: version name, publisher, timestamp, and release description. Over time this becomes the audit record for that Work Instruction — what changed, who approved it, and when it reached the floor.
#Map Publish
The Map uses a separate commit-based workflow. Editors make changes in Draft, then publish a commit from the Map toolbar when the updated value stream is ready. Published commits are timestamped and attributed, with prior commits retained in history for comparison and audit.
Map publish and Work Instruction publish are independent — coordinate both when a process change spans documentation and value stream structure.
#Process CI in Review
Process CI checks run from the Work Instruction Review tab to catch completeness and quality issues before publish. Checks can be configured as required or optional in the Version Control configuration pane. Results appear inline with links to the affected procedures and steps.
Editors can also request org-wide Process CI sweeps through the AI Assistant at any time to audit documentation quality across the organization.
#Why This Matters
The collaborative review process drives alignment and clarity before changes reach operators. Compliance frameworks like ISO 9001 require controlled document review — in Threaded that requirement is satisfied as a natural outcome of the Work Instruction review and Map publish workflows, not as a separate paperwork step after the fact.