SOP REVIEW CHECKLIST

REVIEW RECORD
SOP title:
SOP ID:
Version under review:
Process owner (role):
Approver (role):
Reviewer:
Review date:
Test environment:
Review scope:

PREREQUISITES, STARTING STATE, AND SCOPE
[ ] The SOP names one procedure with a clear trigger and finish condition.
[ ] The version under review is identified and no older copy is being tested by mistake.
[ ] Required roles, permissions, tools, inputs, and approvals are listed before step one.
[ ] The reviewer can create the stated starting state without using live customer data.
[ ] The SOP says what is out of scope and where a different procedure begins.
[ ] Any irreversible, destructive, or permission-changing action has an explicit authorization check.

ACTION → EXPECTED RESULT → EVIDENCE
Complete this block for every step.

Step number:
Action:
Expected result:
Observed result:
Evidence reference:
Status: Pass / Revise / Blocked

[ ] The step contains one observable action and starts with a specific verb.
[ ] The named role is allowed to perform the action.
[ ] The expected result is visible or otherwise verifiable.
[ ] The evidence is sufficient to confirm the result without collecting unrelated data.
[ ] The next step starts from the state this step actually creates.
[ ] A reader can tell when to continue, retry, stop, or use a different branch.

DECISION POINTS, EXCEPTIONS, AND OWNERS
[ ] Every decision uses an observable condition rather than an assumed cause.
[ ] Each branch names the next action and the role that owns it.
[ ] Stop conditions appear before an unsafe or irreversible action.
[ ] Escalation instructions name a destination, required evidence, and communication owner.
[ ] No branch ends with vague wording such as "handle as needed" or "contact the appropriate team."
[ ] A missing prerequisite leads to a defined correction or handoff rather than a guess.

DATA, PERMISSIONS, AND ACCESSIBILITY
[ ] The procedure asks for only the data needed to complete or verify the task.
[ ] Synthetic or sample data is used for the review when possible.
[ ] Secrets, authentication codes, payment details, health information, and unrelated personal data are excluded.
[ ] Permission boundaries are stated where the action occurs.
[ ] Instructions do not depend only on color, sound, motion, or an image.
[ ] Informative screenshots have useful alternative text and the instruction remains available in text.
[ ] Links, recordings, and referenced documents are accessible to the intended reader.

SECOND-PERSON DRY RUN
[ ] A trained person who did not write the SOP followed it without coaching.
[ ] The reviewer recorded every pause, question, skipped step, and unexpected branch.
[ ] The operator reached the stated finish condition or a documented stop condition.
[ ] A second reviewer is scheduled when the task has meaningful operational, security, or data risk.
[ ] The owner received the review notes and assigned each required revision.

APPROVAL AND MAINTENANCE HANDOFF
Review outcome: Ready for approval / Needs revision / Blocked
Required revisions:
Evidence retained at:
Owner response:
Approver decision:
Approved version:
Effective date:
Next review date:
Change-log entry:
Event-based review triggers:

[ ] Every required revision has an owner.
[ ] The approver is reviewing the corrected version, not the failed draft.
[ ] The revision history records what changed and who approved it.
[ ] Calendar and event-based review triggers are recorded.
[ ] Linked screenshots, recordings, and supporting documents match the approved text.
[ ] Superseded instructions are clearly marked or removed from the normal workflow.