# Keep the procedure and each occurrence as separate records

Use a fictional weekly help-link review. The library describes how to perform it; a work log records one occurrence. All references, roles and observations below are teaching examples, not customer results. The review finishes when each reference is classified and every unresolved item has an owner and follow-up; it does not mean all corrections have already been published.

The file contains this fictional procedure, its work-log example and blank fields to adapt. Use Notion's import flow if you need an editable page; configuring typed properties, relations and recurrence remains separate work. Opening a Markdown file in Notion Desktop can instead show a read-only preview.

## SOP library example

- **Procedure:** SOP-07 · Weekly help-link review
- **Maintaining owner:** Support lead
- **Instruction reference:** Revision A · example published instructions
- **Trigger:** The agreed weekly review point
- **Scope:** Fictional references FAQ-11, FAQ-12 and FAQ-13
- **Completion condition:** Classify all three references and assign each unresolved correction and next check.

1. Open the current review instructions and the three permitted sample references. Identify the maintaining owner before proposing a correction.
2. Check each reference against its intended source. Record current, correction needed or source unavailable, with the observation.
3. Assign each open correction to a named owner with a follow-up point. Route proposed instruction changes through the team's agreed review and publication process.
4. Review the occurrence record and open actions together. Record the review outcome without marking unresolved content as corrected.

## One fictional work-log record

- **Occurrence:** WL-104 · first example weekly review
- **Procedure used:** SOP-07 revision A
- **Person doing the review:** Reviewer A · fictional role
- **Observations:** FAQ-11 current; FAQ-12 title needs correction; FAQ-13 source unavailable.
- **Open actions:** Owner B follows up FAQ-12 and Owner C resolves FAQ-13 before the next agreed review.
- **Review outcome:** Review complete; two correction actions remain open.

In a Notion setup, choose how library pages, work-log entries and linked actions are represented and connected. Configure the property types and permissions your team needs. In SOPFlow, keep the maintained SOP separate from its operational runs and inspect the particular run's checks and evidence. Neither a page view nor a status label alone demonstrates the underlying work.

A label saying revision A and a link to a live page do not by themselves preserve A's instruction content. Agree how earlier work retains its reference, using the history, archived content or other controls your chosen setup supports. SOPFlow snapshots a run's starting procedure content. Test an instruction change between two occurrences and inspect the old and new records in both products.

## Blank setup and occurrence record

- **Procedure title and maintaining owner:** __________
- **Current instruction reference and approved source:** __________
- **Trigger, scope and finish condition:** __________
- **Steps and exception route:** __________
- **Occurrence reference and person doing the work:** __________
- **Instruction reference retained for this occurrence:** __________
- **Observations and completion evidence:** __________
- **Open action, resolving owner and follow-up:** __________
- **Review decision and next occurrence:** __________

https://sopflow.io/compare/sopflow-vs-notion/