1. Checklist & SOP Management
  2. Features
  3. Checklist Execution
Feature · Checklist Execution

Checklist Execution

Trace performed steps to the published definition.

OverviewMy definitions
Checklist & SOP Management · Checklist Execution

My definitions

SOP definitions

New
NumberNameRevisionStatusExecution date
SPD-76199SOP definition 53330Draft16 Oct
SPD-72029SOP definition 764550Reviewed19 Oct
SPD-96863SOP definition 900270Published26 Oct
SPD-70578SOP definition 31550Executing16 Oct
SPD-71217SOP definition 237700Completed04 Oct
6 of 6 records
SOP definition 533SOP definitions · SPD-76199
Draft
Revision30
Execution date16 Oct
Example screen with sample data

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

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.

How to get started