Incident Logging Page

Incident logs are one of the simplest ways to improve spill prevention, response times and compliance. A good log turns every spill (and near miss) into usable evidence: what happened, why it happened, what worked, and what must change before it happens again.

If you also need to meet reporting duties, your log provides the factual timeline regulators and insurers expect (what, where, when, how much, who was notified, and what controls were used). See our Reporting requirements and Regulatory Compliance pages for related guidance.

How to Use Logs for Future Prevention

Evidence logs are not just historical records; they are instrumental in shaping future policies. By analysing the data collected over time, local authorities can:

• Identify patterns: Recognise recurring issues or high-risk areas that may require targeted interventions.
• Enhance training: Use insights from past incidents to inform training programmes for staff, ensuring they are better prepared for future spills.
• Develop preventive measures: Implement strategic changes to infrastructure or processes to mitigate the risk of similar incidents happening again.

What an Incident Log Should Capture

For spill and leak events, the most useful logs include enough detail to support investigation, corrective actions and (where relevant) statutory reporting. HSE guidance explains that certain workplace incidents and dangerous occurrences must be reported under RIDDOR, and record-keeping is part of that duty.¹

Recommended minimum fields

• Unique reference: Log ID, site name, department, and exact location (including drain reference if applicable).
• Date and time: Time discovered, time contained, time cleared, and when operations resumed.
• Substance details: Product name, hazard notes (from SDS), and whether it was oil-only, chemical, coolant, fuel, food oil, etc.
• Estimated quantity: Best estimate (litres/kg), plus method used to estimate (container size, area covered, absorbents used).
• Cause and contributing factors: Equipment failure, handling error, housekeeping, weather, blocked drain, inadequate bunding.
• Immediate controls used: Drain covers, socks/booms, pads/rolls, leak diverter, shut-off, isolation and signage.
• People and safety: Injuries/exposure, first aid, PPE used, evacuation/cordons.
• Environmental pathway: Did it reach a drain, watercourse, soil, or leave the boundary?
• Notifications: Who was notified internally and externally, with times and reference numbers.
• Waste and disposal: Waste type, containers used, contractor details (if used), consignment/transfer note references.
• Corrective actions: What will change, who owns it, due date, and verification evidence.
• Attachments: Photos, CCTV stills, maintenance tickets, SDS, training records.

Suggested Log Layout (Copy-and-Use Template)

This layout works well on an “incident logging page” because it is quick to complete during a response, but still structured enough for later analysis.

Turning Logs into Prevention: Practical Analysis

Once you have 10–20 entries, trends start to appear. Review monthly (or after any significant incident) and use simple groupings:

• Hotspot mapping: Sort by location to identify repeat areas (loading bays, IBC stores, pump rooms).
• Substance grouping: Separate fuels/oils, coolants, chemicals, and food oils to target the right controls.
• Root cause themes: “Hose failures”, “overfilling”, “poor bund housekeeping”, “forklift impact”.
• Time-of-day patterns: Shift change, delivery windows, cleaning periods, planned maintenance.
• Effectiveness scoring: What contained fastest and cleanest? What led to rework or escalation?

Use the outputs to update your spill response plans and align with your broader spill management best practices.

Training Improvements from Real Incidents

Logs are most valuable when they feed directly into skills and behaviours. Convert your top repeat causes into short toolbox talks, and use photos from your own site (where appropriate) to make training “real”. You can also link learning outcomes to your internal training approach on Serpro’s spill training page.

External Reporting and Escalation

If a spill presents a risk to the environment or human health, reporting routes may apply. GOV.UK advises that if there’s a risk to the environment or human health you should call the Environment Agency incident hotline (24-hour service).² For workplace incidents, HSE guidance explains when incidents are reportable under RIDDOR and how to report them.¹

Always follow your organisation’s escalation process and document decisions in the log (including “not reported” and why). For practical response steps and planning, see Emergency response guidelines and Emergency Planning Resources.

Data Quality and Retention

• Keep it consistent: Use drop-downs for substance type, location and cause wherever possible.
• Record near misses: A small leak contained early can reveal a future major failure point.
• Close the loop: Do not treat an entry as “complete” until corrective actions are verified.
• Store securely: Keep personal data to the minimum needed for safety and compliance (see Health and safety for related context).

Need Help Setting Up Your Incident Logging Process?

If you want a practical set of spill logging fields aligned to your site layout and spill risks, contact our team and we can point you to suitable controls and documentation options: Contact Serpro.

Sources

1. HSE: RIDDOR – Reporting of Injuries, Diseases and Dangerous Occurrences Regulations
2. GOV.UK: Report an environmental problem (Environment Agency incident hotline)
3. NetRegs: GPP21 Pollution incident response planning (guidance)