Getting Pre-Incident Plans Into the Cab: Mobile Access When It Matters

Why a Plan Nobody Can Reach Is No Plan

Departments invest real hours building pre-incident plans. Crews walk buildings, note hydrant locations and flows, mark standpipe and sprinkler connections, log hazardous materials, capture floor layouts, and record contacts for the property. That effort pays off only if the information reaches the people who need it at the moment they need it, which is almost never at the station and almost never after the incident.

The classic failure is the binder. It sits on a shelf, it is a year out of date, and the one building you get called to at 0300 is the one whose page is missing. Even a well maintained binder cannot be paged through by a firefighter riding backward in a moving apparatus. The shift the fire service has been making, unevenly and over years, is from paper stored somewhere to data that follows the call into the cab.

The window is short. Most of what a pre-plan can change happens before the first line is pulled: which side to approach, where the closest adequate hydrant is, whether there is a known collapse or chemical hazard, where the alarm and utility shutoffs live, and who to call. If the officer cannot glance at that during the response or in the first minutes on scene, the plan did not do its job.

How Plans Actually Get to the Cab

There is no single way plans reach the apparatus, and the right answer depends on what your CAD, your mapping, and your devices already support. The common paths are these.

• CAD integration. When a call is created, the dispatch system attaches or links any pre-plan tied to that address or premises, and it surfaces on the mobile data terminal alongside the dispatch. This is the tightest coupling because the plan arrives automatically with the call, but it depends heavily on your specific CAD vendor and how premise records are keyed. Verify what your system supports locally.
• Mapping layers. Plans, hydrants, and hazards render as selectable layers on the responding map. Crews see markers along the route and tap for detail. This is strong for spatial data (hydrants, access points, staging) and weaker for long-form content like contact lists and floor-by-floor notes.
• Standalone apps and web tools. A dedicated pre-plan application on the tablet or phone that crews open and search by address or name. This decouples the plan from CAD, which makes it easier to maintain but means someone has to remember to open it.
• Documents pushed to the device. The lowest-tech version: PDFs or images synced to a tablet folder. Better than a binder because it travels, but it lacks search, structure, and any guarantee of being current.

Most departments end up with a blend. What matters is that the officer's path to the right plan is short and predictable, and that the crew has practiced it so it is muscle memory rather than a scavenger hunt during a working incident.

Offline Is the Whole Point

The single most important requirement for mobile pre-plans is that they work when the data connection does not. Coverage drops in rural districts, in the concrete cores of large buildings, in basements and parking structures, and during large incidents when many devices compete for the same congested towers. Those are exactly the conditions where you most need the plan, so a system that only works with a live connection fails when it matters.

Practical offline design means the plans are cached on the device ahead of time, not fetched on demand. The device should hold current copies of the plans for your response area (and ideally your mutual aid area) so they open instantly with the radio's data light off. Syncing happens opportunistically when connectivity returns, not as a prerequisite to opening a plan.

• Cache the whole response area, not just favorites. You do not get to choose which building burns, so the offline set should cover everywhere you might be dispatched, plus automatic and mutual aid.
• Include the images. Floor plans and site photos are usually the largest files and the first thing a network-dependent system drops. If the diagram will not load offline, the plan is gutted.
• Show the crew how fresh the cached copy is. A visible "last synced" indicator tells the officer whether they are looking at current data or a copy from three weeks ago.
• Do not let a login screen become the wall. If the device demands a fresh server authentication to view a cached plan, offline access is theater. Sessions need to persist through dead zones.

Standardize the Layout So Crews Read Fast

Under stress, people read less and read worse. A pre-plan that is a wall of freeform text will not get read in a moving rig. The plans that actually get used share a predictable structure so the officer's eye lands on the same information in the same place every time, regardless of who built the plan.

Decide as a department what a plan contains and in what order, then enforce it. A workable core set includes construction type and occupancy, primary and secondary access, hydrant and water supply detail, fire protection systems (sprinkler, standpipe, connection locations), known hazards (structural, chemical, electrical), utility shutoffs, and current contacts. Put the life-safety and tactical items at the top, not buried below a paragraph of history.

• Lead with what changes the first two minutes. Access, water, hazards, and building systems belong above narrative detail.
• Use consistent labels and symbols. A hydrant marker, a hazard flag, and a Knox or key-box note should look the same on every plan so crews do not relearn the legend each call.
• Keep each field short and scannable. Bulleted facts beat paragraphs. The plan is a reference to glance at, not a document to study.
• Make the diagram legible at a glance. Clear orientation, a north arrow, labeled entrances, and a simple color scheme matter more than architectural precision.

A standard template also makes the plans faster to build and far easier to maintain, because everyone knows what a complete plan looks like and can spot what is missing.

Keeping Plans Current and the Garbage-In Problem

A mobile pre-plan is only as trustworthy as its worst wrong detail. If crews learn that the hydrant marked on the plan has been dead for two years, or that the listed contact retired, they stop trusting the whole system and fall back on instinct. One confidently displayed error does more damage than a missing plan, because a missing plan prompts caution while a wrong one prompts confident bad decisions.

Buildings change. Occupancies turn over, tenants store new chemicals, contractors add or remove walls, sprinkler systems get taken out of service, and phone numbers go stale. A plan captured once and never revisited decays quietly. The fix is a review cycle, not a one-time build.

• Set a revisit interval. High-hazard and high-occupancy targets deserve more frequent review than a small commercial strip. Many departments tie pre-plan review to inspection schedules; confirm what your local requirements and adopted standards call for and verify against them.
• Capture changes from the field. The crew that just walked a building at an alarm call is the best source of corrections. Give them a fast way to flag "this is wrong" so the update actually happens instead of dying as a hallway comment.
• Date every plan. A visible last-reviewed date lets the officer weigh how much to trust it, and it makes stale plans easy to find and work through.
• Treat construction and demolition as triggers. A permit, a renovation, or a change of occupancy should push that building's plan to the top of the review queue.

Who Owns Maintenance

Pre-plan programs stall when maintenance is everyone's job and therefore no one's. The plans get built during a grant-funded push or a motivated officer's tour, and then that person moves on and the data freezes. Sustainable programs name an owner and build the work into the routine rather than relying on enthusiasm.

There is no single correct owner, and it depends on how your department is organized. Common arrangements include a fire prevention or inspections division that folds pre-plan review into occupancy inspections, a training or operations officer who coordinates company-level target hazard walk-throughs, or a distributed model where each company owns the plans in its first-due area. Each works; the failure mode is when no one is named.

• Name a program owner. One person or role accountable for the plans existing, being reviewed, and being reachable, even if the actual walking is distributed.
• Distribute the fieldwork. Company-level ownership of first-due targets spreads the load and builds crew familiarity with the buildings they will actually respond to.
• Build it into a schedule. Tie reviews to inspections, to training cycles, or to a rotating list so the work is calendar-driven rather than mood-driven.
• Close the loop on field corrections. Someone has to receive the "this is wrong" flags and actually make the edit, or crews stop sending them.

Training Crews to Pull and Use Them

A perfect, current, offline-capable pre-plan system is worthless if the crew does not reach for it. This is the step departments most often skip. They buy the technology, build the plans, and then assume officers will use them, which does not happen on its own under load. Pulling and reading a plan has to be trained until it is reflex.

• Make it part of the response routine. Pulling the pre-plan should be as automatic as putting on a seatbelt and donning gear. It belongs in the normal cadence of a response, not as an extra step someone remembers.
• Assign the reading. On a staffed apparatus, define whose job it is to open and relay the plan (often the officer or a specific seat) so it is not left to chance.
• Drill it on real buildings. Run response drills where the crew pulls the actual plan for the actual target and talks through what it tells them. This tests the plan, the device, and the habit at once.
• Make walk-throughs double as training. When crews build or review a plan by walking a building, they are also learning the building. That familiarity is half the value.
• Debrief with the plan open. After incidents at a pre-planned building, review whether the plan was pulled, whether it was right, and what it missed. That feedback both improves the data and reinforces the habit.

Privacy and Security on Mobile Devices

Pre-plans concentrate exactly the information you would not want to lose control of: building vulnerabilities, alarm and access details, key-box and utility locations, hazardous material inventories, and private contacts for property owners and facility managers. Putting that on tablets and phones that ride in vehicles and occasionally get lost or stolen raises real obligations. The convenience of mobile access and the sensitivity of the data pull against each other, and both matter.

• Control the devices. Department-managed devices with encryption, screen locks, and the ability to be wiped remotely if lost are the baseline. A pre-plan library on an unmanaged personal phone is a harder problem.
• Limit access to those who need it. Access to plans should be tied to identity and role, so a lost device or a departed member does not equal an open library forever. Sessions should be revocable.
• Mind sensitive premises. Some occupancies (schools, certain government or infrastructure sites, shelters, private residences with medical or protective concerns) carry heightened sensitivity. Decide who can see those and handle them accordingly.
• Know your local rules. Public records law, data protection obligations, and any agreements with property owners about how their information is stored and shared vary by jurisdiction. This is a place to check with your legal or records authority rather than assume, and to verify locally.
• Balance lockdown against access. Security that makes the plan hard to open in a dead zone at 0300 defeats the purpose. The goal is protecting the data without breaking the offline, fast-access core the whole program depends on.

Takeaways

• A pre-plan only has value if the right building's plan reaches the responding officer in the window between dispatch and arrival; measure the program by that, not by how many plans exist.
• Plans reach the cab through CAD integration, mapping layers, standalone apps, or pushed documents, and most departments blend them; the details vary by vendor and CAD, so test on your own devices and verify locally.
• Offline access is non-negotiable, because coverage drops exactly where and when you need the plan most; cache the whole response area, images included, and prove it works in airplane mode.
• Standardize what a plan contains and in what order, lead with access, water, hazards, and building systems, and keep every field short and scannable for reading under stress.
• Currency is the program: a wrong detail displayed with confidence is more dangerous than a missing plan, so run a real review cycle and let the field flag errors fast.
• Name an owner and build maintenance into a schedule; distributed company ownership of first-due targets spreads the load and builds familiarity.
• Train the habit of pulling and reading the plan until it is reflex, and protect the sensitive data with managed devices and role-based access without breaking fast offline access.