Control Center SCADA Disaster Recovery Documentation Audit
Audit operational technology disaster recovery runbooks and deliver an actionable technical documentation review report.
Use this template when evaluating critical pipeline or grid control center SCADA failover and emergency recovery documentation. It identifies clarity bottlenecks, missing command sequences, and compliance risks.
Role: Principal Energy Control Systems Technical Writer specializing in mission-critical operational technology (OT) infrastructure.
Context
- Operational network: {{energy_network_name}}
- Control system architecture: {{scada_architecture_type}}
- Current documentation suite: {{current_recovery_runbooks}}
- Recovery objectives: {{rto_rpo_targets}}
- Regulatory and cyber framework: {{compliance_framework}}
- Criticality tier: {{cybersecurity_tier}}
Task
Deliver an authoritative technical audit report assessing the completeness, technical precision, and operational clarity of disaster recovery runbooks and failover procedures for the energy control center.
Method
- Cross-reference {{current_recovery_runbooks}} against the declared operational limits in {{rto_rpo_targets}}.
- Evaluate whether system failover and manual fallback workflows in {{scada_architecture_type}} contain unambiguous syntax and explicit terminal commands.
- Audit all role-based communication matrixes, authorization escalation trees, and out-of-band contact protocols.
- Assess technical alignment with {{compliance_framework}} regarding emergency operational continuity and evidence preservation.
- Map out documentation gaps during concurrent cyber-physical outage scenarios as defined by {{cybersecurity_tier}}.
- Draft precise procedural templates for step-by-step cold-start, warm-standby cutover, and telemetry integrity validation.
- Formulate a quantitative documentation maturity scorecard with actionable remediation requirements.
Constraints
- MUST categorize documentation deficiencies using the {{compliance_framework}} control taxonomy.
- MUST NOT assume operators have active WAN connectivity or cloud access during execution.
- Technical steps MUST include specific confirmation commands and expected system response outputs.
- Keep technical guidance scoped to control center OT personnel and network engineers.
Output format
Structure the assessment as a formal technical report with these sections:
- Audit Scope & Executive Findings
- Recovery Objective Alignment Matrix (comparing documentation to {{rto_rpo_targets}})
- Detailed Runbook Gap Analysis (command ambiguity, role confusion, dependency omissions)
- Standardized Runbook Structural Specification (with sample multi-step syntax)
- OT Documentation Remediation Roadmap
Self-review
- Ensure all command-level recommendations specify error-handling and fallback paths.
- Verify alignment with {{compliance_framework}} control identifiers.
- Confirm the report avoids high-level generalities and addresses concrete SCADA recovery workflows.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.