Gas Utility Compliance Excellence
Manage gas safety, pipeline compliance, and emergency response with digital tools designed for gas distribution networks.
The Challenge
Gas distribution networks operate under intense regulatory scrutiny where a single pipeline failure can cause explosions, fatalities, and mass evacuations. Managing pipeline inspections, leak surveys, emergency response documentation, and engineer competencies across thousands of kilometres of pipe and hundreds of field workers using paper systems creates unacceptable risk. When HSE investigates a gas incident or Ofgem reviews emergency response performance, incomplete documentation can result in prosecution, licence conditions, and public loss of confidence in network safety.
How Assistant Manager Solves Gas Compliance
Each module is designed to address the specific challenges gas businesses face every day.
Digital Checklist
Gas distribution networks must demonstrate systematic pipeline surveillance and maintenance to Ofgem and HSE - digital checklists provide the evidence trail that paper systems cannot
The Problems
Why This Matters for Gas
- Pipeline patrol and leak survey routes are recorded on paper that gets wet, damaged, or lost before it reaches the office for filing
You cannot prove patrol coverage to Ofgem, and leak detection is compromised because survey completion cannot be verified
- Governor maintenance checklists vary between engineers, with some checking all safety features and others taking shortcuts under time pressure
Safety-critical features aren't consistently checked, and governor failures can cause dangerous over-pressurisation
- Emergency response documentation is completed hours after the incident when engineers return to the depot, leading to inaccurate timings and missed details
Ofgem emergency response data is unreliable, and you cannot accurately analyse response performance
The Solution
How Digital Checklist Helps
Digital checklists with GPS route tracking, standardised inspection forms, real-time completion timestamps, and photo evidence capture for all field activities
Every patrol is tracked, every inspection is standardised, and every emergency response is documented in real-time with accurate timestamps
Use Cases:
- • Pipeline patrol route tracking with GPS verification
- • Leak survey coverage documentation with detection results
- • Governor maintenance checklists with safety feature verification
- • Pressure regulator inspection and testing records
- • Emergency response documentation with real-time timestamps
- • Meter installation safety checks and compliance verification
Feature Screenshot
Digital Checklist
Real-World Examples
Example 1: Pipeline patrol and leak survey routes are recorded on paper that gets wet, damaged, or lost before it reaches the office for filing
Real Scenario
"A gas escape causes an explosion. HSE requests patrol records for the affected pipeline section. The paper patrol sheets for that month were water-damaged and are illegible."
Example 2: Governor maintenance checklists vary between engineers, with some checking all safety features and others taking shortcuts under time pressure
Real Scenario
"A district governor fails to relieve excess pressure, over-pressurising a low-pressure network. Investigation reveals the relief valve wasn't checked during the last three maintenance visits because it wasn't on the engineer's checklist version."
Example 3: Emergency response documentation is completed hours after the incident when engineers return to the depot, leading to inaccurate timings and missed details
Real Scenario
"Ofgem challenges your emergency response performance data. When you investigate, you discover response times were estimated from memory hours after incidents, and many are significantly understated."
Staff Training
Gas engineers require specific competencies for different work types including emergency response, mains work, and service installation - deploying engineers without current qualifications creates serious safety and regulatory risk
The Problems
Why This Matters for Gas
- Gas engineer competencies for different work types are tracked on spreadsheets that aren't updated when training is completed or qualifications expire
Engineers are deployed to work they're not qualified for, or qualified engineers aren't utilised because their credentials aren't visible
- National Grid Emergency Responder training and assessment isn't systematically tracked, with refresher training often overdue
Emergency responders aren't current on procedures, increasing the risk of errors during high-pressure emergency situations
- New engineers complete initial training but there's no structured verification that they can apply competencies in real-world situations
Newly trained engineers make errors in the field because classroom knowledge doesn't translate to practical competence
The Solution
How Staff Training Helps
Learning management system with work-type competency tracking, automatic certification expiry alerts, assessment workflows, and training matrix reporting for all gas qualifications
Every engineer has verified current competencies for their assigned work, with automatic alerts before any certification expires
Use Cases:
- • Emergency responder certification and refresher tracking
- • Polyethylene welding competency management
- • Meter installation and exchange qualification verification
- • Mains replacement team competency matrices
- • Confined space and excavation safety training
- • Gas detection equipment competency assessment
Feature Screenshot
Staff Training
Real-World Examples
Example 1: Gas engineer competencies for different work types are tracked on spreadsheets that aren't updated when training is completed or qualifications expire
Real Scenario
"A mains replacement team includes an engineer whose polyethylene welding certification expired three months ago. When a weld fails and causes a leak, HSE discovers the competency lapse."
Example 2: National Grid Emergency Responder training and assessment isn't systematically tracked, with refresher training often overdue
Real Scenario
"An emergency responder mishandles a gas-in-building situation, delaying evacuation. Investigation reveals their emergency response assessment was 18 months overdue."
Example 3: New engineers complete initial training but there's no structured verification that they can apply competencies in real-world situations
Real Scenario
"A newly qualified engineer incorrectly installs a service valve, causing a leak that isn't detected until a customer reports a gas smell days later."
Safe Supplier
Gas distribution relies on specialist contractors for mains replacement and connection work - Gas Safe registration and appropriate accreditation are mandatory requirements that must be continuously verified
The Problems
Why This Matters for Gas
- Mains replacement and connection contractors are engaged without systematic verification of Gas Safe registration, competency schemes, and insurance
Unqualified contractors work on your network, creating safety risks and regulatory exposure when incidents occur
- Contractor safety documentation requirements vary by work type, but there's no systematic way to ensure the right documents are obtained for each job
Safety documentation is incomplete, and you cannot demonstrate contractor competence for specific work packages
- Multiple contractors working on network reinforcement projects aren't coordinated, leading to confusion about safety responsibilities at interfaces
Safety incidents occur at handover points between contractors because responsibilities aren't clearly documented
The Solution
How Safe Supplier Helps
Supplier portal with Gas Safe registration verification, competency scheme accreditation checking, insurance validation, and work package safety documentation requirements
Every contractor is verified qualified before work begins, with automatic alerts when registrations or accreditations approach expiry
Use Cases:
- • Gas Safe registration verification and scope checking
- • GIRS/EUSR accreditation validation
- • Contractor insurance certificate review and limit verification
- • Pre-start safety documentation collection
- • Subcontractor approval and qualification chain verification
- • Contractor safety performance monitoring and review
Feature Screenshot
Safe Supplier
Real-World Examples
Example 1: Mains replacement and connection contractors are engaged without systematic verification of Gas Safe registration, competency schemes, and insurance
Real Scenario
"A contractor causes a major gas escape during mains diversion work. Investigation reveals their Gas Safe registration had been suspended three months earlier for previous safety violations."
Example 2: Contractor safety documentation requirements vary by work type, but there's no systematic way to ensure the right documents are obtained for each job
Real Scenario
"Ofgem audits your contractor management. They identify that 25% of contractor work packages lack the required pre-start safety documentation."
Example 3: Multiple contractors working on network reinforcement projects aren't coordinated, leading to confusion about safety responsibilities at interfaces
Real Scenario
"Two contractors working on adjacent mains sections both assume the other has completed isolation. When one begins cutting, they cut into a live main because neither actually completed the isolation."
Action Tracker
Gas utilities face stringent regulatory timeframes for defect repair, Ofgem improvements, and HSE notices - missing deadlines results in enforcement action and prosecution risk
The Problems
Why This Matters for Gas
- Pipeline defects and repair requirements identified during surveys are logged but not systematically tracked to ensure repair within required timeframes
Known defects remain unrepaired beyond regulatory timeframes, creating safety risk and regulatory non-compliance
- Ofgem improvement requirements and HSE enforcement notices aren't tracked centrally, leading to missed deadlines and escalated enforcement
Regulators escalate enforcement action because you fail to meet agreed improvement timelines
- Post-incident actions agreed during investigations aren't systematically implemented, allowing the same incidents to recur
Repeat incidents demonstrate failure to learn from previous events, increasing regulatory scrutiny and prosecution risk
The Solution
How Action Tracker Helps
Centralised action tracking with owner assignment, regulatory deadline monitoring, automatic escalation, and evidence upload for action closure verification
Every action has a clear owner and deadline, regulatory deadlines are tracked centrally, and escalation ensures nothing becomes overdue
Use Cases:
- • Pipeline defect repair tracking with regulatory timeframes
- • Ofgem improvement requirement monitoring
- • HSE enforcement notice response tracking
- • Post-incident action implementation verification
- • Mains replacement programme progress tracking
- • Audit finding resolution and evidence upload
Feature Screenshot
Action Tracker
Real-World Examples
Example 1: Pipeline defects and repair requirements identified during surveys are logged but not systematically tracked to ensure repair within required timeframes
Real Scenario
"A pipeline coating defect requiring repair within 6 months is logged on a spreadsheet but forgotten. Two years later, corrosion at that location causes a leak that leads to HSE investigation."
Example 2: Ofgem improvement requirements and HSE enforcement notices aren't tracked centrally, leading to missed deadlines and escalated enforcement
Real Scenario
"HSE issued an improvement notice requiring enhanced emergency response procedures within 3 months. The notice was filed locally and the deadline passed without action, resulting in prosecution."
Example 3: Post-incident actions agreed during investigations aren't systematically implemented, allowing the same incidents to recur
Real Scenario
"A third similar excavation damage incident in 12 months triggers an HSE review. They discover that actions from the first incident investigation were never completed."
Document Vault
Gas utilities must maintain extensive pipeline and asset documentation for regulatory compliance, emergency response, and operational safety - systematic document management is essential for safe operations
The Problems
Why This Matters for Gas
- Pipeline records including as-built drawings, pressure test certificates, and material specifications are scattered across multiple systems and paper archives
When you need pipeline information for emergency response, repairs, or investigations, finding the right documents takes hours or they cannot be located
- Governor station records including maintenance history, settings documentation, and test certificates aren't maintained in a single accessible location
Maintenance engineers cannot access previous maintenance records, and settings changes aren't documented systematically
- Ofgem requires retention of operational records for specified periods, but document retention policies are inconsistent and unenforced
Documents are either retained indefinitely at significant cost, or disposed of prematurely and unavailable when needed
The Solution
How Document Vault Helps
Centralised document management with pipeline asset linkage, version control, retention policy automation, and mobile access for field teams
Every document is stored once, linked to the relevant assets, accessible from the field, and retained according to regulatory requirements
Use Cases:
- • Pipeline as-built drawings with GPS reference
- • Pressure test certificates linked to pipeline sections
- • Governor station maintenance history and settings
- • Emergency response procedure documentation
- • Ofgem regulatory submission archive
- • Material specifications and safety data sheets
Feature Screenshot
Document Vault
Real-World Examples
Example 1: Pipeline records including as-built drawings, pressure test certificates, and material specifications are scattered across multiple systems and paper archives
Real Scenario
"During an emergency excavation, engineers need to confirm pipe material and depth. The as-built drawings for that section cannot be located, forcing speculative excavation that delays response."
Example 2: Governor station records including maintenance history, settings documentation, and test certificates aren't maintained in a single accessible location
Real Scenario
"A governor is found with incorrect pressure settings. Nobody can determine when the settings were changed or by whom because documentation is fragmented across paper files and spreadsheets."
Example 3: Ofgem requires retention of operational records for specified periods, but document retention policies are inconsistent and unenforced
Real Scenario
"A legal claim relating to a property excavation damage from 7 years ago requires production of work records. The records were disposed of after 5 years under an informal policy."
Incident Reports
Gas distribution networks must report certain incidents to HSE and Ofgem, and demonstrate systematic learning from incidents - robust incident management is essential for regulatory compliance and network safety improvement
The Problems
Why This Matters for Gas
- Third-party damage incidents during excavation are underreported because crews fear blame for failing to protect the network
You cannot identify excavation damage hotspots or engage with problem utility companies because you don't have accurate incident data
- Gas escape investigations are completed locally but findings aren't systematically analysed to identify network-wide issues
The same types of escapes recur across the network because learning isn't shared between regions
- RIDDOR-reportable incidents aren't identified quickly enough, particularly for injuries to contractors or members of public
HSE prosecutes for late RIDDOR reporting separately from the underlying incident
The Solution
How Incident Reports Helps
Mobile incident reporting with automatic RIDDOR assessment, structured investigation workflow, root cause analysis, and cross-network trend identification
Every incident is captured immediately, RIDDOR requirements are automatically identified, and lessons are shared across the entire network
Use Cases:
- • Gas escape investigation with root cause analysis
- • Third-party damage incident reporting and hotspot analysis
- • Emergency response performance documentation
- • RIDDOR determination and HSE notification workflow
- • Contractor incident reporting and investigation
- • Network-wide safety alert generation and distribution
Feature Screenshot
Incident Reports
Real-World Examples
Example 1: Third-party damage incidents during excavation are underreported because crews fear blame for failing to protect the network
Real Scenario
"Analysis reveals that third-party damage incidents are significantly higher in one area. Crews had been quietly repairing minor damage without reporting it, masking a systematic coordination problem with a specific contractor."
Example 2: Gas escape investigations are completed locally but findings aren't systematically analysed to identify network-wide issues
Real Scenario
"Three different regions experience similar service pipe failures over 12 months. Each investigates independently without knowing the others had similar issues, delaying identification of a material defect."
Example 3: RIDDOR-reportable incidents aren't identified quickly enough, particularly for injuries to contractors or members of public
Real Scenario
"A contractor injury during mains work isn't reported to HSE because the incident wasn't escalated from the contractor to your team in time. HSE adds reporting prosecution to their investigation."
Temperature Monitoring
Gas pressure reduction causes temperature drops that can affect equipment operation in cold weather - continuous monitoring enables proactive response to prevent icing and supply interruption
The Problems
Why This Matters for Gas
- Pressure reduction equipment generates low temperatures that can cause ice formation and equipment failure, but temperature isn't monitored continuously
Ice blockages occur in regulator equipment during cold weather, causing pressure problems and potential supply interruption
- LNG storage tank temperatures and pressures aren't monitored with automatic alerts, relying on periodic manual checks
Temperature or pressure excursions aren't detected quickly enough, risking tank safety and LNG losses
- Governor station heating systems aren't monitored, and failures are only discovered when ice forms on equipment
Heating system failures cause regulator icing and pressure problems, affecting supply to customers
The Solution
How Temperature Monitoring Helps
Continuous temperature monitoring for governor stations and LNG facilities with automatic alerts, trend analysis, and integration with control systems
Temperature excursions are detected immediately with automatic alerts, enabling rapid response before equipment failure or supply problems
Use Cases:
- • Governor station downstream temperature monitoring
- • LNG tank temperature and pressure tracking
- • Regulator preheating system performance monitoring
- • Telemetry room environmental monitoring
- • Equipment enclosure temperature tracking
- • Cold weather alert and response coordination
Feature Screenshot
Temperature Monitoring
Real-World Examples
Example 1: Pressure reduction equipment generates low temperatures that can cause ice formation and equipment failure, but temperature isn't monitored continuously
Real Scenario
"A district governor ices up during a cold snap, reducing pressure to the downstream network. Customers experience low pressure before the problem is identified and heating equipment is deployed."
Example 2: LNG storage tank temperatures and pressures aren't monitored with automatic alerts, relying on periodic manual checks
Real Scenario
"An LNG tank pressure relief valve activates overnight, venting significant LNG to atmosphere. Morning checks reveal a cooling system failure that occurred hours earlier."
Example 3: Governor station heating systems aren't monitored, and failures are only discovered when ice forms on equipment
Real Scenario
"A governor station heater fails on a Friday evening. The icing problem isn't discovered until Monday when customers report low pressure, by which time extensive ice formation requires emergency response."
Audit Trail
Gas utilities face potential prosecution for safety failures that may be investigated years after the event - a complete audit trail is essential for defending against allegations and demonstrating systematic safety management
The Problems
Why This Matters for Gas
- Pressure changes and network operations are logged but there's no complete audit trail linking authorisation, execution, and outcome
When problems occur following network operations, you cannot reconstruct exactly what happened and whether correct procedures were followed
- Changes to emergency procedures and operating instructions aren't tracked with version control and change justification
When procedures prove inadequate during incidents, you cannot determine when they were last reviewed or why changes were made
- Ofgem and HSE investigations may examine events from years ago, but complete records of activities, decisions, and approvals don't exist
You cannot defend against allegations because you cannot prove what actually happened or who made which decisions
The Solution
How Audit Trail Helps
Complete audit trail of all system activities including network operations, procedure changes, approval workflows, and compliance activities with timestamp and user identification
Every action is recorded with who, what, when, and why - providing complete reconstructibility for any regulatory investigation
Use Cases:
- • Network pressure change authorisation and execution logging
- • Emergency procedure version control and change tracking
- • Mains work permit approval and closure audit
- • Competency assessment and authorisation sign-off records
- • Document review and approval workflow tracking
- • Investigation timeline reconstruction from system records
Feature Screenshot
Audit Trail
Real-World Examples
Example 1: Pressure changes and network operations are logged but there's no complete audit trail linking authorisation, execution, and outcome
Real Scenario
"A pressure increase causes customer appliance problems. Reconstructing what happened requires piecing together control room logs, field communications, and SCADA data across multiple systems."
Example 2: Changes to emergency procedures and operating instructions aren't tracked with version control and change justification
Real Scenario
"An emergency response is criticised for procedural gaps. Investigation reveals the procedure was changed 18 months ago but nobody can explain why certain steps were removed."
Example 3: Ofgem and HSE investigations may examine events from years ago, but complete records of activities, decisions, and approvals don't exist
Real Scenario
"Three years after a gas explosion, HSE examines your pipeline maintenance decisions for that section. Your records are incomplete and you cannot prove the maintenance approach was appropriate."
Results Gas Businesses Achieve
Other Utilities Solutions
Fuel Your Compliance Excellence
Join gas utilities using Assistant Manager to maintain safety and regulatory standards.