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
- Checklist Execution
Checklist Execution
Trace performed steps to the published definition.
OverviewMy definitions×
Checklist & SOP Management · Checklist Execution
New
My definitions
SOP definitions
| Number | Name | Revision | Status | Execution date | |
|---|---|---|---|---|---|
| SPD-76199 | SOP definition 533 | 30 | Draft | 16 Oct | |
| SPD-72029 | SOP definition 764 | 550 | Reviewed | 19 Oct | |
| SPD-96863 | SOP definition 900 | 270 | Published | 26 Oct | |
| SPD-70578 | SOP definition 315 | 50 | Executing | 16 Oct | |
| SPD-71217 | SOP definition 237 | 700 | Completed | 04 Oct |
6 of 6 records
SOP definition 533SOP definitions · SPD-76199
DraftRevision30
Execution date16 Oct
What you can do
Run from the published version
Execution begins from a published definition. The operator works through checklist execution records that carry sequence, description, observed date and outcome. Each record links to its parent definition and keeps the source record identity and version number. The definition’s required and completed step counts provide a summary, while individual outcomes show what actually happened at each step.
For a scheduled inspection, the operator records accepted results with evidence references and marks a rejected observation when a check fails. The rejected line is still part of the execution history. A follow-up action can be assigned to address it. The durable execution run records the source revision, and state history records the move into active execution. The operator can use the review page to compare the execution with its published definition.
How the work is organized
- Published source. The Checklist Operator starts from a published definition and its version rather than an unreviewed draft.
- Performed step. Each checklist record keeps sequence, observation, outcome, source identity and a link to its parent.
- Execution trace. The run and state history identify the source revision and the move into active execution.
What to agree during setup
The Checklist Operator and Procedure Owner should agree which published version applies on the planned execution date. Give each source step a stable identity so a later comparison can distinguish a repeated delivery from a different observation. Decide when a step is Accepted, Rejected or left Pending and what evidence reference should accompany each outcome. The Operations Lead should agree how to compare the run with the definition when an execution fails or the source revision has changed. Keep the operator’s observations separate from the reviewer’s later evidence decision.
Check the handoff on an actual case
Use an inspection with one accepted observation and one rejected observation. Start with a published definition and confirm its revision and version. Perform the checklist, then inspect the execution records for sequence, source record identity, outcome and parent. Compare the required and completed step counts with those records rather than assuming the counts explain a rejection. Open the Checklist Execution Review page with the Independent Reviewer to see the definition and evidence together. If a follow-up is raised, verify that the rejected outcome remains visible and that the assigned person can find the original observation.
What your team sees
- Execution board — Find published and active definitions ready for checklist work.
- Step outcomes — Inspect individual observations and their evidence references.
Follow the work through
See the first handoff and the next decision.
What it keeps track of
Data model- SOP definitions
- Versioned standard operating procedure definitions with execution status.
- Checklist executions
- Step-level execution detail captured against a published SOP definition.
- Execution attempts
- Each retry attempt of a checklist execution operation key.
- 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- Checklist Operator
- , Procedure Owner, Independent Reviewer 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.