internaloperations/sops/README.md
SOPs
- Owner
- Bence
- Updated
- 26 August 2026
- Review
- quarterly
A standard operating procedure is a repeatable process involving people.
Every SOP follows templates/sop.md: Purpose, Scope, a RACI matrix, the process flow,
steps as Who / When / How / Output, an exceptions table, metrics, and related documents.
The exceptions table is the most valuable section and is never omitted. "Usually we do X, but when Y we do Z" is the part nobody else knows.
Write one with /process-doc.
Index
| SOP | Thin? |
|---|---|
releasing-a-version.md |
Yes — links to docs/BRANCHING.md |
deploying-to-production.md |
Yes — links to docs/OPERATIONS.md |
handling-a-gdpr-request.md |
Yes — links to docs/COMPLIANCE.md |
running-a-mobile-sound-setup.md |
No — physical equipment, no technical counterpart |
Still to write: monthly-close.md, onboarding-a-contractor.md,
offboarding-a-contractor.md, running-a-flow-event.md.
"Thin" is a property worth tracking. An SOP marked thin must not grow a procedure. If somebody adds commands to one, the fix is to move them into the technical document and shrink the SOP back.
In this section
SOP: Deploying to productionPut a named release onto the production box, deliberately.operations/sops/deploying-to-production.mdSOP: Handling a GDPR requestconfidentialAnswer a member exercising their rights, correctly and in time.operations/sops/handling-a-gdpr-request.mdSOP: Releasing a versionTurn a set of merged changes into a named, deployable release.operations/sops/releasing-a-version.mdSOP: Running a mobile sound setupPut amplified music into a space we do not control, reliably, with one person carrying the gear. The process exists so that a Flow event does not depend on the venue having a PA, and so that somebody who has never touched DJ equipment ca…operations/sops/running-a-mobile-sound-setup.md