What EHS Software Do You Actually Need?

TL;DR: The feature matrix is a trap. Every EHS platform has mobile inspections, corrective actions, and dashboards on the slide. What separates them is which problem they got architected around: governance, regulatory reporting, maintenance economics, form-building, or field execution. Four questions sort it out in about ten minutes. If you want the full category-by-category breakdown with named vendors, we wrote that up separately: EHSTracks vs. other EHS software.

---

Here is how the average EHS software evaluation goes.

Someone builds a spreadsheet. Down the left side, sixty capabilities. Across the top, five vendors. Everyone fills in their column, and because the spreadsheet was written in the language every vendor already uses, almost every cell comes back green. The team picks the vendor with the most green cells, or the one whose salesperson was most responsive, or the one corporate already has a contract with.

Eighteen months later the platform is in place and inspectors are still texting photos to a supervisor, because nobody put the one thing that mattered on the spreadsheet: whether the app works in the back half of the tank farm where there’s no signal.

The spreadsheet didn’t fail because it was incomplete. It failed because it measured the wrong axis. Sixty capabilities that every vendor has can’t tell you anything about which vendor to pick. Only the questions with different answers can do that.

So here are four.

1. What is the thing that is actually broken?

Not “what would be nice.” What is currently costing you sleep?

The honest answer usually lands in one of four places, and each one points at a different category of software:

• “We can’t standardize across thirty sites.” That’s a governance problem. You need an enterprise EHS suite: Cority, Enablon, Intelex, Sphera. One taxonomy, one definition of a recordable, one corporate view. Nothing narrower will fix it, and buying a specialist for one process leaves the other nineteen exactly where they were. Budget for the consulting engagement as carefully as the license, because in this category the services bill often rivals the software.
• “We’re not sure which rules apply to the new unit.” That’s a regulatory intelligence problem. You need an environmental compliance platform: Dakota, Encamp, Mapistry, ERA. Applicability analysis, legal registers, permit obligations, emissions calculations, agency submissions.
• “We can’t get parts to the right technician fast enough.” That’s a maintenance problem. You need a CMMS: MaintainX, Limble, UpKeep, Fiix. Work orders, parts inventory, labor, downtime.
• “We can’t prove the inspection happened.” That’s an execution problem, and it’s the one this company exists for.

Most facilities have more than one of these, and having several problems isn’t the mistake. The mistake is assuming one platform solves all of them equally well, then finding out which one it was really built for after the contract is signed.

2. Do your findings start a clock?

This question does more work than any other, and most evaluations never ask it.

If an inspector finds a problem tomorrow, does a regulatory countdown begin? Under 40 CFR Part 60 subpart VVa, a detected leak requires a first repair attempt within 5 calendar days and completion within 15. Post-storm stormwater inspections run against a window measured from the weather event. Hazardous waste containers carry accumulation limits where the calendar itself does the enforcing.

If the answer is yes, you’ve just eliminated an entire category of software, because a form builder has no idea what a repair clock is.

Worth being precise about this rather than dramatic. Products like SafetyCulture and GoCanvas are genuinely well built, and they digitize a checklist faster and cheaper than anything else on the market. But a form is a document. It holds whatever due date somebody typed into it, and it holds it just as calmly if nobody typed anything. Every safeguard rests on the process discipline of the people using it, which works right up until the month somebody is short-staffed.

The reverse matters just as much. If no clock attaches to your findings and your assets aren’t fixed and mapped, buying regulatory compliance software is an expensive answer to a question you don’t have. Buy the form app. Sleep fine.

3. What happens when the network is not there?

Ask this one adversarially, because “we support offline” is the single least reliable sentence in enterprise software sales.

The right follow-ups are specific:

• Does the complete inspection work offline, or just the form? Photos, new equipment records, instrument calibrations, conditional question logic.
• What happens to a photo captured offline if the app is force-closed before it syncs?
• If a save is retried after a dropped connection, do we get one record or two?

A real architectural difference sits underneath these questions. A cached web wrapper stores a form and hopes. An offline-first application downloads a complete local copy of the facility, including configuration, points, questions, inspection history, calibration data, and images, then treats the network as an occasional visitor rather than a prerequisite. Both get described with the same word on a slide. Only one of them survives a compressor station.

Watch the demo happen with the device in airplane mode. Insist on it. It takes ninety seconds, and they’ll be the most informative ninety seconds of your entire evaluation.

4. Does the software know where the inspector was?

This is the question people are least comfortable asking out loud, so let us be direct about what it is really about.

Pencil whipping means recording an inspection that never physically happened, and it’s no hypothetical. It’s the most common way compliance programs fail, and it almost never comes from bad people. It comes from a technician with forty points left, ninety minutes of daylight, and a system that can’t tell the difference between a valve that got inspected and a valve that got marked.

A completion timestamp and a username prove somebody pressed a button. They say nothing about the physical world.

Location verification changes what the record means. When the system compares the inspector’s GPS position against the inspection point’s recorded location, and demands a written justification before the form opens if they’re outside the permitted distance, you get something a timestamp can never give you: evidence, plus a documented explanation for the times there was a legitimate reason to be somewhere else.

The design point is that it works as a record, not a lockout. Sometimes an inspector genuinely can’t approach the asset. The system’s job is to make sure the record says so, in a report an auditor can read, instead of letting that inspection look identical to every other completed one.

The reframe: narrow is a feature, not a gap

There is a move that happens in every competitive evaluation, and it is worth naming so you can watch for it.

A broad platform will point out everything a narrow one lacks. No incident management. No training records. No ESG module. No carbon accounting. Each of those is true, and each is presented as a deficiency.

But consider what the breadth costs, and who pays for it. Every module a platform carries is a module its interface has to accommodate, its implementation has to configure, and its price has to recover. When a facility buys an enterprise suite for its inspection program, the operational budget ends up subsidizing boardroom reporting features that no field technician will ever open. The inspector, meanwhile, gets an interface designed around a corporate compliance officer sitting at a desktop.

Then the failure arrives, and it has nothing to do with a missing feature. It’s adoption. The most sophisticated analytics dashboard ever built is worthless if the data feeding it got entered from the cab of a truck by someone who gave up on the interface three weeks in.

That’s the real argument for buying narrow: field adoption sits upstream of everything. Data integrity depends on it, dashboards depend on the data, and decisions depend on the dashboards. A platform inspectors will actually use in gloves, in November, with no signal, produces better executive reporting than a platform with better executive reporting.

None of which means missing features don’t matter. It means you should know which features you’re paying for, which ones your field team will ever touch, and which category of problem you’re solving.

What to do with this

Pick your one broken thing from question one. Answer questions two through four honestly. If the answers point at governance, regulatory reporting, or maintenance economics, go buy the right category and don’t let anyone talk you out of it. Us included.

If they point at execution instead, meaning recurring inspections on fixed physical assets, unreliable connectivity, regulatory clocks attached to findings, and a documentation trail that has to survive an audit, then you’re in the category EHSTracks was built for. The full comparison names every alternative and says plainly when one of them is the better buy.

And whatever you evaluate, bring one of your own inspection forms to the demo instead of watching the vendor’s. You’ll learn more in fifteen minutes than the spreadsheet will tell you in a quarter.

FAQ

How do I choose between EHS software categories? Start with the single most painful problem rather than a feature list. Governance and standardization across many sites points to an enterprise EHS suite. Regulatory applicability and agency reporting points to an environmental compliance platform. Maintenance economics points to a CMMS. Proving that recurring inspections happened correctly points to a field inspection platform. Feature lists can’t separate these categories, because every vendor uses the same vocabulary to describe all of them.

Is a general inspection app enough for environmental compliance? It depends entirely on whether your findings start a regulatory clock. Form apps digitize checklists quickly and cheaply, but they hold whatever due date a person types and know nothing about requirements like the 5-day first repair attempt and 15-day completion deadline under 40 CFR Part 60 subpart VVa. If no deadline attaches to your findings and your assets aren’t fixed and mapped, a form app may be exactly the right size.

What does offline-first actually mean in EHS software? An offline-first application downloads a complete local copy of the facility to the device, including configuration, inspection points, questions, history, calibrations, and images, so field work never depends on connectivity. That differs from a cached web wrapper that stores a form and struggles when the connection drops mid-task. Test it by asking the vendor to run the demo with the device in airplane mode.

Why does GPS verification matter for inspections? A completion timestamp and username prove somebody pressed a button, not that anyone visited the asset. Comparing the inspector’s GPS position against the inspection point’s recorded location, and requiring a written justification when they fall outside the permitted distance, produces evidence rather than an assertion. It also documents the legitimate exceptions instead of hiding them among ordinary completions.

Should we replace our enterprise EHS platform to fix field inspections? Usually not. Enterprise suites solve governance problems a specialist tool won’t touch, including incident management, occupational health, training, and corporate reporting. The common pattern is that corporate governance stays where it is, while the inspection and repair execution gap gets solved underneath it at facility level.