Environmental Compliance Obligations Register Template

What a compliance obligations register is for

An environmental compliance obligations register turns requirements into a controlled working record. It should show what applies to the organisation, where the requirement came from, which activities or environmental aspects it affects, who owns it, what controls are in place and how the organisation checks compliance. It is not a generic list of laws and it is not legal advice.

This guide is part of the Environmental Aspects and Impacts hub. For the wider system context, see What Is ISO 14001? and Environmental Aspects Register Example Entries. The ISO 14001 template pack provides the workbook and connected documents.

What the AuditReady workbook contains

The inspected ISO 14001 pack includes EMS-LOG-11 Compliance Obligations Register - ISO14001 Template.xlsx. It has three useful views:

• Compliance Register for the detailed record of each obligation.
• Obligation Index for a concise management view.
• Permits and Licences for authorisations, conditions, renewal dates and related actions.

The workbook includes document-control information such as the template owner, issue date, revision and storage location. It also warns that the organisation must determine its own applicable obligations and obtain competent advice where needed. That warning matters: a template can structure the work, but it cannot decide which laws, permits or commitments apply to a particular site or activity.

The pack also includes EMS-PROC-12 Legal Compliance Obligations Procedure, EMS-FRM-10 Compliance Obligations Evaluation and EMS-AUD-12 Legal Compliance Obligations Audit Checklist. These documents support the register without replacing the organisation's applicability decisions: the procedure sets out the controlled approach, the evaluation form records the review and evidence, and the audit checklist helps test whether the process is operating.

Field-by-field template guide

Obligation ID and category

Give each entry a short, unique ID so it can be referenced from audits, environmental aspects, objectives, corrective actions and management reviews. Categories might include legislation, regulation, permit, licence, regulator requirement, customer commitment, landlord requirement or voluntary commitment. Use categories consistently so the register can be filtered and reviewed.

Legislation, regulation, permit or commitment

Record the exact title or reference of the requirement and identify the source. Avoid copying a list from another organisation without checking its jurisdiction, activities and sites. If an adviser, regulator or subscription supplied the information, record enough source detail for someone else to find and verify it.

Jurisdiction and issuer

State the country, region, local authority, regulator or other issuing body. The same activity may be subject to different requirements in different locations. A clear issuer field also helps the organisation monitor changes and know where to seek current information.

Applicable activities and environmental aspects

Describe the activity, process, product, service, site or aspect affected by the obligation. For example, a waste requirement might apply to maintenance, packaging or a particular contractor, while a discharge condition may apply only to one site or process. Linking the register to the environmental aspects register review makes the relationship visible.

Specific requirements

Write what the organisation must actually do in practical language: obtain or maintain an authorisation, follow a handling condition, keep a record, complete a report, monitor a parameter, notify an authority or retain evidence. Do not turn this field into an unverified legal summary. Where wording or interpretation is uncertain, mark it for competent review.

Controls in place

List the procedures, inspections, operational controls, contractor checks, training, monitoring or document reviews that support compliance. Controls should describe how the requirement is managed in practice, not simply repeat the name of a procedure. If an obligation is not yet controlled, say so and link the gap to an action.

Evidence reference

Point to controlled evidence rather than writing “records available”. Depending on the obligation, evidence may include a permit, licence, waste transfer record, monitoring result, inspection log, training record, regulator correspondence, audit result or corrective-action record. Use a stable document reference or storage location so another reviewer can retrieve it.

Responsible role and compliance status

Assign a role rather than relying only on a named person. Roles remain clear when staff change and make escalation easier. Keep status precise and honest, such as compliant, action required, under review, not applicable, expired or awaiting confirmation. Do not mark an obligation compliant merely because a procedure exists; check whether the control operates and evidence is available.

Evaluation and action fields

Use the last and next evaluation dates to make review frequency visible. Record any change identified, the action required and the corrective-action or improvement reference. This prevents a new legal update, expired permit or missed evaluation from being buried in a notes column.

Using the three workbook sheets

The Compliance Register is the detailed control record. Review it with the people who understand the activity and the evidence, not only with whoever maintains the spreadsheet.

The Obligation Index provides a shorter view with the obligation title, issuer, owner, review dates, status, source or access location and notes. It is useful for management review and for checking whether the register has owners and review dates.

The Permits and Licences sheet records the permit or licence ID, activity, authority, site or scope, issue and expiry dates, conditions or reporting requirements, responsible role, renewal lead time, status, evidence location and actions. This view helps prevent an organisation from knowing that an authorisation exists but missing a condition or renewal date.

A practical review cycle

Start by listing the activities and environmental aspects in scope. Identify possible obligations from competent advisers, regulator sources, permits, contracts, customer requirements and relevant internal commitments. Record the source and applicability decision for each item. Then assign an owner, identify controls and link the evidence that demonstrates those controls.

Set a review date that matches the risk and the way requirements change. Revisit the register when activities, sites, equipment, contractors or permits change, and when a regulator or other source issues an update. During evaluation, record the result and any action rather than overwriting history. Feed significant gaps into the organisation’s corrective-action and improvement process.

Common mistakes to avoid

Do not treat the register as a one-off legal inventory. It needs owners, controls, evidence and review dates.

Do not pre-populate legal requirements from a generic example without checking the organisation’s jurisdiction, scope and actual activities.

Do not leave the evidence field blank when the control is expected to operate. A missing reference may indicate that the control is not implemented or that the record is not retrievable.

Do not put overdue actions only in free-text notes. Use the action and corrective-action reference fields so they can be tracked and reviewed.

Related resources

Use the ISO 14001 Pack for the compliance obligations register, evaluation form, legal compliance procedure and related environmental management documents. For a separate register-focused example, see the environmental legal register template. You can also review the Environmental Aspects and Impacts cluster or visit the free ISO templates page for a sample.

Before closing a register review

Before closing a review, use the workbook to confirm that each applicable obligation has a source, an owner, a control, retrievable evidence, a current status and a next evaluation date. Then check the permits and licences view for expiry dates and conditions, and record any gap in the action fields rather than leaving it only in notes. This keeps the detailed register, management index and authorisation review aligned.