About SystemsAnalytix
Most safety and compliance tools treat every incident as an isolated event and every program as a checklist. We build software on the premise that they're not — that failures come from systems, not individuals, and that understanding the system is the only way to manage safety effectively.
Our starting point
When an incident is reduced to just a category, a severity level, and a paragraph of narrative, the organization learns almost nothing it can act on. The same failure mode is just waiting to happen again. Systems Thinking — the discipline behind fields like aviation safety, healthcare quality, and industrial accident prevention — starts from a different premise: that incidents are rarely caused by one bad decision. They emerge from the interaction of factor across an entire system: conditions, pressures, supervision gaps, and design choices that were in place long before anything happened. That's why tracking near misses is just as important as tracking incidents, they are the 'canary in the coal mine' helping you intervene ahead of an incident.
How we think about SAfety
Modern safety science treats root-cause analysis as a starting point, not the final answer — the real explanation is almost always further upstream. HFACS, ICAM, and STAMP/STPA all reach the same conclusion from different angles: individual error is rarely sufficient explanation. Our software is structured to capture the conditions and system-level factors around an incident, not just the narrative of what one person did.
One incident report tells you what happened once. A structured taxonomy of contributing factors across hundreds of incidents tells you what's actually driving your risk. We build for the second kind of insight — the kind that shows up in a trend line, not a single case file.
A rigid, vendor-controlled schema imposes someone else's idea of what matters onto your organization. We build on Microsoft Dataverse specifically so the taxonomy, the workflows, and the data itself belong to you — configurable without code, owned inside your own tenant, never locked behind a vendor's roadmap.
HFACS (Human Factors Analysis and Classification System) — traces an incident beyond individual error, up through the conditions, supervision, and organizational decisions that made it likely. A systems view, not a search for one person to blame.
ICAM (Incident Cause Analysis Method) — separates what people did from the conditions they worked in and the safeguards that failed, so fixes target the system.
STAMP / STPA — a systems approach that reveals how parts of an operation that each worked “as designed” can still combine into an unsafe outcome.
You don’t need to master these to use IncidentAnalytix — it provides the structure. They’re here because a defensible safety program relies on recognized methods, not a free-text “root cause” box.
The Products We Build
Traditional safety management — what resilience-engineering researchers call Safety-I — defines safety as the absence of failure. You count incidents, trace each one to a root cause, and treat safety as a number you're trying to drive toward zero. It's the model most incident systems are built around, and it's necessary. IncidentAnalytix's contributing-factor analysis, built on HFACS, ICAM, and STAMP/STPA, lives squarely in this tradition: when something goes wrong, understand the real conditions behind it, not just the immediate cause.
But Safety-I has a blind spot. On most days, most programs go right — not because nothing risky happened, but because staff adapted, caught a problem early, or made a judgment call that isn't captured anywhere. Safety-II, another paradigm in resilience engineering, treats safety as the capacity you build, before the program, to succeed under real-world pressures. IncidentAnalytix's schema of mitigating factors captures that side of the picture: what capacity was demonstrated when something almost went wrong. Learning from success is equally important to learning from failure.
ProgramAnalytix is where that adaptive capacity gets built before a program ever runs. Staff training, verified equipment, current certifications, clear requirements met on schedule. Safety-II research consistently points to these conditions as what actually determines whether an organization can adapt when something unexpected happens. ProgramAnalytix exists to make sure those conditions are in place before the program starts, are tracked, and provable.
Put together, the two products cover both halves of the risk management equation. IncidentAnalytix tells you what your system does when things go wrong and, increasingly, what it does when people make things go right under pressure. ProgramAnalytix tells you whether the conditions for that adaptive capacity were actually there in the first place. Most organizations manage these as separate problems, tracked by separate offices that rarely compare notes. We don't think that's sustainable — a program that's chronically out of compliance and a program with a high incident rate are probably the result of the same underlying gaps.
Our Technology Choice
Building Software is slow: Building traditional software is time consuming, and as soon as it's done, it's out of date. That is especially true in risk management and safety science. New principals emerge from safety research, but many products are mired in ancient models like root cause analysis because it's too hard to change what they built years ago. They are stuck so you are stuck.
No-code/Low Code is the Future of Software Development: After years of building software in that traditional way, we made the leap to a fully-user customizable, no-code/low-code approach with the Microsoft Power Platform, and we've never looked back. Now our development time is spent on enhancing and adding new features, not stomping out bugs. Building on Microsoft's platform lets us avoid that tradeoff entirely. Every table, every workflow, every security rule lives in Dataverse — in your Microsoft 365 tenant, governed by your own Entra ID, covered by your own compliance certifications.
No Lock-in: We are safety and risk management experts and ship a complete, starting point. But we know that every organization's needs are different. So instead of locking you into one vendor's vision like most SaaS applications, we give you a fully customizable platform to build on to exactly match your needs. Do you need a new table, new forms, custom views, new security roles? Every SystemsAnalytix product ships as a starting point you can extend with the same no-code tools we used to build it, on your own timeline.
Who do we build for?
Helping people run safer programs is our mission. We design for organizations where the cost of getting this wrong isn't theoretical. Outdoor education, youth-serving organizations, higher education, field science and conservation programs, nonprofits — these are organizations where the cost of an unexamined incident or an unmet requirement isn't abstract. It's a person.
