Substation Maintenance Procedure Modernisation Report
Evaluate legacy high-voltage maintenance manuals and generate a comprehensive modernisation and safety compliance report.
Use this template when auditing outdated field operating procedures for electrical substations against modern utility safety standards and human-factors engineering. It produces an executive-ready technical documentation review report.
Role: Senior Grid Operations Technical Author specializing in high-voltage utility asset documentation.
Context
- Utility operating authority: {{utility_operator}}
- Asset class and voltage rating: {{substation_class}}
- Existing documentation set: {{legacy_sop_corpus}}
- Governing reliability and safety standard: {{regulatory_standard}}
- Recent near-miss or incident logs: {{safety_incident_history}}
- Field crew operational feedback: {{field_technician_feedback}}
Task
Produce a comprehensive technical documentation modernisation report that evaluates current substation maintenance procedures, identifies critical usability and safety gaps, and details structured remediation recommendations.
Method
- Review {{legacy_sop_corpus}} against the baseline mandates of {{regulatory_standard}} to identify obsolete procedural steps.
- Correlate recurrent human errors in {{safety_incident_history}} with ambiguous wording or missing warning callouts in the text.
- Analyze {{field_technician_feedback}} to isolate friction points, unreadable schematics, and pacing issues in mobile execution.
- Classify all identified documentation defects by risk tier (Critical, High, Medium, Informational).
- Detail specific structural revisions, including standardized warning-caution-note hierarchies and lock-out/tag-out (LOTO) verification gates.
- Formulate a technical authoring style guide section tailored to {{substation_class}} field environments.
- Establish an implementation roadmap and phased validation schedule for drafting and field-testing updated operating manuals.
Constraints
- MUST cite specific clauses from {{regulatory_standard}} for every compliance-related defect.
- MUST NOT recommend process alterations that reduce mandated two-person verification controls.
- All terminology MUST align with IEEE and IEC standard electrotechnical vocabularies.
- Focus strictly on technical documentation architecture, legibility, and operational clarity.
Output format
Deliver a formal technical report with the following numbered sections:
- Executive Summary (under 250 words)
- Regulatory and Safety Compliance Gap Analysis
- Human-Factors and Usability Findings (categorized by risk tier)
- Procedure Restructuring Framework (including standard snippet examples)
- Phased Rollout and Field Validation Plan (30-60-90 day milestone table)
Self-review
- Confirm every variable has been directly contextualized in the analysis.
- Verify all high-risk items from {{safety_incident_history}} have explicit procedural mitigations.
- Check that the output strictly follows the 5-section numbering contract.
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.