# Operations manual template

Editable starting structure from SOPFlow. Replace every bracketed field and test with the people doing the work before review and publication.

## Cover and scope

- Manual title/reference: [title and stable ID]
- Maintaining role and backup: [roles]
- Revision/status: [revision; draft / in review / approved]
- Reviewer, decision and effective date: [complete only after the decision]
- Readers and included work: [team, start and end of scope]
- Separate procedures/policies: [maintained references]

## How to use the manual

- Current home and route to a task: [location and search/index instructions]
- Questions or conflicting instructions: [owner and escalation route]
- Access: [who verifies reading, editing and approval permissions]

## Procedure index

Reference | Title | Maintaining role | Current revision | Maintained location
--- | --- | --- | --- | ---
[ID] | [task/outcome] | [role] | [revision/status] | [link]

## Procedure page — repeat for each task

- Title/reference and revision: [ID]
- Outcome, scope and trigger: [accepted result and start event]
- Owner, performers, receiver and reviewer: [roles]
- Prerequisites: [approved access, information and references]

1. [Role: action, decision and expected result]
2. [Role: next action and handoff acceptance]
3. [Role: completion check]

Exception: [stop condition, unresolved-item owner and escalation route]

Execution record: [reference, procedure revision, result, acknowledgment, unresolved items]. Keep individual results separate from reusable instructions and protect private data in its authorized system.

## Review and publication

- Routine review point and earlier triggers: [choose for the work]
- Change request and affected references: [record]
- Ordinary/exception tests and reviewer decision: [results]
- Publication reference and reader-access check: [after approval]
- Training decision and next review: [owner and action]

## Pilot and migration

Ask another teammate to find and follow one procedure, handle an exception and report a correction. Define acceptance criteria first. Inventory old files, reconcile conflicting instructions, preserve useful history and update links before expanding.

Review record: [date; item; decision; owner; next action; reference]. Decide retention and access under your own requirements. Text import does not transfer another system's full history or permissions.