Martin Senterfitt
Forty years in emergency management. Type 1 Incident Commander. Hundreds of incidents stood up in operational command.
The doctrine works. The tools didn't.
Martin has spent his career inside the Incident Command System — first as a responder, then as a Type 1 Incident Commander, and now as the co-founder of the platform he spent decades wishing existed. NIMS Logic is the product of a single recurring observation across hundreds of activations: NIMS gave the emergency management community a standardized framework, but nobody built the software to make it real at the field level.
Agency after agency built Incident Action Plans in Word, tracked resources on spreadsheets, and reconstructed FEMA documentation from memory months after demobilization. Every one of those workarounds existed for the same reason: no one had built ICS-native software. Generic project management tools bolted ICS-shaped fields onto a different data model. Legacy EM platforms digitized the paper without respecting the doctrine underneath it.
NIMS Logic exists to close that gap. The platform reflects the architecture of ICS directly — operational period-aware, organizational hierarchy that mirrors ICS 203/204, resource lifecycle tracked from check-in through demobilization, and documentation produced as a byproduct of running operations rather than a post-incident reconstruction exercise.
Would a 40-year IC sign off on this?
Every product decision, platform feature, and piece of editorial content at NIMS Logic is held to the same standard: would a 40-year emergency management veteran and Type 1 Incident Commander sign off on this? If the answer is no, it does not ship.
The test applies as rigorously to the published content on this site as it does to the software itself. Blog posts, pillar pages, and persona pages are written for the reader Martin knows best — an EM director, IMT member, or fire/EMS chief who runs a handful of incidents a year, files FEMA PA claims, and is tired of vendors who do not understand ICS. If a piece of content would not survive scrutiny from that reader, it does not publish.
That is the editorial and operational standard behind everything NIMS Logic ships.
More from Martin
Connect with Martin on LinkedIn
Read Martin's writing on the NIMS Logic Intel blog.
Learn more about the NIMS Logic team and mission.
Ready to upgrade your command capability?
See how NIMS Logic transforms incident management from administrative burden to operational advantage. Real-time visibility. Automated workflows. Complete accountability.