
A structured pathway to develop, validate and deploy SLA-aligned SOPs and runbooks across L1 and L2 operations delivered by Energy Way's Senior Business Analyst, Scott Evans.

Mile Radosevic | COO
0433 102 100
Domagoj Dedic | CEO
0431 167 294
EVO Power Slide Deck | SOP and Runbook Creation | Asset and Event Analysis
The foundation of effective Help Desk operations begins with a thorough understanding of the assets being supported and the events that will demand a response. This first phase establishes the analytical baseline from which all SOPs and runbooks are built.
Develop a high-level register covering all supported assets, systems and key technical variations to ensure complete operational visibility.
Identify and prioritise the faults and events expected to be managed at L1, ensuring the Help Desk is prepared for the most likely scenarios.
Categorise events by severity, frequency, complexity and expected resolution time to enable structured and consistent triage.
Apply an urgency-versus-impact matrix to determine response priority and ensure the most critical events receive immediate, appropriate attention.
EVO Power Slide Deck | SOP and Runbook Creation | SOP and Runbook Framework
Build standardised, asset-aware SOPs that guide common responses, manage exceptions and align every action with SLA and Liquidated Damages exposure.
With assets and events defined, this phase focuses on building a scalable, structured documentation framework. Each SOP is designed to be precise, repeatable and directly aligned to operational risk — including SLA obligations and Liquidated Damages exposure.
Create a uniform SOP template for each event category, ensuring consistency in format, language and operational instruction across all runbooks.
Develop base SOPs for common events, providing L1 operators with clear, actionable guidance for the majority of expected fault scenarios.
Document exceptions for battery type, asset configuration and fault variation — capturing the nuances that standard procedures alone cannot address.
Map each SOP and runbook against applicable SLA requirements and potential Liquidated Damages exposure, embedding commercial awareness directly into operational procedure.
EVO Power Slide Deck | SOP and Runbook Creation | L1 and L2 Response Procedures
Create clear L1 and L2 checklists, handover protocols and incident-record standards that preserve accuracy, context and accountability.
Consistent, well-documented response procedures are critical to delivering reliable service. This phase standardises how faults are diagnosed, described and transferred — ensuring every incident record is technically accurate and operationally reusable.
Define checklists covering the complete L1 and L2 workflow — from initial triage through to resolution or escalation — ensuring no step is missed under operational pressure.
Standardise how faults are diagnosed, described and transferred between tiers, eliminating ambiguity and reducing handover risk at every stage.
Ensure each incident record captures the relevant technical and operational context in a concise, accurate and reusable format — supporting both immediate resolution and long-term knowledge development.
Develop standard documentation templates and validation checklists to enforce quality and consistency across all L1 and L2 incident records.
EVO Power Slide Deck | SOP and Runbook Creation | Handover, Authority and Escalation
Define how L1, L2 and L3 diagnose, act, hand over and escalate, with controlled triggers for EVO Power, OEM and field engagement.
Clear escalation pathways and well-defined authority boundaries are essential to protecting asset performance and managing risk. This phase documents the end-to-end escalation structure — from L1 triage through to OEM and field team engagement.
Authorised response, initial diagnosis and structured handover to L2 with full incident context.
Technical diagnosis, permitted actions, exception handling, anomaly management and escalation decision rights.
Structured assessment of whether to resolve, monitor or escalate — with defined immediate triggers for L2-to-L3 escalation.
Escalation to EVO Power, L3 specialists, OEMs or field teams — with defined handover protocols and documentation requirements.
The L1-to-L2 handoff process is fully documented, including required information, validation checks and all supporting documentation , ensuring clean, accountable transitions at every tier.
EVO Power Slide Deck | SOP and Runbook Creation | Technical Review and Approval
Apply internal technical scrutiny and formal EVO Power approval to ensure every SOP meets operational, technical and contractual requirements.
All SOPs and runbooks undergo a rigorous two-stage review process before entering controlled use. Internal technical scrutiny is followed by formal submission to EVO Power — ensuring every procedure meets operational, technical and contractual standards.
A comprehensive internal review of all SOPs and runbooks is led by Mile Radosevic, validating technical accuracy, operational clarity and procedural completeness prior to external submission.
Documentation is submitted to EVO Power for formal review, amendment and approval — ensuring alignment with asset owner expectations, operational requirements and contractual obligations.
Approved amendments are incorporated and all documentation is finalised as controlled versions — establishing a clear, auditable record of approved procedures ready for deployment.
EVO Power Slide Deck | SOP and Runbook Creation | Training and Knowledge-base Deployment
Convert SOPs and runbooks into structured courseware and searchable Atlassian knowledge, ready for use at the point of response.
Approved procedures are only effective when operators can find, understand and apply them reliably. This final phase converts finalised documentation into training courseware and structures it for deployment within the Atlassian knowledge base — ensuring the Help Desk is operationally ready from day one.
Approved playbooks and runbooks are converted into structured training courseware, equipping L1 and L2 operators with the knowledge and confidence to respond correctly under operational conditions.
Approved content is prepared and ingested into the Atlassian knowledge base, creating a centralised, searchable repository accessible to frontline operators at the point of need.
Content is structured to support rapid frontline retrieval, consistent application across all operators and straightforward updates as assets, procedures or requirements evolve over time.
If you have any questions, or would like to discuss this opportunity in more detail, please contact us.

Mile Radosevic | COO
0433 102 100
Domagoj Dedic | CEO
0431 167 294
From Asset Knowledge to Operational Readiness. A Five-Phase SOP Framework