It's 11 PM the night before an MSHA inspection. The EHS director is at the kitchen table with a three-ring binder, six months of paper inspection records, a spreadsheet of contractor sign-ins that does not quite balance, and a pot of coffee. The binder gets finished around 2 AM. The inspector arrives at 8.

I have watched some version of that night happen at quarries, asphalt plants, paving operations, and aggregates yards across the northeast and beyond. It happens not because anyone is bad at their job, but because the tools that were supposed to make it unnecessary did not. The audit pack still gets reconstructed manually. The citations still turn on whether the right form was attached to the right record. The platforms that promised to solve this in 2014 are mostly still promising to solve it in 2026.

My name is Jeffrey Reynolds. I'm the Chief Systems Architect at Kinetiq Analytics, and I'm heading the team building Kinetiq Nexus — a new generation of EHS software for industrial sites. This is the first post of what will be an occasional, hopefully honest series about what we're building, what we've gotten wrong, and what we're trying to push forward in a category that has stopped pushing itself.

The short version

I got tired of waiting.

For years I watched EHS programs on the frontlines try to do audit-grade safety work with tools that were not designed for the way the work actually happens. The big-name platforms in the space are functional. They are also expensive, slow to deploy, generally hostile to integration, and built around assumptions that haven't been true since the early 2010s. The inspector still writes on a clipboard. The contractor still signs in on paper. The audit pack still gets reconstructed at 2 AM. Workers carry tablets that crash, kiosks that lock up, and apps that ask them to enter a six-digit pin every shift.

That gap — between what the field actually needs and what the category was shipping — is the one I sat down one day and started chasing. I'd seen enough EHS programs from the inside to have opinions. I started writing those opinions down. Then I started writing the platform. Some of it was straightforward. A lot of it was harder than I expected. Some of it I got wrong the first time and threw away. Most of what this blog is going to be about is that last part — the choices we made, the choices we'd reverse if we started over, and the parts that are working.

What we're building (the very short version)

A handful of things that take EHS work from the audit-prep crisis to the audit-ready posture that EHS leaders actually want:

  • An inspection flow that starts at the asset, not at the form. Tap a card on a kiosk; the asset is bound to the record; no pin entry, no QR-code spoofing.
  • A structured root-cause analysis surface inside the inspection workflow itself. 5-Why methodology, every corrective action tied back to a specific section of the regulation, no inventing references. (More on this in the next post.)
  • Identity that spans the workforce. Federated to Microsoft Entra. Module-level access control, not just role-level. External contractors and auditors get scoped access without a full identity provision.
  • 12 regulated forms — LOTO, MOC, JSA, Hot Work, Confined Space, RPE, Fatigue Risk, Auto-Accident, Equipment Damage, Regulatory Audit, Toolbox Talk, Hours Worked — on one backend, one identity, one audit ledger.
  • Broadcast delivery to the kiosk. Operators push acknowledgement-required notices to every Pulse device on a site; the kiosk holds the broadcast on screen until acknowledged.
  • Federal Safety Indicators benchmarked against MSHA and OSHA datasets, shipped out-of-box, filtered to your mine type, scored at the category level.
  • An analytics engine that reads the incident corpus in natural language, surfaces threshold alerts on category baselines, and produces audit-ready evidence packs.

A lot of that already runs in production at customer sites. A few pieces are on the roadmap and I'll write about them as they ship. Some of what we shipped last quarter, we'd ship differently if we did it over. I'll write about that too.

What this blog is going to be

  • Short. Most posts will be under a thousand words. We are not in the content-marketing business; we are in the EHS business.
  • Occasional. A new post when something is worth saying. No content calendar.
  • Specific. If we say a feature does X, the post tells you what we changed to make X actually work.
  • Honest about what didn't work. Lessons-learned is a real section, not a marketing veneer. The first version of a thing is almost never the version we shipped, and the difference is usually the interesting part.

What it isn't

  • A roadmap promise machine.
  • A "we're excited to announce" newsletter.
  • A place where the worst version of EHS marketing happens.

One more thing

If you're an EHS director, a site lead, an inspector, or anyone who has had to defend an audit pack that wasn't quite ready — this blog is for you. If you're a peer building in this space and want to swap notes, also for you. If you're a competitor — welcome; take what you need; the workers we both serve are bigger than either of us.

The next post is already up. It's a deep-ish look at the structured root cause analysis surface I mentioned above — what it does, what it explicitly does not do, and the one guardrail we treated as non-negotiable from day one. I'd appreciate it if you read it and tell me what's wrong with it.

If you'd rather just talk — the offer is a thirty-minute walkthrough against your actual MSHA inspection history. You bring last year's citations; I'll walk through what the platform would have done. No deck, no demo theatre.

Get in touch

Glad you're here.

— Jeffrey