Obligation evidence guide
Turn Every Obligation Into an Owned Evidence Trail.
A useful obligation register connects the source, due rule, owner, work, evidence, review and submission outcome. Software coordinates the trail; qualified people decide what the source requires and whether the response is sufficient.
Build from sources, not a copied spreadsheet
Start with the granted right, permit, approval, agreement, law, regulation, regulator direction, management plan or contractual commitment that creates the obligation. Preserve the source file, issuing body, identifier, jurisdiction, effective dates, version and retrieval date. Then link each interpreted obligation back to the exact clause or location.
Do not treat one country's template as an African default. For example, the South African Government's mining-right service page describes conditions in that specific national process. It does not establish requirements for Ghana, Zambia, Tanzania, Côte d’Ivoire or any other jurisdiction. Each country and instrument needs independent validation.
Use a controlled obligation record
For each requirement, capture enough structure to support scheduling and review without erasing the legal interpretation:
- source, clause reference, original wording and approved interpretation;
- applicable entity, right, site, area, activity and responsible function;
- trigger, frequency, calculation rule, due date, time zone and non-working-day rule;
- named accountable owner, contributors, reviewer and required segregation of duties;
- required action, evidence standard, submission channel and authority acknowledgement;
- status, risk or priority, dependencies, escalation route and approved exception;
- source version, interpretation reviewer, approval date and next review trigger.
Map the full evidence lifecycle
- Identify: inventory governed sources and record who is authorised to interpret each one.
- Interpret: convert the source into a reviewable obligation while preserving the original language and uncertainty.
- Plan: assign work, dependencies, lead time and resources before the due date becomes urgent.
- Perform: collect source evidence with provenance; do not mark complete merely because a task checkbox changed.
- Review: test completeness, period, scope and authority against an approved evidence standard.
- Submit: preserve the exact submitted package, channel, timestamp, sender and receipt or acknowledgement.
- Reconcile: record regulator responses, corrective work, superseded sources and the next recurring instance.
The OECD's Handbook on Environmental Due Diligence in Mineral Supply Chains presents a risk-based process that includes identifying and assessing impacts, preventing or mitigating them, tracking results and communicating how impacts are addressed. That framework can inform evidence design, but it does not replace binding permits, local law or regulator instructions.
Decision checklist
- Can a reviewer move from dashboard status to the exact source clause and current interpretation?
- Are due dates generated from an approved rule, with manual overrides justified and audited?
- Does “complete” require the right evidence and reviewer rather than an attachment of any kind?
- Are submission packages immutable or versioned, and are receipts separate from internal task completion?
- Can the team identify obligations affected by a source amendment, ownership change or site transition?
- Can confidential, personal, community or legally privileged evidence use narrower access and retention rules?
Test failures before rollout
Use fictional records to test a late source amendment, a disputed interpretation, missing evidence, an unavailable owner, a rejected submission, a recurring obligation generated twice and a date rule spanning time zones or non-working days. Confirm that reminders do not substitute for accountability and that exceptions remain visible until an authorised resolution is recorded.
Limitations
No generic workflow proves compliance or authority acceptance. Legal meaning, accountable roles, evidence sufficiency, retention and submission rules change by jurisdiction, instrument and fact pattern. Maintain a documented country-pack approval process and revalidate sources at defined triggers. Never encode draft research as a production obligation without qualified approval.
Continue the obligation review
Review the tenure and obligation workflow, the trust evidence questions, and the implementation acceptance model before selecting a controlled first scope.