This SOP checklist template separates X01's recorded evidence from X02's blank start. Both reference P04v1, but only X01 has the fictional E11 content-version check. Run selectors show the right step records, and an exception view keeps missing H03 visible even when a later receipt is proposed.
Link the action to its revision
The fictional welcome-packet procedure has three supplied requirements: S01 matches the approved content version, S02 verifies included handout IDs H01, H02, and H03, and S03 records the review handoff. P04v1 identifies the exact version being discussed. Its actual authorization and current-use reference are still to confirm before operational use.
EPA's historical SOP guidance distinguishes a checklist from the complete procedure and links completed-action records to the activity. Use that structural idea here. The example is an office record, not an approved procedure or a claim of regulatory compliance. Your owner supplies the actual instructions, roles, and criteria for the work.
Read X01 one step at a time
In X01, S01 has illustrative evidence E11. S02 says H03 absent and links exception EX01. S03 was not performed. That produces one step with supplied evidence, one incomplete step, and one unperformed step. It does not establish a completed run.
Choose X01 in the reading view to inspect these three records. Select the exception to see its link to X01/S02/P04v1. Keep the observed gap distinct from the requirement. "Verify H01–H03" says what to check; "H03 absent" says what this sample execution found. Neither statement should overwrite the other.
Start X02 without inherited ticks
Choose X02. All three steps are Not started, and the evidence count is zero. Reusing the table structure and the same procedure reference is useful; reusing E11 as proof of another run's action would be misleading. Return to X01 and its original observations remain intact.
A reusable action record needs execution ID, step ID, exact revision, required check, observed result, evidence reference, actual date and role, exception, and review outcome. Leave unsupplied actual dates and people blank. Copying a sheet is not the time an action happened, and opening the HTML does not perform it.
Retain the gap through a later recheck
The later-H03 example adds a proposed arrival note without closing EX01. A file arriving is different from confirming its version, inclusion in the packet, and the required review. Keep the original absence record and add an actual source reference, recheck result, date, role, and decision when those exist.
If the procedure changes, retain the version used for the original action and ask the owner what must be rechecked. Preserve the old observation beside the new evidence. This makes it possible to understand what changed instead of replacing an incomplete historical record with a fresh tick. The example's controls inspect these states only; they neither approve P04 nor save an execution.
Copy this prompt to adapt the example
Design a procedure review sheet with the selected run above its checklist and a separate, persistently labeled exception record. Return one self-contained HTML file with embedded styling and working interactions. Use readable type, strong contrast, clearly labeled keyboard controls, and a layout that flows on a narrow phone. Identify the supplied data as a fictional example.
Build a run-specific reading checklist for fictional welcome-packet routine P04v1. State actual procedure approval/current-use reference as To confirm before operation. Requirements: S01 match approved content version; S02 verify included H01, H02, H03; S03 record review handoff. X01: S01 has fictional evidence E11; S02 records H03 absent with open exception EX01; S03 not performed. X02: all three steps Not started, no inherited evidence.
Provide X01 and X02 buttons that update the visible execution, step rows, evidence count, and open-exception summary together. A focused exception button shows EX01 linked to X01/S02/P04v1, regardless of current run view, with that scope explicitly labeled. A later-H03 scenario adds a hypothetical arrival note and blank source/version/recheck/date/role/review fields but never closes EX01. A baseline button clears that scenario. Preserve original observations and exact revision. Show actual dates, role holders, and reviewer decisions as not supplied, rather than invented. Include a blank reusable record outline. No operational checkboxes claiming work performed, authorization, file changes, saving, or fabricated completion.
Start the next packet with X02's empty checklist, while X01's exception remains attached to X01. That side-by-side distinction is useful in a reviewer discussion, and NOS can render the HTML companion for it. The reviewer can then identify the precise recheck still needed without mistaking a fresh run for closure of the earlier problem.