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
- Evidence and Follow-up
Evidence and Follow-up
Verify supporting records and assign corrective work.
OverviewRejected steps×
Checklist & SOP Management · Evidence and Follow-up
New
Rejected steps
Checklist executions
| Parent | Sequence | Description | Outcome | Evidence reference | Waiver reason | |
|---|---|---|---|---|---|---|
| SPD-23292 | 80 | Rejected ce-142 | Rejected | ER-730 | Rejected ce-116 | |
| SPD-85108 | 60 | Rejected ce-750 | Rejected | ER-939 | Rejected ce-887 | |
| SPD-16371 | 60 | Rejected ce-579 | Rejected | ER-328 | Rejected ce-727 | |
| SPD-23432 | 40 | Rejected ce-229 | Rejected | ER-752 | Rejected ce-272 | |
| SPD-86495 | 40 | Rejected ce-712 | Rejected | ER-805 | Rejected ce-290 |
6 of 6 records
Rejected ce-142Checklist executions · CE-37349
RejectedParentSPD-23292
Sequence80
Evidence referenceER-730
Waiver reasonRejected ce-116
What you can do
Turn findings into accountable work
Evidence documents attach to a definition and keep a title, document date, external reference and verification state. A named person verifies each document. Step outcomes have their own evidence reference and observed date. Reviewing these together helps the team see which observation supports a finding and which source document was checked by a person.
If an execution step is rejected, the team can raise a follow-up action against the same definition. The action names the work, responsible person, due date and status. The assigned person records the resolution and completion date when the work is finished. An open finding remains distinct from the status of the definition itself: someone can see both the execution and the action it created. The reviewer can revisit the evidence before accepting a correction or superseding the executed revision.
How the work is organized
- Document check. An evidence document links to its definition and records its external reference, verification state and verifier.
- Finding. A rejected checklist outcome keeps the observation and evidence reference that prompted a closer look.
- Assigned action. A follow-up carries its source definition, assignee, due date, status and final resolution.
What to agree during setup
The Independent Reviewer and Checklist Operator should agree what evidence is sufficient for a performed step and who verifies a supporting document. Choose a stable external reference so the original material can be found again. For rejected observations, agree who opens the follow-up and how the assignee records a useful resolution. The Follow-up Owner needs a due date and a clear description of the work. The Operations Lead should decide when an unresolved finding requires correction of the executed revision and another independent decision.
Check the handoff on an actual case
Take a rejected safety check from a published execution. Open the observation and follow its evidence reference to the source material. Have the Independent Reviewer verify the supporting document under their own name. Create an Open follow-up on the same definition, assign it to the Follow-up Owner and set a due date. After the owner records a resolution and completion date, compare it with the original rejected outcome. The outcome should still tell the team what was observed at the time. If the executed revision needs correction, use the correction process and retain the earlier run.
What your team sees
- Rejected steps — Review failed observations and their supporting references.
- Open follow-ups — See assigned work that still needs a resolution.
Follow the work through
See the first handoff and the next decision.
What it keeps track of
Data model- Evidence documents
- Verifiable evidence attached to a SOP definition execution.
- Follow up actions
- Corrective follow-up work raised from checklist findings.
- Checklist executions
- Step-level execution detail captured against a published SOP definition.
- Review decisions
- Independent reviewer decisions recorded against an exact SOP revision.
- SOP definitions
- Versioned standard operating procedure definitions with execution status.
Who uses it
Permissions- Independent Reviewer
- , Checklist Operator, Follow-up 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.