Automatic Vehicle Location and Closest-Unit Dispatch: A Plain-Language Guide

What AVL actually is

At its core, AVL is a GPS receiver plus a way to report its position. Each piece of apparatus carries a GPS unit, the same satellite positioning technology in your phone or your personal vehicle. That unit calculates where the vehicle is, and then something (a modem, a radio, or a cellular device) sends that position back to your computer-aided dispatch (CAD) system on a regular interval. Dispatch software plots those positions on a map. That is the whole idea in one sentence: know where the trucks are, on a screen, in close to real time.

The word "automatic" matters. Older approaches asked crews to key up and announce their location, or asked dispatchers to guess from the last known assignment. AVL removes the human step in reporting position. It does not remove the human step in reporting status, and that distinction becomes important later in this guide.

AVL is not one product or one standard. The GPS hardware, the transport (cellular, land mobile radio, or a mix), the map, and the CAD logic can all come from different vendors and can be combined in many ways. Because there is no single universal setup, almost every specific number in this article (accuracy, update rate, cost) will vary by system and jurisdiction. When we say verify locally, we mean it.

From run cards to closest-unit dispatch

Traditional dispatch runs on static run cards. A run card (sometimes called a running assignment or a box alarm) says: for this address or this geographic box, send these specific units in this order. It is built ahead of time from where stations sit and which unit "owns" that area. Run cards are reliable and easy to understand, but they assume units are in quarters. The card does not know that Engine 2 is out on a transfer three miles away, or that Medic 4 just cleared a call two blocks from the new one.

Closest-unit dispatch uses live position instead of assumed position. When AVL feeds real locations into CAD, the system can recommend the nearest available unit to the incident, not simply the unit the box says should go. Some systems call this closest-unit, nearest-available, or automatic vehicle location routing. The recommendation usually accounts for more than a straight-line distance: better implementations estimate drive time over the road network, which can differ a lot from "as the crow flies" when rivers, highways, or one-way streets are involved.

It is worth being clear about a subtlety. Closest by distance is not always fastest by time, and fastest is not always most appropriate. A slightly farther engine on a highway may beat a closer one stuck behind a rail crossing. And the closest unit is not always the right resource: you still need the correct unit type for the call. Good CAD logic layers closest-unit on top of, not instead of, resource requirements.

The mapping and mobile-data side

AVL is only as useful as the map it draws on. The positions have to land on an accurate, current base map with correct street names, address ranges, and jurisdiction boundaries. If your underlying map data (often called GIS data) is out of date, a brand-new subdivision may not exist on screen, and the routing engine cannot route to a road it does not know about. Many departments underestimate how much ongoing work the map layer takes.

The other half of the picture is what crews see in the cab. A mobile data terminal or a rugged tablet (sometimes just a phone in smaller agencies) can show the responding unit its own position, the incident location, and the recommended route. It can also show where other units are, which is powerful for coordination on larger incidents. When apparatus can see each other on a shared map, staging and mutual aid get noticeably smoother.

• Base map and GIS. Streets, address points, hydrants, and boundaries have to be maintained. This is a recurring task, not a one-time import.
• Transport. Positions travel over cellular, radio, or both. Coverage and cost drive this choice.
• In-cab display. Routing and situational awareness for the crew, ideally big, simple, and glanceable while moving.
• CAD integration. The dispatch system consumes positions and turns them into unit recommendations. This is where closest-unit logic lives.

Where the payoff really shows up

The headline benefit is faster, smarter dispatching. Sending the genuinely closest available unit can shave time off responses, especially when units are frequently out of quarters. But the real value is broader than a single stopwatch number, and it is honest to talk about it that way rather than promising a specific percentage improvement that nobody can guarantee.

• Better mutual aid. When neighboring agencies share position data (or at least share a map), the nearest unit can come from across a line when your own units are committed. That can matter enormously at the edges of your district.
• Situational awareness. Command and dispatch can see where everyone is at a glance, which helps with move-ups, coverage gaps, and knowing who is actually available.
• After-action and analysis. Recorded position and timestamp data supports honest review of response patterns, station location decisions, and staffing discussions with funders.
• Crew confidence. Turn-by-turn routing to an unfamiliar address, especially for newer members or covering crews, reduces wrong turns and second-guessing.

Honest limits you should expect

AVL is real technology with real constraints, and pretending otherwise sets crews up to distrust it. Be upfront with everyone about what it will not do perfectly.

• GPS accuracy. Consumer-grade GPS is good but not perfect. Positions can drift, especially among tall buildings, under heavy canopy, in tunnels, or inside large structures. Expect a dot that is close, not surveyed-in exact.
• Update intervals. Positions report on an interval, not continuously. Between updates the map shows where a unit was, not where it is right now. A fast-moving apparatus can be well down the road from its last plotted dot. The interval is a tunable trade-off between freshness and data cost.
• Coverage gaps. If positions ride on cellular and there is no signal in a rural corner of your district, updates stall until the unit is back in coverage. Radio-based transport has its own dead spots. Know where yours are.
• Garbage in. If a crew does not mark themselves available when they clear, the system thinks they are still busy and will skip them. AVL knows where a unit is, but it relies on status to know whether it can be dispatched. This is the single most common way closest-unit dispatch underperforms.
• Boundary and political issues. The closest unit sometimes lives on the other side of a jurisdiction line. Whether it can or should be sent is a policy and agreement question, not a software question. Automatic recommendations can surface uncomfortable questions about who covers what, who bills whom, and whose crews cross which line.

None of these are reasons to avoid AVL. They are reasons to plan for it with clear eyes, write policy around it, and set expectations so the first stale dot does not sink the whole program in the crew's estimation.

Data quality and status discipline

Closest-unit dispatch lives or dies on status discipline. The system makes decisions from two inputs: where a unit is (from GPS) and whether it is available (from status). GPS mostly takes care of itself. Status is a human habit, and it is where most departments struggle. If crews forget to mark en route, on scene, or available, the map lies, and every downstream recommendation inherits that lie.

• Make status changes easy. The fewer taps or button presses it takes to update status, the more consistently crews will do it. Friction is the enemy of clean data.
• Train the "why," not just the "how." When crews understand that a missed available status can send a farther unit to a real emergency, discipline improves. It stops feeling like paperwork.
• Audit gently and regularly. Look for patterns of missed or late status changes and coach, do not punish, especially early on. The goal is a habit, not a gotcha.
• Keep your map current. Assign someone to own GIS updates so new streets, renamed roads, and changed boundaries make it into the system on a predictable schedule.

Privacy and tracking your people

Tracking apparatus also means, in practice, tracking the people in it. That is not a reason to avoid AVL, but it deserves an honest, respectful conversation rather than a surprise rollout. Members are more likely to support a system they understand and trust, and far more likely to resist one that feels like it was installed to watch them.

Be clear internally about what is being collected, why, who can see it, and how long it is kept. Position and timestamp history is operational data, and in many places it may also be a public record subject to disclosure rules. The specifics depend heavily on your state, your labor agreements, and local policy, so this is an area to review with your own legal counsel and, where relevant, your labor representatives. Do not rely on generic advice, including this article, for the rules that bind your agency.

• State purpose plainly. AVL exists to get the right unit to emergencies faster and to keep crews coordinated and safe. Say so, and mean it.
• Set retention and access rules. Decide who can view live and historical position data, and how long history is stored. Write it down.
• Address off-duty and personal-device concerns. If any tracking could reach personal phones or off-duty movement, handle that explicitly and conservatively.
• Bring people in early. Involving crews and any bargaining unit before deployment builds trust and surfaces concerns while they are still cheap to fix.

Practical advice for a small department

You do not have to boil the ocean, and you should not try to. A small department can get most of the value of AVL without the biggest-agency price tag if it stages the effort and keeps expectations realistic.

• Start with the problem, not the product. Are your units often out of quarters? Do you rely heavily on mutual aid? Is response time your biggest pressure? Let the actual pain point decide whether AVL earns its cost.
• Confirm CAD and dispatch fit first. If a regional or county center dispatches you, the closest-unit logic may live with them. Talk to your dispatch partners before you buy anything, because their system and their willingness to enable the feature can make or break your plan.
• Budget for the whole thing. Hardware is the visible cost. The recurring costs (cellular or radio transport, map and GIS maintenance, software subscriptions, and training) often outweigh it over time. Ask vendors for total cost across several years, not just the sticker.
• Pilot before you scale. Put AVL on a few units, work out the transport dead spots and the status habits, then expand. A small pilot teaches you more than a big brochure.
• Invest in status training on day one. The technology is the easy part. The human habit of accurate status updates is what actually delivers closest-unit dispatch. Build that culture from the start.
• Sort out the boundary agreements. If closest-unit routing might cross a line, get the automatic aid or mutual aid agreements in writing before the software starts making those recommendations for you.
• Verify every number locally. Accuracy, update rates, coverage, and cost all depend on your specific setup and geography. Insist on a demonstration in your own district, not a generic claim.

Takeaways

• AVL is GPS in each apparatus reporting its position to CAD, which lets dispatch send the closest available unit instead of following a static run card.
• Closest-unit routing is a recommendation aid for dispatchers, not an autopilot, and it should sit on top of correct resource requirements, not replace them.
• The map and GIS layer, the transport, the in-cab display, and CAD integration all have to work together, and the base map needs ongoing maintenance.
• The real benefits include faster responses, smoother mutual aid, strong situational awareness, and better after-action data, though the exact gains vary and should not be promised as a fixed number.
• Honest limits include GPS drift, reporting intervals, coverage gaps, missed status updates, and boundary or political questions when the closest unit crosses a jurisdiction line.
• Closest-unit dispatch depends on status discipline and a current map; garbage in means bad recommendations out.
• Tracking apparatus means tracking people, so set purpose, access, and retention clearly, involve crews and any bargaining unit early, and verify your legal obligations locally.