A risk row names an uncertain event that could affect a named objective. An aspects row names how an activity interacts with the environment. Those are different tasks. A fully described row can still be untreated. You may propose a follow-up before evidence exists. A verified treatment needs evidence that the action was implemented.

Keep activity-environment rows on the aspects register. Read the strategy guide that names a risk log as an input. Check a public sentence before a risk is advertised as managed.

What this log records that the aspects register does not

The 16 August 2023 US TAG clarification on ISO 14001:2015 says risks and opportunities are not the same as significant environmental aspects. The note is used only for that distinction. It does not verify 2026 clauses.

The same activity may appear in both files. Do not copy an aspects row into this file. Completing a risk row is not residual-risk acceptance, not insurance, and not ISO 31000 certification. ISO 31000:2018 is published guidance and cannot be used for certification.

row_status is incomplete or recorded and describes record completeness only. recorded needs event_description, objective_affected and owner. treatment_status is untreated, proposed, started or verified. A recorded row can still be untreated. proposed allows a follow-up such as asking for billing terms while existing_control and evidence_reference stay blank. verified needs evidence that the action was implemented. Missing event, objective or owner keeps the row incomplete even if someone types verified.

Fill in one event row

Download both files. Save a copy of the blank file and type into that copy.

The files are plain CSV. They do not score likelihood. Columns: risk_id, event_description, objective_affected, source_of_uncertainty, existing_control, evidence_reference, likelihood_note, consequence_note, treatment, treatment_status, owner, review_date, row_status.

Likelihood and consequence notes are the organisation’s own words. There is no official matrix.

Worked example: one proposed follow-up

The example is fictional. Northgate Services is invented.

Row What was written Status
NS-R1 recharge breakdown Event: the landlord stops providing a consumption and period breakdown on the electricity recharge. Objective: keep a comparable 12-month kWh record. Treatment: ask the landlord or managing agent for billing terms that keep kWh and period. Owner office manager. Review 16 April 2026. Existing control and evidence blank. Recorded and proposed. The event threatens the kWh record, not only a price change.
NS-R2 climate change No event, no objective, no owner. Incomplete.

If someone types verified while evidence is blank, the treatment is still only proposed.

Limits

Do not claim ISO 31000 certification. Do not turn this file into a legal compliance register. An untreated or proposed row is not a public reassurance.

Your next action

Review untreated and proposed rows in the working group.

Sources