Incident management software
IMT Logic connects your existing plans with real-time incident management, helping teams turn information into coordinated action — a clearer, faster and more coordinated response, whether the team is in the room or spread across three time zones.
The problem
Most organisations already have thorough emergency procedures. What they do not have is a way to run them — so the response falls back on a printed folder, a whiteboard and a spreadsheet that only one person can edit at a time.
What it does
IMT Logic turns your established emergency procedures into a live, adaptable incident management system. Your command structure, your functions, your checklists — loaded as data, not rebuilt as software.
Checklists are layered — a base plan, plus the incident type, plus the site — so one change is made once. Approved versions are frozen, and an incident records which version it ran on.
Every action has an owner, a priority and a target time. Anything past its target flags itself as late, worked out from the clock rather than from anybody remembering to update a status.
A tick in the control room appears on the laptop of the person joining from home in the same second. Lose signal and it resynchronises on its own rather than quietly showing you an old picture.
Taking a position shows you what is still open on it before you accept it. Who held which seat, and between which times, becomes part of the record — a different question from who pressed the button.
Everything is recorded as it happens, with a name and a time against it, and the log is append-only at the database level. That is what makes it worth something in an investigation months later.
Incident commander, section lead, facilitator, observer. Each sees what they should and can change only what they should — decided on the server, so hiding a button is never mistaken for a permission.
The platform
Connecting command, planning, operations, resources and information through a shared Common Operating Picture. The platform is designed to support all of the below. Live is working today and can be demonstrated in a tabletop exercise. On implementation is delivered and configured to your own requirements as part of setting the system up — because a form, a report format or a command arrangement is only useful in the shape your organisation actually uses.
Designed to support both ICS and AIIMS frameworks, with incident forms and records updating dynamically as information changes.
In the platformThe incident structure, roles, priorities and terminology follow ICS, and the action tracker is an ICS 233 in all but name. Specified with youwhich framework your organisation works to, and which numbered forms it uses.
Connect emergency plans, tactical response guides, procedures and pre-incident information directly into the live incident environment.
Maintain a clear, accountable and time-stamped incident record, built to support internationally recognised incident-management, information-security and records-management principles.
Expand or contract the incident-management structure dynamically according to the size, complexity and operational needs of the event.
Support formal establishment and transfer of command, with defined reporting lines, chain of command and unity of command.
Enable multiple agencies, departments or organisations to work toward shared incident objectives while retaining their individual responsibilities and authority.
In the platformOne organisation with one command structure, with defined reporting lines and formal transfer of command. Specified with youhow partner agencies share the incident while keeping their own authority.
Align operational activity around clearly defined, measurable and prioritised incident objectives.
Develop and share Incident Action Plans that bring together objectives, strategies, tactical assignments, responsibilities and operational-period priorities.
In the platformObjectives, strategies, tactical assignments and their owners are planned and tracked in the platform. Specified with youyour own IAP format and operational periods.
Support structured dispatch and deployment so personnel and resources are requested, assigned and tracked through the appropriate command channels.
In the platformActions are assigned to named owners with target times, and go late on their own. Specified with youyour dispatch routes and the channels resources are requested through.
Track personnel, teams, equipment and critical resources throughout mobilisation, deployment, operations and demobilisation.
In the platformPersonnel and equipment are tracked as assigned actions with named owners and target times. Specified with youthe resource categories and states you track, from mobilisation to demobilisation.
Capture accurate, timely incident reports and attachments with built-in security, access controls and audit trails.
In the platformThe incident record is time-stamped, attributed, and cannot be altered after the fact. Specified with youyour report formats, attachments and who may see them.
Maintain a complete record of personnel, assignments, decisions, actions and operational status, supporting clear accountability and seamless handover between personnel, shifts and command teams.
Remote incident management
Site is on the phone, the duty manager is at home, the technical authority is in another country and somebody senior wants to watch without getting in the way. IMT Logic gives all of them the same live picture, with an observer role for the people who should see everything and change nothing.
Exercises and training
An exercise is marked as an exercise permanently, everywhere it appears, and exercise controls are refused against a live incident — so a drill can never be mistaken for the real thing in the record, and a simulated casualty can never be injected into a real response.
Who it is for
IMT Logic is built for operations where an incident has consequences beyond the balance sheet, and where a regulator will eventually ask what was done and when.
Security and information
The record an incident leaves behind is often more valuable than the response itself. It has to still be there, and still be trustworthy, a year later.
The best way to see it
Rather than watch a demonstration, put your own team round a table and run a scenario. You will see the platform doing the job it is built for, and your team gets a useful exercise out of it whether or not you go any further.