Why compliance belongs to agents: mining approvals, pharma deviations and expiry tracking
By Vishal Kumar, Founder and CEO · Last updated · 7 min read

In short: Compliance work is long, repetitive and unforgiving. A mine can run for 20 or 25 years with something due every month, quarter and year. One missed rent payment or report can put the tenement at risk. People get tired and forget; software doesn't. AI agents can watch every obligation, collect the evidence, remind the right owner and escalate early, while people keep the judgement and the signatures. We have seen the same pattern in mining approvals, pharma deviations and expiry tracking.
A mine can last 20 or 25 years.
Every one of those years has a calendar full of things to lodge, pay and prove. Miss the wrong one and the whole operation is exposed.
This is how I explained it to someone from a global IT company last weekend:
"If you can imagine mines, they last for 20, 25 years. Every quarter, every month, every year, there's a bunch of stuff to submit. If you miss something out, you can lose your licence overnight."
That's not an exaggeration. In Queensland, rent on mining leases and mineral development licences is due on 31 August. If it isn't paid by then, an extra 15% is payable. And if the rent and penalties aren't paid before 1 December, the Queensland Government says the mining tenement "may be cancelled". [1]
That's one obligation, in one state, for one kind of tenure. A mining company may hold hundreds of tenements across several jurisdictions.
What is tenement management?
A tenement is a mining or exploration title: the legal right to explore or mine a defined piece of land. Each one comes with conditions: rent, reports, expenditure commitments, renewals, environmental obligations and more.
Tenement management is keeping every one of those conditions met, on time, with proof.
Before software, that lived in personal spreadsheets, inboxes and people's heads. When someone went on leave, the knowledge went with them.
What did we build with PX4 Software?
PX4 Software is a mining technology company we work with. I was one of the first coders on the platform.
Together we built a tenement management platform. It brings multi-stakeholder workflows and approvals into one system, with GIS (geographic information system) integration to ESRI and TENGRAPH, reminders, workflow triggers and reporting. [2]
The problem it solved: mining tenement data was held across personal devices and multiple channels. That created security exposure, and made data flows hard to trace. [2]
Today the platform supports more than 60 regulatory jurisdictions across six continents, and delivered 35% cost savings in mining project planning. [2] PX4 is now expanding in the US, and we're helping.
I want to be clear about one thing. The PX4 platform is a compliance platform, not an AI project. It's the foundation that makes agents useful: one place where every obligation, due date and document lives. You can't automate what you haven't organised.
Read the full PX4 Software case study or our mining page.
- 60+
- regulatory jurisdictions supported
- Source: PX4 case study [2]
- 6
- continents
- Source: PX4 case study [2]
- 35%
- cost savings in mining project planning
- Source: PX4 case study [2]
Why does compliance suit AI agents?
Because the work has three properties agents handle well.
It's rule-based. Most obligations come with a clear trigger, a due date and a known set of evidence.
It's high volume and low variety. The same kind of task repeats hundreds of times a year.
It's punishing when missed. The cost of a lapse is far higher than the cost of checking.
And agents don't get tired. We use an internal review agent on client content, and it's caught small mistakes that people scrolled straight past:
"It'll do multiple times and just never gets tired. So even at midnight, if you do it, it'll be like, hey, there's an issue. There's an issue."
A person checking a register on a Friday afternoon is doing their best. An agent checking it every hour is just doing its job.
How do pharma deviations fit the same pattern?
In pharma, the "obligation" is often an event, not a date.
Something goes wrong on the line. Now a chain of steps must happen, in order, with evidence: immediate action, deviation report, root cause analysis, corrective and preventive action (CAPA), approval of any new standard operating procedure (SOP), and training for everyone affected.
For a pharma manufacturer, we designed that whole chain as a workflow on phones and tablets. AI drafts the corrective action from the approved SOP. People review and sign. Every step is recorded in a tamper-evident audit trail.
The pattern is the same as mining: a trigger, a set of required steps, evidence, a named owner and a deadline. The difference is that one starts with a calendar and the other starts with an incident.
The details, including what US FDA 21 CFR Part 11 and India's revised Schedule M expect, are in our article on digital SOPs, CAPA and audit trails.
What about expiry tracking?
This is the most common compliance problem, and the most boring. Which is exactly why it gets missed.
Insurance policies expire. Licences expire. Staff checks expire. Equipment certifications expire.
A partner this week described the problem in childcare. A provider with hundreds of centres has to keep public liability cover, supplier insurance and staff background checks current at every site. Each one has its own date, owner and document.
That's a register problem first and an agent problem second:
- Every item has an owner, an expiry date and the document that proves it.
- The agent checks the register daily.
- Ninety days out, it asks the owner for the renewal.
- It reads the new document when it arrives and checks the dates and names match.
- If nothing arrives, it escalates to a manager, then to leadership.
- Every reminder, reply and document is logged.
| Item | Owner | Expires | Agent reminder | Outcome |
|---|---|---|---|---|
| Public liability cover | Centre manager | June | March (90 days before) | Renewal received and checked |
| Supplier insurance | Procurement | September | June (90 days before) | Renewal received and checked |
| Staff background check | HR | November | August (90 days before) | No reply: escalated to a manager, then leadership |
What is the common pattern across industries?
Strip away the industry words and every compliance system has the same parts:
- An obligations register. What must happen, under which rule, for which asset or person.
- Triggers. A date, an event, or a change in something else.
- Owners. A named person for every obligation, with a backup.
- Evidence. The document, photo or record that proves it was done.
- Monitoring. Something that checks continuously, not quarterly.
- Escalation. A clear path when something is late or unclear.
- An audit trail. Who did what, when, and what changed.
Agents are very good at 2, 4, 5 and 6. People are essential for 3 and for the judgement calls. Everyone needs 1 and 7 to be right.
| Part | Best handled by |
|---|---|
| 1. Obligations register | Everyone needs it right |
| 2. Triggers | Agents |
| 3. Owners | People |
| 4. Evidence | Agents |
| 5. Monitoring | Agents |
| 6. Escalation | Agents |
| 7. Audit trail | Everyone needs it right |
What should never be left to an agent?
Three things.
Signatures. Anything that carries legal weight, such as a lodgement, an approval or a quality sign-off, is signed by a person.
Judgement. If a condition is ambiguous, or a regulator's notice needs interpreting, a person decides.
Uncertainty. If an agent isn't sure, it must say so. I build every agent with an escape route: a third option that hands the case to a person instead of guessing. Without it, an AI will pick an answer even when it's only 60% sure.
The tempting choice and the better choice
a shared spreadsheet of due dates, with a colour code and a monthly check-in. It works until the person who owns it leaves.
one register, with owners and evidence attached, watched by an agent that never forgets and always escalates. The spreadsheet's knowledge moves into a system, and stays when people move on.
This connects to a bigger idea I've written about: a company where agents run the routine and people handle the exceptions. See AGI and the agentic operating system.
Your next step
Which compliance deadline in your business lives in one person's head, or one person's spreadsheet?
Start there. Write it into a register with an owner and evidence. Then let an agent watch it. Get your AI roadmap.
Frequently asked questions
What happens if a mining tenement holder misses a payment in Queensland?
For mining leases and mineral development licences, rent is due on 31 August and a 15% late amount applies after that. The Queensland Government says the tenement may be cancelled if rent and penalties are not paid before 1 December. Check the current rules for your tenure type.
What is tenement management software?
Software that tracks every mining or exploration title, with its conditions, due dates, documents, approvals and map location, so nothing is missed.
Can AI agents submit regulatory filings?
They can prepare them, check them and remind people. In our approach, a person reviews and lodges or signs anything with legal weight.
Is compliance automation only for large companies?
No. Smaller firms often have more to lose, because one person holds all the knowledge. A simple register with automated reminders is a good start.
How is this different from calendar reminders?
A reminder tells you a date is coming. An agent also checks whether the evidence arrived, whether it's valid, and who to escalate to when it hasn't.





