The situation
A coal producer operating both an underground and an open cut mine, with additional assets moving through wind-down and rehabilitation, and a lean Brisbane-based environment team covering all sites, plus site-by-site safety obligations under CMSHA.
The problem, in their terms
Environmental obligations lived in a planner that listed due dates but gave no compliance status and weak reminders, across roughly 15 tenements plus EA conditions, EPBC approvals and PRCP requirements.
Safety obligations under CMSHA were spread across thousands of pages of SHMS documentation, with no live view of where the gaps were.
Assets in different life stages (operating, winding down, rehabilitating) carried different obligation profiles, all tracked the same way.
The deployment
01
Started from their real documents. The existing tenement tracker spreadsheet became the build source for the tenement controls, and a real Environmental Authority was loaded and mapped before kickoff, so the first thing the client saw was their own obligations live in the platform, not a demo dataset.
02
Safety came largely pre-built. The CMSHA framework carried over from prior coal deployments, making the safety side a data-mapping exercise rather than a framework build.
03
Piloted on one asset, all frameworks. Fully mapped to build confidence before rollout, with ownership assigned per control so assignment and reminder emails flowed to the right person from day one.
04
Scope flexed mid-deployment. NGER was swapped out for tenement management when that emerged as the sharper pain. The workflow-to-requirement customisation promise, demonstrated rather than claimed.
What runs now
Obligations across five frameworks tracked with live compliance status, owners and reminders. Documents mapped to the legislative requirement they satisfy. Gaps flagged with clause references.
