MapBook puts your pre-plans, water sources and access boxes on the same map as live 911 dispatch β then alerts your members, shows who is responding, and keeps working when the network doesn't.
Written by a volunteer lieutenant with 20 years in the fire service β’ In daily use at the Clinton Volunteer Fire Department, Clinton, Connecticut

MapBook started as a way to retire the paper map binder. It has grown into the software a department runs its calls on.
Before the call
The pre-plan work your department already does, made searchable, shareable, and current β instead of photocopied and out of date.
Vector maps of your whole response area with streets, satellite and hybrid basemaps. Zoom thresholds keep the map readable β hydrants first, then occupancies, then access boxes β instead of burying you in pins.
Wet and dry hydrants, draft points, cisterns and inground tanks, with flow rate, static pressure, status and inspection dates. Departments define their own supply types and how each one looks on the map.
Building profiles with hazards, tap-to-dial contacts, photos and special considerations. Parent-child structure handles malls, campuses and multi-unit buildings the way they're actually addressed.
Knox boxes and key vaults with box and serial numbers, install and inspection dates, photos, and links to the occupancies they open. Boxes on a parent building show on its units too.
Your own map layers with colors and icons β hazard zones, staging areas, gates, dead-end roads, drafting sites. Anything specific to your district that isn't on a commercial map.
Bring hydrants, occupancies and access boxes in from CSV or GeoJSON, and see a full preview of exactly what will be created and changed before a single row is written.
During the call
Most tools in this category do alerting or mapping. MapBook runs the call β dispatch, alerting, response tracking and radio in one place.
Your dispatch center already sends you every call. MapBook turns those dispatch emails into located calls on the map automatically β call number, type, units and dispatch time come through, and the call is matched to your own occupancy record when it recognizes the address.
Dispatch reaches members' phones through native iOS and Android apps, with the app closed and the screen locked. Android alerts run on a high-importance channel of their own, separate from department messages.
Members mark where they're headed β station, scene, wherever you define β and everyone sees who's coming and how many. Statuses expire on their own so the board never goes stale.
Stream your department's dispatch audio in the app, on the truck or at home. Optionally record it: each transmission is kept as its own clip on a timeline of the day, so you can replay the one you missed. When your tones drop, members get an alert, and each picks which tones they want. Runs on a radio receiver at your station that we supply ready to go.
An always-on wall screen for the apparatus bay. At rest it shows the map and recent alerts; when a call lands it splits to the scene map, the responders coming in, and the dispatch text. Runs on a display box we supply ready to go.
Maps, pre-plans, water sources and calls are cached on the device. Edits and photos queue locally and sync the moment you're back in coverage β no dead screen at the far end of the district.
Running the department
Membership, records and accountability β the questions that come up at budget time and in the after-action, not on the fireground.
Announcements to the whole department, to a group, or to specific members β with push delivery, edit-in-place, and no third-party service injecting text into your dispatch feed.
Flag hydrants for snow removal or repair, report issues, and clear them β individually or in bulk across hundreds at once. Every change is logged with who did it and when.
Log incidents with event timelines, notes and photo attachments, linked to the occupancy they happened at. Every building's call history is on its record.
Optional or department-required two-factor sign-in, plus an audit trail of every change, every login, and every cross-department access β the record security questionnaires ask for.
Granular permissions on top of admin, user and viewer roles, with user groups for stations and companies. Departments are isolated from each other at the database level, not just in the interface.
Native iPhone and Android apps, plus the same screens in any browser β truck computers and station desktops. Nothing to install on an MDT.
MapBook isn't a software company's idea of what a fire department needs. It was written by a volunteer lieutenant with 20 years in the fire service and EMS. Every feature is inspired by real-world experiences while responding to incidents.
How a call actually runs
This is the part that separates MapBook from a mapping app. The call comes in and the system does the work β you just read the screen.
MapBook reads your dispatch center's alert the moment it arrives β no polling, no delay, no third-party service in the middle. The call type, number, units and dispatch time are parsed out and the address is placed on the map.

Members get a native push notification with the app closed and the phone locked. On Android it runs on a high-importance dispatch channel of its own, so a call sounds different from everything else on the phone at 3am.

Members mark where they're headed. The officer sees who is coming and where before anyone reaches the station, and the wall display in the bay shows the same thing to whoever walks in.

If the address matches an occupancy you've pre-planned, the call links straight to it β hazards, contacts, Knox box, photos and the building's own call history, in one tap, on the way.

In the bay
A wall-mounted screen that sits idle showing the district map and recent alerts, then splits to the active scene the instant a call drops β map, responders and the dispatch text, readable from across the apparatus floor.
Pairs like a TV app: the screen shows a code, an admin approves it, done. Any modern 1080p or better TV works, with a MapBook display box behind it that we supply preloaded and configured β no per-screen licence.

Twenty minutes on a call, looking at a department that runs on it every day β live dispatch, real pre-plans, a real district. Ask anything. No obligation and no sales team: you'll be talking to the person who wrote it.
Not a sandbox with six pins in it. A working district with hydrants, pre-plans and calls coming in while you watch.
If your center emails dispatch alerts, forward us one and we'll tell you whether it parses β before you spend anything.
Once you're in, importing your hydrants and wiring up your dispatch is part of onboarding β not something you do alone.
Prefer email? Reach us directly at sales@fdmapbook.com