Features / Environmental Permits
Environmental permits, on the same connected record as your safety program.
Most facilities carry their environmental permits in a folder of spreadsheets, a filing cabinet, and a renewal date someone hopefully remembers. SE makes a permit a first-class record — connected to the same platform as your incidents, hazards, inspections, and audit packets. Industrial stormwater discharge permits and air operating permits — Title V, state minor source, synthetic minor — live on one portfolio dashboard: which are active, which renewals are coming due, which have open follow-up work, and how each is performing against its discharge benchmarks or emission caps. Open any permit to see its discharge points or emission units, the latest results with exceedances flagged automatically, its inspection history, and any open corrective work. Maryland and Delaware permit terms come built in; the rest of the country is added as customers bring it.
Permit portfolio dashboard
Every permit, every facility, on one screen.
The portfolio dashboard rolls up every permit within your reach — stormwater and air alike — into a single view. Across the top: how many permits you hold, how many are active, how many renewals are coming due, how many carry open corrective work, and how many of those are overdue. Below that, one row per permit — its status, the days remaining until expiration, how many discharge points it covers, and when it was last inspected. The compliance officer who used to reconcile this from a spreadsheet now reads it at a glance and clicks straight into whatever needs attention.
Renewals that surface before they lapse
Each permit carries its renewal lead time, so a renewal that is coming due shows up on the dashboard — and on the unified compliance calendar — well before the expiration date, not the week after an inspector notices. A permit inside its renewal window wears a clear "renewal due" marker so it never hides in the list.
Open follow-up work, counted
The rollup separates permits with open corrective work from permits where that work is already overdue, so a multi-facility manager sees where the real exposure is without opening every record. Each permit row carries its own open-item and overdue counts.
The stormwater permit module against Apex Manufacturing demo data — the multi-facility portfolio, then one permit's discharge points, a benchmark sample with its exceedance flagged automatically, and the open corrective action on a tracked, escalating lifecycle.
Discharge points + sampling
Lab results that flag their own exceedances.
Open any permit and the detail view lays out everything the permit governs: its issuing agency, coverage type (general or individual permit), the receiving waterbody, the effective and expiration dates, and the inspection cadence. Below the header sit the permit's discharge points, its recent benchmark sample results, its inspection history, and its corrective actions — the whole picture on one page instead of four binders.
Discharge points as structured records
Each outfall is its own tracked record under the permit — not a free-text note. The detail page lists every discharge point the permit covers and how many are active, so the team sampling in the field knows exactly what the permit obligates and where.
Benchmark exceedances flagged automatically
Every sample captures its parameter results against the benchmark limits in force for that permit. When a result lands above (or below) its benchmark, the platform flags the exceedance on the sample itself — and the permit's recent-sample list carries an exceedance count, so a high result is visible the moment it is recorded rather than at the next quarterly review.
Air operating permits
Reported emissions against the permit's caps, continuously.
Air operating permits — Title V, state minor source, synthetic minor — live on the same permit record as stormwater. An air permit carries its emission units, its permit conditions, and its emission limits; the team records reported emissions per pollutant per period, and the permit detail answers the question every air manager carries in their head: how close are we to the cap? Semi-annual monitoring-report and annual compliance-certification deadlines land on the same compliance calendar as everything else.
Emission units and conditions as structured records
Each emission unit is a tracked record — description, control device, rated capacity — and each permit condition is catalogued by type (emission limit, monitoring, recordkeeping, reporting, operational) under its citation-style condition code. An emission-limit condition carries the pollutant, the cap, the unit, and the averaging period, so the permit's obligations are data, not a PDF someone has to re-read.
The cap panel answers "how much room is left?"
For every active emission limit, SE sums the reported emissions inside the limit's own averaging window — rolling 12-month, calendar-year, permit-year — and shows the total against the cap with a percent-of-cap reading. A pollutant approaching its cap is flagged before it exceeds, and an exceedance opens its corrective action automatically. Records whose units don't match the limit are excluded and counted — never silently converted.
Corrective action
An exceedance opens its own corrective action.
A benchmark exceedance is the start of an obligation, not the end of one — so SE doesn't wait for someone to notice a red badge. When a recorded sample result exceeds its benchmark, or a reported emission total tips over a permit cap, the corrective action opens automatically: stamped with what triggered it (the sample or emission record, the parameter, the discharge point) and a due date from the jurisdiction's timeline. From there each action moves through a clear lifecycle — open, in progress, completed (or cancelled, with the reason on record) — with a tiered escalation level mirroring Maryland's accelerated-implementation structure. Overdue actions surface on both the permit detail and the portfolio rollup.
The response clock starts itself
The action opens the moment the bad number lands — carrying the triggering record and the parameter, with the deadline set from the jurisdiction's corrective-action timeline. Recording the same result twice never duplicates the action, and an action already being worked is never re-opened. Closing one is always a human decision; SE never auto-closes follow-up work.
A lifecycle, not a status field
Corrective actions move forward through defined states; the platform stamps the completion date when the work closes and keeps the cancellation reason when one is abandoned. Each action carries a tiered escalation level — the same structure Maryland's permits use to escalate accelerated-implementation measures — so a repeat exceedance reads differently from a first one. The history is auditable, not a single editable status that loses its own past.
Built-in jurisdictions
The right deadlines without configuring them.
The work of stormwater compliance is the same shape everywhere — permit, discharge points, benchmark sampling, inspections, corrective action — but the specifics differ by state: who issues the permit, how long the renewal lead time runs, how often inspections are due. SE carries those specifics as built-in jurisdiction profiles. When a permit is issued under a state's program, its renewal lead time, inspection cadence, and issuing agency are set from that state's profile automatically, so the right deadlines surface without anyone keying them in. Maryland and Delaware ship today; additional states are added as customers bring them.
Maryland — MDE
Maryland Department of the Environment coverage for industrial stormwater and air operating permits, with the state's renewal lead times, inspection and reporting cadences, and corrective-action timeline pre-set — and the tiered accelerated-implementation escalation structure reflected in corrective-action levels.
Delaware — DNREC
Delaware Department of Natural Resources and Environmental Control coverage for industrial stormwater and air operating permits, with its own renewal lead times and cadences pre-set — different from Maryland's where the programs differ, and applied automatically per facility.
Inspection day + reporting
Ready for the inspector, the portal, and the annual filing.
Three moments test a permit program: an inspector arriving, a reporting deadline landing, and the annual filing coming due in the December-to-March crunch. SE is built around all three. The single-download inspector audit packet carries a permits section alongside your safety records; a permit's benchmark results export as a discharge-monitoring spreadsheet ready for the state portal; and the annual compliance report composes itself from the records the team kept all year — so the January filing is an output of the year's work, not a separate project.
Permits in the audit packet
When a facility's sites carry permits, the audit packet adds a permits section — current permits, recent visual outfall inspections, the recent sample log with exceedances flagged, open corrective actions, and for air permits the cap-versus-reported verdicts. It rides in the same fingerprinted packet as your incident, hazard, and root-cause records, so an inspector reviewing permits and an inspector reviewing injuries get one document, not two systems.
Discharge-monitoring export
Export a permit's sample results over any date range as a spreadsheet — one row per parameter result, with the benchmark and the exceedance flag carried through. It is built to drop into a state discharge-reporting portal, so the quarterly reporting task stops being a manual re-typing exercise.
The annual report writes itself
One click on the permit composes the annual report for any year. For a stormwater permit: the year's visual inspections, benchmark samples with exceedances, and corrective actions opened and completed, with a certification scaffold. For an air permit: each pollutant's calendar-year total set against its emission limits. Teams that track everything all year stop rebuilding the filing by hand each January — review the content against your permit's own annual-reporting condition, sign, and file.
Documents on the record
The permit document itself, lab reports, photos from the outfall walk, and the as-filed copy of the annual report all attach directly to the permit and its samples, inspections, and corrective actions — so the paper trail lives with the record it belongs to, not in a shared drive.
How it connects
A permit is part of the platform, not a tool beside it.
A standalone permit tracker is one more login, one more export, one more place the data drifts out of date. In SE a permit lives on the same connected record as everything else your EHS team runs. Renewal deadlines land on the same compliance calendar as your annual posting cycle and training renewals. Inspections sit in the same inspection surface as your safety walkthroughs. And the whole stormwater picture flows into the same inspector audit packet as your incidents and hazards.
Compliance calendar
Permit renewals, inspection cadences, air monitoring reports, and annual certification deadlines surface on the same unified calendar as your annual posting cycle and credential renewals — one place to see what is coming due across the whole program.
Inspections — built for the rain
Quarterly visual outfall assessments are captured on a phone-first form designed for the in-the-rain walk — colour, odour, sheen, foam, floating solids as structured pollution indicators — and it works offline, syncing when the inspector is back in signal. The findings feed the permit record and the audit packet.
Audit packet
The permits section rides in the same versioned, tamper-evident audit packet as incidents, hazards, and root-cause records — and the same time-boxed, access-logged secure link can hand it to an inspector without an account.
Coming next
Built on top of the permit record above.
The permit record, portfolio, mobile inspection capture, automatic corrective actions, emission-cap tracking, annual report, audit-packet section, and discharge-monitoring export are shipped and ready to demo. These build on top of them, sequenced by customer demand.
More states, more permit types
Maryland and Delaware are the first two built-in jurisdictions; additional states are added as customers bring them. Stormwater and air operating permits ship today; the same permit record is built to extend to the rest of the cabinet a facility carries — hazardous waste, tanks, spill-prevention plans — on the same per-demand basis.
Direct portal submission
The discharge-monitoring export is portal-ready as a spreadsheet today. Submitting directly to a state's reporting portal — the way OSHA electronic submission already works for injury data in SE — is sequenced behind it.
Continue exploring
More on the SE platform.
Jump into any of the other capability areas.
Talk to us about your environmental permits.
A 30-minute conversation against your operational shape — how many permits across how many facilities, which states, stormwater or air or both, your sampling and inspection cadence, and what an inspector arrival looks like today. We'll walk through what's shipped and the order the rest is landing in.