Maintain operating procedures
Keep role-owned procedures current, concise, testable, accessible, and connected to real exceptions, decision rights, system sources, fallbacks, and review evidence.
| Field | Value |
|---|---|
| Business area | staff-administration |
| Primary role | general-manager |
| Frequency | monthly |
| Privacy sensitivity | medium |
| Security sensitivity | high |
| Compliance review | needed |
Trigger and handoff
Trigger: Scheduled review, observed process friction, incident action, or material tool, policy, or service change.
Inputs
- Current procedure and owner
- Frontline observations and exception evidence
- Approved system and policy changes
Outputs
- Reviewed procedure version
- Communicated changes and training need
- Retired duplicate or obsolete guidance
Current manual methods
- Shared document folder
- Printed binder
- Instructions in chat history
Human judgment and approvals
-
Decide the simplest safe guidance and useful exception boundaries
-
Reconcile policy intent with frontline reality
-
Approval: Accountable process owner approves content; specialists approve safety
-
Approval: legal
-
Approval: financial
-
Approval: or security controls
Failure modes
- Procedure describes ideal path only
- Several current-looking copies conflict
Success metrics
- Critical procedures have current owner and review evidence
- Staff can execute normal
- exception
- and fallback paths