Skip to main content
    qhsetech.com
    All templatesEnvironment · 3 pages · Updated 3 October 2026

    Spill or Release Incident Report Template

    Three-page environmental release report: what, where and when, substance and quantity, receptors and drainage, immediate response, notifications with times and references, cause, clean-up and waste, follow-up actions and sign-off. It relates to ISO 14001:2015 clause 8.2 (number and title only; not reviewed by ISO). Whether a release must be reported depends on substance, quantity and location; the form does not decide that and is not legal advice.

    What's inside

    1. Report details — report number, who reported, phone, date and time, site, status (initial, updated or final), shift or supervisor
    2. What happened, where and when — event type, date and time discovered, started and stopped, exact location, source, who or what was operating, description in order of events
    3. Substance and quantity — name as on the safety data sheet, SDS reference, form, hazards on the label, quantity released and how it was estimated, quantity recovered and not accounted for, concentration
    4. Receptors and drainage — where it went, drain or outfall identifier and whether it was covered, sensitive receptors, weather and ground conditions, people injured or exposed
    5. Immediate response and containment — timed actions with who did them, equipment used, emergency services called
    6. Notifications made — site manager, environmental lead, regulator, sewer or water operator, neighbours, customer, owner or insurer: whether required, date and time, person contacted, reference given, made by
    7. Cause — immediate cause, underlying causes, why it was possible
    8. Clean-up and waste disposal — method and who did it, waste table with quantity, container, class, carrier and transfer note, checks after clean-up
    9. Follow-up actions — actions with owner and dates, documents to update, lessons shared
    10. Sign-off — reported by, supervisor, environmental lead, closed by

    What requires or shapes this record

    A release report has two jobs: to give the people who respond and the people who review a factual timeline, and to feed whatever notification duty applies. Reporting duties differ by country and depend on the substance, the quantity, where it went and the permit you hold, so this page does not tell you whether to report. It explains what the form records so that the decision, and its time, are on the record either way. This is general information, not legal advice.

    • ISO 14001:2015, clause 8.2 (Emergency preparedness and response)

      The clause is about being prepared for the emergencies identified during planning, responding to actual ones, acting to limit the environmental harm, testing the response where practicable, and reviewing and revising it after an incident or a test. This report is the record of an actual response. Section 9 asks whether the emergency procedure, the aspects register or the spill kit arrangements need to change as a result.

    • US EPA, National Response Center (1-800-424-8802)

      EPA's page describes the National Response Center as the federal point of contact for reporting oil, chemical, radiological and biological discharges into the environment anywhere in the United States and its territories, and gives the telephone number 1-800-424-8802. The page does not say which releases must be reported; that depends on the substance and the quantity under the rules that apply to you, which is why section 6 records the decision and the time even when the answer is no.

    • GOV.UK, Report an environmental problem (Environment Agency incident hotline 0800 80 70 60)

      The page, opened on 3 October 2026, lists the Environment Agency's 24-hour incident hotline for England as 0800 80 70 60 and names, among other things, pollution to land and incidents at regulated waste sites. Scotland, Wales and Northern Ireland have their own regulators, and a site's permit may name who to call and when. Section 6 has a row for the environmental regulator and a column for the reference number you are given.

    • ISO 14001:2026 (current edition) and the withdrawn 2015 edition

      ISO's catalogue, opened on 3 October 2026, lists ISO 14001:2026 as published (edition 4) and shows the 2015 edition as withdrawn and replaced. The clause number cited here is the 2015 one because the form was built against it. The 2026 numbering was not reviewed, so check it against the edition your certificate or audit uses. ISO's text is not reproduced on this page.

    Each source checked on 3 October 2026. Not legal advice; check the text in force for your site.

    Field by field

    The form asks for facts in the order they are usually remembered: what and where, how much, where it went, what was done, who was told, why it happened and what changes. It has no field that states a legal reporting threshold, because thresholds differ by substance and jurisdiction. Record the thresholds your permit or emergency procedure uses in that procedure, not on each report.

    Report number and status
    Why: One report is updated as facts come in, so the status (initial, updated or final) tells a reader how complete it is.
    Common mistake: Starting a new report for each update, so the timeline is split across documents.
    Event type
    Why: Liquid spill, leak, vapour release, powder release, overflow and firefighting run-off call for different responses and different follow-up.
    Common mistake: Using Other for fire-water run-off, which is then missed in drainage checks.
    Date and time discovered, started, stopped
    Why: Duration and the time to respond are measured from these three. Notification clocks that apply to you are measured from what you knew and when.
    Common mistake: Entering only the report time, so the duration of the release cannot be calculated.
    Location and source
    Why: An exact location and the named source (tank, drum, pipe, vehicle) let the controls on that source be reviewed.
    Common mistake: "Yard" for a site with three yards and four tanks.
    Substance name, SDS reference, hazards
    Why: The name as on the safety data sheet links to the hazards, the clean-up precautions and the waste classification.
    Common mistake: Using the trade nickname, so the responder cannot match it to a data sheet.
    Quantity released and how it was estimated
    Why: An estimate is only useful with its method. Container volume, a meter reading, flow rate times time and area times depth have different error margins.
    Common mistake: A single number with no method and no figure for what was recovered, so the quantity not accounted for is unknown.
    Where it went
    Why: Bund, hard standing, soil, a surface-water drain, a foul sewer, a watercourse or air each have different consequences and different people to inform.
    Common mistake: Ticking hard standing when a gully drained it to the surface-water system.
    Drain covered or isolated, sensitive receptors
    Why: Records what was protected, when, and what lay downstream: watercourses, abstractions, protected areas, neighbours.
    Common mistake: Recording that a drain was covered with no time, so it cannot be shown to have been covered before the substance reached it.
    Immediate response and containment log
    Why: A timed list of actions with who did them is the timeline a reviewer or regulator will ask for.
    Common mistake: Writing the log afterwards from memory with rounded times.
    Notifications made
    Why: Who was told, when, by whom and under which reference. The Required? column records the decision, including a decision that no external report was needed.
    Common mistake: Leaving the row blank when no report was made, so there is no evidence the question was asked.
    Immediate and underlying causes
    Why: Separates what directly released the substance from why it was possible: a missing check, an unclear procedure, a design weakness, a contractor interface.
    Common mistake: Stopping at "valve left open".
    Waste table and checks after clean-up
    Why: Absorbent, soil and contaminated liquid are waste with their own class, carrier and consignment records, and checks show whether clean-up was enough.
    Common mistake: Putting contaminated absorbent in general waste because the spill was small.
    Follow-up actions and updates needed
    Why: Actions with owner and date, plus prompts to update the emergency procedure, aspects register, spill kit stock and training.
    Common mistake: Actions only for the cleanup crew, with no change to the control that failed.

    Worked example

    IllustrativeDiesel overfill at a yard tank during a delivery (invented site and people)

    SectionEntry
    2 What, where, whenSR-2026-006. Overflow at yard tank T-2. Discovered 07:42 by the driver; started about 07:35; stopped 07:44 when the fill valve was closed.
    3 Substance and quantityDiesel; safety data sheet revision on file in the chemical register. About 180 litres, estimated as the delivery meter reading (2,600 L) less the increase in the tank gauge (2,420 L). 150 L recovered; 30 L not accounted for until the soil check.
    4 Receptors and drainageHard standing, running toward a surface-water drain 12 m away. Drain covered at 07:46. Nearest watercourse about 150 m downstream of the outfall. Light rain. No one injured.
    5 Response07:44 valve closed. 07:46 drain cover placed. 07:50 absorbent socks laid around the drain. 07:55 spill kit absorbent applied. 08:20 vacuum truck called.
    6 NotificationsSite manager told at 07:50. Whether an external report applied was checked against the site permit and emergency procedure at 08:30; the decision, the time and any reference number are written in the regulator row. Sewer operator: not needed, the drain was covered first.
    7 CauseImmediate: tank high-level alarm silenced for testing earlier in the week and not re-enabled. Underlying: no alarm check before a delivery; the procedure does not say who watches the gauge.
    8 Clean-up and wasteAbsorbent and about 40 kg of gravel in two labelled drums, collected by the site's waste carrier; waste class and transfer note number entered on the form. Soil sample taken beside the bund.
    9 Follow-upRe-enable and tag the alarm (maintenance, same day). Add an alarm check to the delivery checklist (yard supervisor). Check where drain covers are kept (environmental lead). Update the fuel delivery row of the aspects register.

    The quantity method matters: if the tank gauge was wrong, 180 litres is wrong too. That is why the form asks for the method and for a quantity not accounted for, instead of one total.

    When a spreadsheet stops being enough

    Paper reports work for occasional events. They stop working when several sites need the same timeline, when a regulator or insurer asks for the time of notification and the reference given, and when waste records and corrective actions have to be traced back to the release that caused them.

    A software record adds a timestamped timeline, notification records with references, photos and sampling results attached to the report, waste records linked to the event and actions tracked to closure; some link releases to the aspects register. Check offline capture, because spills happen in yards and tank farms. The list below applies the spill rule: a matching tag and a sourced spill or environmental-release capability.

    Same rule for every product: tagged “Environmental Management”, “Environmental Monitoring”, “Incident Management”, “Emergency Management”, “Emergency Response”, “EHS Management” or “Chemical Management”, with a sourced spill or environmental-release capability in its record, or one the vendor stated to us, labelled as vendor-stated. Documented and conditional capabilities qualify; check the linked scope before treating a module as included.

    Tekmon pays for a sponsored placement (above); its place in this list follows the same rule as every entry. How lists are ordered

    All 8 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.

    Related guides