An obligations register (or compliance obligations register) is the central, maintained list of every legal, regulatory, permit, and ESIA commitment an organization must comply with. For each obligation it records the source, the specific requirement, the owner, the deadline or frequency, and the evidence that proves it was met.
What a good obligations register contains
| Field | Why it matters |
|---|---|
| Source document & clause | Traces each obligation back to the permit, ESIA condition, or regulation it comes from. |
| The requirement, in plain language | Turns dense legal wording into something the site team can actually action. |
| Owner / responsible person | Every obligation has a name against it, so nothing falls through the cracks. |
| Deadline or monitoring frequency | Drives reminders: daily, monthly, quarterly, or event-based. |
| Status & evidence | Links the proof (reports, photos, monitoring data) directly to the obligation. |
| Jurisdiction / site | Lets multi-site operators filter by regulator, province, or mine. |
Obligations registers and ISO 14001
ISO 14001 requires an organization to determine and have access to its compliance obligations and to evaluate compliance with them. A register of compliance obligations is the standard way an environmental management system (EMS) meets that requirement, which is why the phrase “register of compliance obligations” comes straight from EMS practice. In mining, the same register also carries permit conditions and ESIA (Environmental and Social Impact Assessment) commitments, which often outnumber the statutory ones.
Why spreadsheets break down
A spreadsheet is where most registers start, and it works until:
- you are reconciling obligations across multiple permits and jurisdictions;
- you need an audit trail of who changed what, and when;
- you have to attach and retrieve evidence under inspection time-pressure;
- ownership and deadlines live in someone’s head instead of a reminder.
At that point the spreadsheet has no link between an obligation and its proof, no reminders, and no defensible history.
How CompliantMine builds your register
CompliantMine is environmental compliance software built for mining operators. It turns your permit and ESIA documents into a live obligations register, keeps the evidence attached to each obligation, generates inspection packs on demand, and tracks CAPA (corrective and preventive actions) to closure, so proving compliance is a click, not a scramble. It does one thing well and is not a document management system, general task manager, ERP, or reporting platform.
Frequently asked questions
Is an obligations register required by ISO 14001?
Yes. ISO 14001 requires organizations to determine, have access to, and evaluate compliance with their obligations. A register is the standard way to do it.
What’s the difference between a legal register and an obligations register?
A legal register lists applicable laws; an obligations register goes further, breaking each law, permit, and ESIA condition into the specific, owned, evidenced actions your operation must complete.
Related:
CompliantMine vs Cority, Intelex & IsoMetrix · More frequently asked questions