These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Checklist & SOP Management
- Features
- Review and Publication
Review and Publication
Record independent decisions before a version is published.
OverviewReview queue×
Checklist & SOP Management · Review and Publication
New
Review queue
Action waits for the independent reviewer
| Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|
| SPD-40237 | 50 | Pending | ER-333 | ||
| SPD-28225 | 190 | Pending | ER-102 | ||
| SPD-59458 | 460 | Pending | ER-365 | ||
| SPD-99692 | 280 | Pending | ER-605 | ||
| SPD-42709 | 740 | Pending | ER-170 |
6 of 6 records
ER-333Review decisions · RD-28808
PendingSourceSPD-40237
Source revision50
What you can do
Make the decision traceable
The independent reviewer works against a specific source revision. The decision record holds the reviewer, decision, date, reason and evidence reference. A returned or rejected revision remains a visible decision with its explanation. An approved revision is the basis for moving a definition into the reviewed state. The publication step then freezes that reviewed revision in a durable run and moves the definition to published.
Suppose an owner has updated an instruction after a previous execution. The reviewer compares the current revision with its supporting evidence and records the decision. If the evidence needs clarification, the reviewer returns it with a reason. The owner can correct the definition and seek another decision. When approved, the publication operation keeps its source revision and operation key, so the published version can be traced back to the human decision.
How the work is organized
- Revision decision. The Independent Reviewer records a decision, reason, date and evidence reference for the source revision.
- Published result. The Procedure Owner publishes the reviewed revision; its run retains the frozen source revision and operation key.
- State trace. The publication step and state history show the result of the operation and the resulting definition status.
What to agree during setup
Agree who prepares the revision and who may decide it independently. The Procedure Owner must give the reviewer the revision and supporting evidence, including the reason for a change after earlier execution. Define what warrants Returned instead of Rejected, and require a useful reason for either decision. Before publication, compare the approved source revision with the current definition revision. The Operations Lead should know where to inspect a failed run or a publication request repeated after a timeout. A status alone cannot establish whether the numbered publication step succeeded.
Check the handoff on an actual case
Prepare a draft inspection procedure and ask the Independent Reviewer to return it with a reason. Have the Procedure Owner correct the instruction and request another decision against the new revision. Once the reviewer approves that exact revision, publish it and compare the decision, publication run, numbered step and state history. Repeat the request with the same operation key and inspect the recorded result before any retry. If the definition changes between approval and publication, stop and seek a decision for the changed revision.
What your team sees
- Review queue — Find pending decisions and the revision each one concerns.
- Publication board — See draft, reviewed and published definitions by status.
Follow the work through
See the first handoff and the next decision.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact SOP revision.
- SOP definitions
- Versioned standard operating procedure definitions with execution status.
- Evidence documents
- Verifiable evidence attached to a SOP definition execution.
- Operation runs
- Workflow-maintained durable runs with frozen revision and input hash.
- Operation steps
- Numbered step trace with persisted input and output references.
- State history
- Immutable status transition history for each SOP definition.
Who uses it
Permissions- Independent Reviewer
- , Procedure Owner and Operations Lead.
Set up Checklist & SOP Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.