botminds.aiRequest a demo
SystemEnvironment, Emissions & Regulatory

Permit Condition Compliance

Permit compliance software that keeps the approval word for word, puts the proof in its margin and tests each piece against the condition it has to meet.

See the demoBook a demo
Follow one groundwater condition from 02:14 to 09:12 ↓
The problem

A ticked row in the condition tracker can hide a well nobody sampled

The approval arrives as a long PDF in legal prose. An analyst retypes each condition into a spreadsheet, usually shortened, and works out its due date by hand from triggers such as before startup. Holders do the work, file from their own folders and tick the row.

Nobody has the hours to read each report against the words it answers to, so the tick stands in for proof. A quarterly report can go in on time, be marked done, and still leave out a well. The first person to read that page closely may work for the regulator.

Amendments move dates, sometimes earlier, while the old wording lingers in the tracker. Before an inspection someone spends a week pulling files, and when the project team closes out, its rows keep the names of people who have left.

Built forRegulatory leadsPermit compliance analystsEnvironmental engineersInternal auditors

The Problem Today

A condition counts as met when someone ticks it, and nobody reads the proof against the condition's own words.

706
hours a year to test proof for 1,412 conditions by hand our estimate

Tracked by hand today

  • Conditions
  • Due dates
  • Proof
  • Amendments
  • Dates moved by amendmentAn earlier deadline hides in a new version
  • Holders who have leftProject teams close out; their duties stay

The Solution

  1. Read word for wordEach condition marked in place in the approval, with trigger and holder
  2. Proof collectedReports, logs, lab results and receipts gathered from the plant's systems
  3. Does this prove it?Each word tested against the proof, both sides quoted, even when done
  4. A person rulesThe regulatory lead reads the page and rules; two people sign each notice

Built-in controls

  • The checker must open the proof before ruling
  • Agents never rule, file or mark a condition done
  • Two signatures on every notice to the regulator

What You Get

Each shortfall reaches the regulatory lead with both sides quoted, and each ruling rests on the page itself.

  • Dates from their triggersStartup, first gas and quarter ends worked out for you
  • No condition left unheldProject duties handed over before the team leaves
  • Reports from tested proofAnnual report and inspection pack drafted, then signed
One condition, one morning

Marked done, sent on time, and one well short of what the approval asks

An approval with 173 conditions. Overnight, a groundwater report sent on time is read against condition 47, and the regulatory lead has a ruling to make by lunch.

demoThis plant, its approval, its crew and its counts are sample data.

  1. 0122:00 to 02:14

    38 new pieces of proof overnight, and 4 of them fall short

    Proof collector and proof tester

    The run pulled 38 items from document management, the lab system, the email archive, the plant historian and contractor uploads. Of those, 33 meet the words and wait for the next routine batch, and one unreadable scan goes back to the contractor. Four shortfalls, condition 47 among them, go to the regulatory lead on a five-working-day ruling clock.

  2. 02Start of the day

    The approval opens on the 20 conditions that need a person

    Regulatory lead

    The approval is on screen as it was issued, each condition marked in place with its proof in the margin. One line sums it up: 173 conditions, 9 where the proof falls short, 6 of them marked done, 2 overdue. Met boilerplate folds away without losing its place, and one button says where to begin.

  3. 03Morning

    Three of the four requirements meet. Which wells does not

    Permit compliance analyst

    The tester splits condition 47 into what it asks for. How often, what is measured and when it is filed all meet: the report went in inside the 30 days. Which wells falls short, because Table 4 lists five wells sampled and MW-4 dry. It is 97% sure, quotes both sides and leaves awareness to the lead.

  4. 04Morning

    Page 14 says it in a table: MW-4, dry, no sample

    Permit compliance analyst

    A citation opens the source page with the passage marked: page 14 of the 22-page groundwater report, depth to water 47.6 at MW-4, and the words dry, no sample. The report disclosed the dry well but never called it a failure to meet the condition. The analyst's opening of the page goes on the record.

  5. 0509:06

    Proposed: tell the regulator. The lead cannot sign yet

    Permit compliance analyst, then regulatory lead

    The analyst, who neither holds condition 47 nor marked it done, proposes falls short, tell the regulator. Switched to the regulatory lead, the sign button is greyed out with its reason: open the proof page first. The holder could not have proposed on their own condition, and an analyst cannot sign a ruling at all.

  6. 06Before she signs

    The field note on page 15 records a phone call the same day

    Regulatory lead

    The lead opens the cited pages herself. Page 15 is the field note: total depth 48.0 ft, 0.4 ft of water above the bottom of the screen, too little to purge three well volumes. The crew lead told the plant environmental engineer by phone that day, and that call is one of three dates she can record as awareness.

  7. 0709:08

    Dated from the phone call, the notice is already 70 days late

    Regulatory lead

    The choices come from the records: the day of the call, the day the quarter closed unsampled, and the night the tester found it. She picks the call. The notice condition allows seven days from awareness, and the screen says in red that the notice is 70 days late. Page opened and date recorded, she signs.

  8. 0809:10 to 09:12

    A notice that admits it is late, signed by two people who do not hold it

    Permit compliance analyst, then regulatory lead

    The draft is built from the ruling and the records: what happened, from page 14; when the company became aware, from page 15; and a plain line that the notice is late. Cause and steps come from the field note and the holder's own note, with steps not taken written as not yet done. The analyst signs, then the lead.

  9. 0909:12

    Six minutes of decisions, each line with a name and a time

    Internal auditor

    The trail shows the proposal at 09:06, the ruling at 09:08 with the awareness date and the day the notice fell due, then signatures at 09:10 and 09:12. Agent entries sit beside the people's, back to the overnight run. No entry can be edited or removed, and the auditor exports the evidence without being able to change a thing.

Four more conditions that fell short once the proof was read word by word

Six of the nine shortfalls on the approval had already been marked done by their holders.

Flaring notice 5 h 05 min short

The amended condition wants 24 hours' notice before commissioning flaring. The email went 18 h 55 min ahead; the row was marked done.

An annual report two complaints light

The report listed 14 complaints; that year's complaint log holds 16. Marked done.

A nest survey 11 days before clearing

The condition allows no more than 7 days between the survey and the start of clearing.

Dust control on 6 of 19 dry days

Twice a day in dry weather, says the condition. The log shows 13 days with two waterings and 6 with one.

demoSample data, from the working solution.

Where all 173 conditions stood on the morning of the ruling

168 conditions as issued and 5 added by two amendments, counted from the condition rows.

Met58
Ongoing, with current proof64
Not yet triggered31
Due within 30 days9
Proof falls short of the words6 of them already marked done9
Overdue2
Conditions on the approval173

demoSample data, from the working solution.

Around the approval

Permit compliance across 63 permits, their holders and their dates

Seven more views of the same plant: other permits, holders, dates and the coming inspection.

The condition in its scheduleCondition 47 among its neighbors, the margin beside it: falls short, five of six wells, marked done by the holder, waiting for a ruling.
Shortfalls, with their clocks31 shortfalls across the plant's permits in one queue, with why each falls short, whether it was marked done and when its ruling is due.
Holds before gas comes inDates worked out from triggers. Five conditions hold hydrocarbons first in, two hold first gas, and readiness sign-off stays blocked until each is met.
An amendment that pulled a date forwardAmendment 2 changed 7 conditions and added 3. The revegetation report now falls due a month earlier, so the fresh test shows it overdue.
Duties that outlive the project10 project conditions outlive the team, 3 with nobody since the project's environmental lead left. Holders are proposed by role and accept.
All permits, searched63 permits and 1,412 conditions. A search for a wetland and a distance finds condition 120 and the setback survey behind it.
The inspection pack64 conditions in scope from the inspection notice, the 6 open ones first, each a click from its proof.

demoSample data, from the working solution.

Who proposes, who rules and who signs a notice to the regulator

Nobody signs a ruling or a notice on a condition they hold or marked done.

Permit compliance analyst
Sees
The approval, the word tests and the cited pages
Signs
Proposes rulings and signs notice drafts
Regulatory lead
Sees
The proof page, opened before any ruling
Signs
Rules on each shortfall, records the awareness date, gives the second signature
Plant environmental engineer
Sees
The conditions they hold, and any question about them
Signs
Adds proof and answers questions, never rules on their own
Plant operations superintendent
Sees
What holds hydrocarbons first in and first gas
Signs
The environmental part of startup readiness, once each hold is met
Project close-out manager
Sees
Project conditions that outlive the team
Signs
Proposes handovers, which each new holder accepts
Internal auditor
Sees
Each ruling, opened page and signature
Signs
Nothing; exports the evidence
The agents

None of the approval's seven agents can rule, file or mark a condition done

They read, collect, test, date and draft, each within its limits.

Condition reader

Reads the approval word for word and marks each condition in place, with trigger, timing, filing and holder.

  • Never rewrites the binding words
  • Its list is used only after the regulatory lead signs it
Amendment tracker

Shows each amendment in place and tells an amendment from an explaining letter.

  • Never applies a change on its own
  • Each changed condition gets a fresh proof test
Proof collector

Gathers reports, logs, lab results and receipts by trigger and date.

  • Read only on every source
  • Never marks a condition done
Proof tester

Tests each piece of proof against the words, quotes both sides and says how sure it is.

  • Never rules
  • Accepts no near match on a number
Deadline watcher

Works out due dates from triggers, reminds holders ahead and escalates what is overdue.

  • Never moves a date the regulator set
Handover agent

Finds conditions that outlive their holder or the project and proposes a holder by role.

  • Never assigns a condition; the new holder accepts
Report builder

Drafts notices, the annual report and the inspection pack from tested proof.

  • Never files anything
  • Never writes that the plant complies

The systems the proof is collected from, read only

Read by trigger and date; nothing is written back.

Document managementThe approval, amendments, letters and the reports sent
Lab information systemLab results and chain of custody
Plant historianOperating records behind monitoring conditions
Email archiveNotices given and receipts kept
Contractor uploadsLogs and inspections from construction crews
Survey and mappingSetback surveys and site boundaries

What regulatory leads ask about permit compliance software

What is permit compliance when each condition is tested against its proof?

Permit compliance means meeting each condition of a permit or approval as written, and being able to show it. Here the approval stays word for word, each condition is marked where it sits, and its proof is tested against the condition's own words, even when the holder marked it done. People rule on each shortfall and sign each notice.

How does this differ from permit condition tracking in a spreadsheet?

A tracker holds retyped rows and a tick. Here the binding words stay as issued, the proof sits in the margin beside them, and the proof tester reads it against what, where, how many, when and filed, quoting both sides with the page.

Can an agent rule on a shortfall, file a notice or mark a condition done?

No. Agents read, collect, test, date and draft. An analyst who neither holds nor marked the condition proposes, and the regulatory lead rules only after opening the proof page. Each notice carries two signatures from people who do not hold the condition.

How is the deadline for a notice worked out?

From the day the company became aware, which the regulatory lead records in the ruling from dates in the records, such as a field note. A late notice says it is late, and its cause and steps come only from records, with steps not taken written as not yet done.

What happens when an amendment changes a condition?

It is shown in place, old wording struck and new beside it, and each changed condition gets a fresh proof test, so a date pulled forward shows as due or overdue at once.

Does it help with environmental permit management at inspection and report time?

Yes. The inspection pack lists the conditions in scope, open ones first, each linked to its proof. The annual report is drafted from tested proof and never says the plant complies; people sign it.

Environment, Emissions & Regulatory

Related environmental and regulatory compliance work

All 7 solutions →
Petroleum License Compliance

Ask before the work: every consent, date and duty tied to its clause.

1-min demoStakeholder Commitments Register

Promises found, owned and proved, even after the person who made them leaves.

1-min demoEU Methane Regulation Compliance

Sales traced back to their producers, with what cannot be proved yet said plainly.

1-min demo

Start with one approval
and last quarter's reports.

We’ll read your conditions against your own proof and show where ticks stand alone.

Book a demoBrowse solutions