ISO 14001:2026 Clause 8.2 sets six obligations. Most environmental management systems discharge four of them well. Two go missing consistently — periodic testing of the planned response, and providing information to interested parties outside the organization — and they go missing for a structural reason rather than a careless one.
Both are the only obligations in the clause whose evidence is created by an activity that has to be scheduled against production, or against somebody else's calendar. Writing a plan can be done at a desk. Testing it cannot, and neither can getting the fire service to walk your site.
This is a complete Clause 8.2 procedure written to close both. Thirty-one pages, editable Word format, with a worked fictional organization throughout and bracketed placeholders only where a value is genuinely yours to set.
Clause 8.2 c) requires action appropriate to the magnitude of the emergency and the potential environmental impact. Almost every procedure collapses this into a single undifferentiated plan, which is calibrated either to the worst case — expensive, and therefore ignored — or to the ordinary case, which fails on the day it matters. This one defines three tiers with stated conditions and a named decider, and draws the boundary at the point a receptor is threatened rather than reached. Sites that draw it at "reached" consistently discover that the middle tier never gets declared.
ISO 14001 asks for a process and for information to relevant interested parties. It does not tell you to send your plan to the fire department, and it sets no threshold. Regulation does both, and these duties are consistently absent from environmental management systems because no clause checklist points at them.
Appendix D covers RCRA large quantity generator preparedness under 40 CFR 262 Subpart M, the submission duty at 40 CFR 262.262 — which requires the contingency plan and a quick reference guide to be sent to local responders, and resent on every amendment — SPCC under 40 CFR 112, and EPCRA Section 304 release notification. With an applicability determination table, because your obligations are yours to determine.
The line most often missed. Organizations revise the contingency plan properly and then nobody re-sends it. The submission log at Appendix D.2 exists because that failure is almost universal and entirely invisible until someone asks for the acknowledgment.
Not a requirement of any clause, which is exactly why nobody writes it. A compactor fire is extinguished promptly and well within the team's training — and nine hundred liters of firewater run to the yard drain, because the plan treated fire as a safety event and containment as a spill event, and no single plan owned the case where fighting a fire creates a release. Appendix C carries that worked example in full, alongside a four-liter seep whose exposure had nothing to do with the four liters.
Environmental managers, EHS leads, and consultants at ISO 14001 certified or certifying organizations. Particularly useful where the existing procedure was written to the 2015 edition and has not been revisited, where emergency planning sits with a safety function that does not own the aspects register, or where a site holds regulatory contingency plans that have drifted apart from the ISO procedure.
Already certified to ISO 14001:2015? Our ISO 14001:2026 transition course covers the edition changes clause by clause. It is relevant only if you hold a current 2015 certificate — if you are implementing for the first time, build to the 2026 edition directly and skip it.
This template is also included in the full documentation packages, which bundle the procedure set for a standard at a lower cost per document:
Prefer to be invoiced? If your organization purchases by purchase order or requires an invoice, contact us at 760-434-9141 or toll-free 888-914-9141, or through msi-international.com, and we will raise one. Templates are delivered on receipt of payment.
A completed procedure. The decisions are already made and explained, with bracketed placeholders only where a value is genuinely yours to set — your test frequencies, your named roles, your retention periods. Every placeholder is a decision you must make, and the document says so. There are no blank records tables and no "TBD" entries.
Yes. It is supplied in editable Word format and licensed for internal use at any number of your own sites. Replace the fictional organization with your own, insert your own document number, and issue it as a controlled procedure. Resale, redistribution, or use in consulting deliverables for third parties requires a separate consultant license — contact us if that is what you need.
No, and no document can. A procedure is conformant when it reflects what your organization actually does and when the records it calls for exist. What this gives you is a structurally complete starting point, so the work is adapting decisions rather than inventing them from a blank page.
Most templates restate the clause. The standard says test the planned response; the template says "the planned response shall be tested." Nothing has been added. This one names the test types, states what each proves, requires findings to be recorded including what did not work, and explains why a test record with no findings is worth less than no record at all.
Microsoft Word (.docx), fully editable, with the header and footer document control blocks already built. Download is immediate on purchase.
Management Systems International, LLC is a veteran-owned and female-owned ISO consulting firm, co-founded in 1998. Across 28 years we have supported 80+ certifications, attended 200+ audits, and trained 600+ professionals. These templates encode what recurs across those audits — not one organization's approach generalized, but the structural patterns that show up again and again.
msi-international.com · 760-434-9141
