Environmental Aspects and Impacts Register Template
Three-page A4 landscape register: activities, aspects, impacts, normal, abnormal and emergency conditions, example severity-by-frequency scoring criteria with a significance rule, existing controls, legal and other requirements, owner and review date. It relates to ISO 14001:2015 clauses 6.1.2 and 6.1.3 (numbers and titles only; not reviewed by ISO).
What's inside
- Register header — site, scope of the register, version, prepared by, date, next full review
- A. Significance scoring criteria (example) — severity of the impact (S) from 1 Negligible to 4 Major, frequency or likelihood (F) from 1 Rare to 4 Continuous; score = S × F, from 1 to 16; the rule used for deciding that an aspect is significant
- B. Operating conditions — N normal, A abnormal and E emergency, with what each means on the register
- C. Register — fourteen columns: reference, activity, product or service and location, aspect, condition, impact (beneficial or adverse), S, F, score, law yes or no, significant yes or no, existing controls, legal and other requirements, owner, review date; two example rows and sixteen blank rows
- D. Sign-off — completed by, reviewed by the environmental lead, approved by management
The scales and the significance rule are examples to replace with your own criteria.
What requires or shapes this record
The register is the record behind two requirements of an environmental management system: knowing which of your activities cause which environmental impacts, and knowing which obligations apply to them. Neither the standard nor any law prescribes a scoring scale, so the scales on the form are an example. The clauses below say what the register has to cover.
- ISO 14001:2015, clause 6.1.2 (Environmental aspects)
The clause asks an organisation to identify the aspects of its activities, products and services that it can control or influence, with the impacts that go with them, considering a life cycle perspective and normal, abnormal and foreseeable emergency conditions. It then asks the organisation to decide which are significant using criteria it sets itself, to keep that information, and to make the significant aspects known across the organisation. Columns activity, aspect, condition and impact hold the first part; section A and the Signif. column hold the second. The standard sets no scale, so the 1 to 4 scales here are an example.
- ISO 14001:2015, clause 6.1.3 (Compliance obligations)
The clause covers the legal requirements and the other requirements an organisation has to or chooses to meet that relate to its aspects, and how they apply to it. The Law column and the Legal and other requirements column link an aspect to the obligation that governs it. The register is not a legal register and does not decide which laws apply to your site.
- 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 numbers cited here are the 2015 ones because the form was built against them. The 2026 numbering was not reviewed, so check the numbers 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 prints a rule for significance (score of 8 or more, or a compliance obligation that depends on the control, or a documented concern). The two example rows show how that rule is applied. Replace the rule and scales with your own criteria and record them with the version of the register.
- Site, scope and version
- Why: A register covers a defined scope. Naming the area, process or activity group and the version lets a reader see what is and is not included.
- Common mistake: One register headed with the company name, so nobody knows whether the storage yard or the contractor's work is covered.
- Activity, product or service and location
- Why: Aspects belong to activities, so the entry starts with what is done and where. The same activity in another building can be a separate row.
- Common mistake: Listing departments instead of activities, which hides non-routine work such as maintenance.
- Aspect
- Why: The element of the activity that interacts with the environment: an emission, a discharge, a use of a material or energy, a waste, a noise or a spill risk.
- Common mistake: Writing the impact in the aspect column ("water pollution") instead of the cause ("washdown water to the drain").
- Condition (N, A or E)
- Why: Normal, abnormal and emergency conditions are separate rows because the controls differ. Emergency rows link to the emergency procedure.
- Common mistake: Recording only normal operation, so start-up, shutdown, maintenance and spills never appear.
- Impact (B or A)
- Why: States the change to the environment, beneficial or adverse. Beneficial impacts are recorded so they are not lost at review.
- Common mistake: Recording only adverse impacts and leaving out, for example, reduced purchased energy from a rooftop array.
- Severity (S) and frequency (F)
- Why: Two 1 to 4 scales with written definitions, so two people score the same row alike. The definitions are on page 1.
- Common mistake: Scoring with the controls assumed to work. Say whether the score is before or after existing controls, and keep to one.
- Score and Law
- Why: Score is S × F, from 1 to 16. Law is Y when a legal or other requirement applies to the aspect, which can make an aspect significant whatever its score.
- Common mistake: Treating a low score as the end of the question for an aspect with a permit limit or a duty to prevent pollution.
- Significant (Y or N)
- Why: The decision the standard asks for, made with criteria written down. The reason is written next to the mark when it is not simply the score.
- Common mistake: Changing the mark in a review without recording why, so the register cannot be explained to an auditor.
- Existing controls
- Why: What is in place today: containment, procedures, maintenance, training, monitoring. Controls are what an auditor checks against the significant aspects.
- Common mistake: Listing controls that are planned or that exist elsewhere in the company but not at this site.
- Legal and other requirements
- Why: The reference to the permit condition, regulation or commitment that governs the aspect, so the register and the obligations can be read together.
- Common mistake: "Environmental law" with no reference, which cannot be checked or kept up to date.
- Owner and review date
- Why: A named person and a date turn the row into something that is maintained. Changes, new products and incidents reopen the row earlier.
- Common mistake: One annual date for the whole register and no trigger for a change in process, material or site layout.
- Sign-off
- Why: Shows who compiled the register, who checked the scoring and who approved it.
- Common mistake: An unsigned register that no one can identify as current.
Worked example
IllustrativeFour register rows for a small workshop and yard (invented site)
| Activity and aspect | Condition | Impact | S × F, Law | Significant, and why; controls |
|---|---|---|---|---|
| Parts washing, bay 2: solvent cleaner vapour and spent liquid | N | Adverse: air emission, waste generation | 2 × 4 = 8, Law Y | Yes (score 8 and a permit condition applies). Lidded tank; spent solvent in labelled drums; safety data sheet at the point of use. |
| Fuel delivery to the yard tank: diesel spill during transfer | E | Adverse: soil and surface water contamination | 3 × 1 = 3, Law Y | Yes by the rule's second limb, although the score is 3. Bunded tank, drain cover, spill kit, attended transfer. |
| Filter change on the same tank: drips to ground | A | Adverse: small release of oil to ground | 2 × 2 = 4, Law N | No. Drip tray and kit used; reopen if frequency rises or the task changes. |
| Rooftop solar array in normal use | N | Beneficial: lower purchased electricity | Not scored in this example | Recorded so the benefit is not lost; the organisation decides whether to treat beneficial aspects as significant. |
Row 2 is why the rule has more than one limb. A spill that is unlikely but would breach a requirement still needs its controls checked, whatever the product of S and F. The scores and rows are invented for illustration.
When a spreadsheet stops being enough
A spreadsheet register holds for one site and one reviewer. It stops holding when aspects have to be tied to the permits, legal obligations and monitoring results that control them, when several sites score against the same criteria, and when a new product, a change or an incident should reopen the affected rows instead of waiting for the annual date.
A software record links each aspect to its obligation, controls and monitoring data, versions the scoring criteria, reminds at the review date and shows significant aspects across sites. Ask whether scoring scales are configurable, and what happens to old scores when you change them. The list below applies the ISO 14001 rule: environmental or ISO management tags plus a sourced aspect, obligation or monitoring capability.
Same rule for every product: tagged “Environmental Management”, “Environmental Monitoring” or “ISO Management”, with a sourced environmental aspect, obligation or monitoring 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
ESdat · Environmental data consolidation · Documented
Vendor source · Profile checked
ERA-EHS · Air emissions modelling and reporting · Documented
Vendor source · Profile checked
Mapistry · Waste manifest tracking · Documented
Vendor source · Profile checked
SoundPLAN · Industrial and workplace noise · Conditional
Vendor source · Profile checked
Acoem (Cadence and Airodis) · AI-assisted noise-source recognition · Conditional
Vendor source · Profile checked
Wastebits · Waste-stream approval and renewal · Documented
Vendor source · Profile checked
Effivity · Environmental aspects and occupational hazards · Documented
Vendor source · Profile checked
Tekmon · GHG emissions calculation · Documented
Vendor source · Profile checked
Cority · Environmental obligations · Documented
Vendor source · Profile checked
Enablon · Environmental aspects, permits and compliance · Conditional
Vendor source · Profile checked
Evotix · Environmental activity records · Documented
Vendor source · Profile checked
IsoMetrix · Environmental performance · Documented
Vendor source · Profile checked
Quentic · Environmental aspect and risk assessments · Documented
Vendor source · Profile checked
SAP Environment, Health, and Safety · Environmental obligations · Documented
Vendor source · Profile checked
SoftExpert · Audits and checklists · Documented
Vendor source · Profile checked
Sphera · Environmental, corporate carbon and product LCA scopes · Conditional
Vendor source · Profile checked
VelocityEHS · Environmental compliance and obligation tracking · Documented
Vendor source · Profile checked
Cirrus Research (NoiseTools and MyCirrus) · Noise exposure and hearing protection · Documented
Vendor source · Profile checked
Lisam · Environmental calculations and regulatory reporting · Conditional
Vendor source · Profile checked
Locus Technologies (Platform / EIM) · Permit obligations and compliance calendars · Conditional
Vendor source · Profile checked
Metegrity Visions Enterprise · Fugitive-emissions and LDAR workflow · Conditional
Vendor source · Profile checked
All 21 matching profiles are shown. Documentation review, not hands-on testing or a claim of compliance.
Related guides
- ISO 14001 Implementation Guide: A 12-Step EMS Roadmap
Article on ISO 14001 implementation.
- Environmental Data Software: Samples, Lab Imports and Amendments
Software guide on environmental data.
- Water Management Software: Meters, Samples and Reports
Software guide on water management.