See CompliantMine in action

Here's one Ontario approval with thirty-two obligations in it. So where do they live today?

Let's start with the approval PDF itself. This one's a real, public Ontario air and noise approval, which we'll load against a fictional mine, and then extract.

CompliantMine reads all twelve pages and drafts thirty-two obligations. Each one cites its clause, its page and the exact wording, so you can always check it against the original.

Some conditions only start when something happens. After a complaint, you've got two business days to notify the District Manager, and five to report.

None of this goes live until someone reviews it. Search for complaint, and you'll see the retention condition too: complaint records have to be kept for five years.

When you're happy with a draft, activate it and assign an owner. Here that's Lee Feldspar, so there's no doubt who's responsible for this condition from now on.

So when a complaint does come in, you just log it with the date it arrived. The register works out the rest, and the steps with a deadline now show their due dates.

Reminders run every six hours, or on demand, and owners are emailed the day before a step is due, and again if it's late, with the clause included.

That's every permit condition, tracked to proof. Pilots are open in Ontario, so find us at compliantmine dot com.

You're responsible for three sites and twenty-two permit obligations. So, what's actually late today?

The dashboard puts all three sites and nine permits on one screen, and shows what's coming due, at which site, and who owns it.

Two obligations are overdue across the company. One click opens them, each with its site, its clause and how many days late it is.

Now let's look at the proof behind a single obligation. Here's the permit condition, quoted word for word, and the inspection finding that led to a corrective action.

Four files back it up, each one reviewed and accepted, so when someone asks, the whole story is already in one place.

That's every permit condition, tracked to proof. Pilots are open in Ontario, so find us at compliantmine dot com.

Your approval was issued this week, which means its deadlines have already started.

So you upload the approval PDF, and CompliantMine reads it and drafts thirty-two obligations, each citing its clause and page. We're using a real, public Ontario approval here, on a fictional project.

Take this condition. It says not later than three months, so the suggested due date is counted from the issue date.

None of this goes live until someone reviews it, and the review list puts your first deadlines at the top.

Then, once an obligation is active, its owner gets email reminders fourteen, seven and one day before it's due, with the clause and the date.

That's every permit condition, tracked to proof. Pilots are open in Ontario, so find us at compliantmine dot com.