The command post's screen. The ICS chart, the tasks, the teams and the forms all hang off one call file.
Every call has an operational period at the top: when it started, how long is left, and what the team is trying to get done. Under it are the objectives, the command emphasis, the safety message and the weather.
The ICS chart is filled by choosing people into positions: Incident Commander, Operations, Planning, Logistics, Finance and the units under them. Roll the period over to a new one when it ends.
The briefing is laid out as SMEAC: situation, mission, execution, administration, command. A brief board shows the live picture on a second screen or a TV at the command post, with the call's map, the tasking agency and file number, and the radio channel names (never the frequencies).
The decision log records what was decided and why, and meetings keep their notes. Each ICS section has its own colour, so you know where you are on the chart without reading.
Make a task and drag it onto a team. A task moves from planned to assigned to in field to complete to debriefed, and the time on task is shown on the way. Each team's card shows who is on it, which channel it uses and when it last checked in. A team that is overdue turns red, and a banner tells everyone on the incident team.
The debrief for a task records coverage, probability of detection, clues, hazards and recommendations. There are task types for hasty, area, grid, tracking, K9, drone, swiftwater, rope, door knock and welfare checks.
If you would rather see a plain list by status, switch to it. Each task has the next step on a button: assign, send to the field, complete.
You plan on the map, try things freely, and save when you like the result. Nothing changes for anyone else until you save.
Pick the subject's category (hiker, snowmobiler, child, dementia and so on) and the terrain, and the map draws distance rings from lost person behaviour statistics around the point last seen. Divide the area into segments, give each a starting probability, and update it as teams search with their own probability of detection. You can seed the plan from the rings, weight it by clues, or split it evenly.
Each team has a check-in interval. The team leader can confirm "all accounted for" from the phone in one tap. Mobilization and demobilization record who arrived, who left, and who has got home safe.
Clues go in one log with who found them, where, how important they are and what was done with them. Clue weighting feeds straight back into the search plan.
Start any ICS form from the call and it fills in what the system already knows: the incident, the operational period, the organization, the teams, the people and the resources.
The set is ICS 201, 202, 203, 204, 205, 206, 209, 211, 213 and 214, plus three for searches: 301 subject profile, 305 safety plan and 307 transportation plan. One button starts the whole incident action plan (202, 203, 204, 205, 206 and 307), and you can print it as a package. There are Canadian and US versions of the form set.
The SMEAC briefing is not typed from scratch. It is built from the call as it is right now: the subjects, the objectives, who is assigned where, the hazards, the comms plan, the organization chart and the safety, transportation and medical plans, once they exist. View it, print it, or save it as a PDF.
The incident action plan prints as one package of the forms that make it up, and the operational period report summarizes the period when it ends.
The first page of the incident management screen is a board of big buttons, and it starts with the ones for your position on the chart. The Planning Section Chief sees the action plan, the briefing, search planning, objectives, ICS forms, a clue and the situation report; below that are the things everyone on the team does: a radio log entry, a decision, a note, a resource request, safety and hazards, tasks, accountability and the brief board.
Everyone can open and change every page. Your own section's pages keep their colour and the others go grey, so you can see where you are on the chart without reading.
Add a hazard from a button or draw it on the map: a point for a spot, an area for a region. Each hazard records its type and severity, what to do about it, special instructions, and the protective equipment needed. Hazards marked for briefings flow into the safety messages, the team tasking cards, the SMEAC briefing and the brief board.
The incident management team has a chat of its own for each call, for the people on the chart. Each message shows the sender's ICS position beside their name. Photos and files can be shared in it. When someone leaves the chart they can no longer see it, though what was said stays.
Everyone on the call also has a call chat, and there are direct messages. Chat is not saved to the call file.
Forms a team finalizes that go to a section, such as an evacuation form for Operations, arrive on a page with a count beside the section. Nothing pops up. See disaster response.
Who called whom, on what channel, and what was said, next to the channel plan for the period.
Ask for people, equipment or supplies and follow each request until it arrives.
Pull the weather for the call's location and keep an eye on how it changes.
Hours for everyone on the call, and the expense claims waiting for Finance.