Grace Williams·
Wrote an ISO-style SOP for backup verification detailed enough that a new on-call could follow it
Creates detailed, compliant SOPs with step-by-step instructions, safety notes, version control, and training checklists.
SOP (Standard Operating Procedure) Builder
You are a quality management systems expert who creates ISO-compliant Standard Operating Procedures. Write a comprehensive SOP for: {{procedure_name}} at {{organization_name}}. The SOP applies to {{audience}}. The objective is: {{objective}}. This procedure is performed {{frequency}}. Key safety/compliance considerations: {{safety_considerations}}. Include: (1) SOP Header with document control information (version, author, approval, effective date, review cycle), (2) Purpose and scope statement, (3) Roles and responsibilities with named positions, (4) Required materials, tools, and prerequisites, (5) Step-by-step procedure with numbered steps, substeps, and decision points, (6) Visual workflow diagram description, (7) Quality checkpoints and acceptance criteria, (8) Safety warnings and PPE/equipment requirements, (9) Troubleshooting guide for 5 common issues, (10) Related SOPs and references, (11) Revision history table, (12) Training verification checklist, (13) Sign-off page. Make it precise enough that someone unfamiliar with the task could follow it.
Ergebnisse
# SOP — Monthly Production Database Backup Verification @ CloudNest
**Doc control:** v1.0 | Author: SRE Team | Approved: Eng Director | Effective: 2026-06-01 | Review: annual.
**Applies to:** on-call SRE engineers. **Objective:** confirm backups are complete and restorable. **Frequency:** monthly. **Compliance:** SOC 2 evidence required.
## Roles
- **SRE on-call:** executes the restore test.
- **SRE lead:** reviews + signs off.
## Prerequisites
- [ ] Read access to backup bucket
- [ ] Isolated staging restore target
- [ ] Latest backup manifest
## Procedure
1. Confirm the most recent backup exists and matches the schedule.
1.1 Check checksum against manifest.
2. Provision an isolated restore instance.
3. Restore the latest backup to staging.
- **Decision:** restore fails → escalate to SRE lead immediately, do not retry blindly.
4. Run the validation query suite; confirm row counts within tolerance.
5. Record completion time + result in the evidence log.
6. Tear down the staging instance.
## Quality checkpoints
Backup age < 24h · checksum valid · validation suite 100% pass.
## Safety
Never restore into production. Use read-only credentials for verification.
## Troubleshooting (5 common)
| Issue | Action |
|-------|--------|
| Checksum mismatch | Quarantine backup, trigger fresh backup |
| Restore timeout | Increase instance size, retry once |
| Missing backup | Page backup-system owner |
| Row-count drift | Compare against prod snapshot |
| Permission error | Verify IAM role |
**Revision history:** v1.0 initial. **Training verification:** trainee completes one supervised run + sign-off. **Sign-off:** executor + reviewer initials and date.
Modell: Claude Sonnet 4
91 Likes37 SavesScore: 49
6 Kommentare
Noah Steiner·
The delegation breakdown showed me what I should've handed off ages ago.
Ethan Reed·
Sending this project management one to my team.
Maya Patel·
Adopted the two-minute capture habit from this and never looked back.
Sofia Almeida·
Energy-band routing finally made my afternoons usable.
Leon Wirth·
My inbox went from 200 to 0 using this triage logic.
Anna Hofmann·
This made my 1:1s 10x more useful. The agenda structure is gold.