6.5 Jurisdictional Boundaries on Maps
Key Takeaways
- Jurisdictional boundary rules on CritiCall are always stated in the problem (a named road, a centerline, or an address parity) — never assumed from real-world knowledge of any specific city.
- The centerline rule means a boundary road usually splits jurisdiction between its two sides, but an incident occurring exactly on the roadway itself has no clean 'side' and should trigger a mutual-aid or closest-unit protocol instead.
- Jurisdiction can be defined by address parity (even/odd), exactly like street-side conventions, just mapped to agency instead of physical side of the street.
- A boundary-line ambiguity should never be treated as a reason to delay dispatch — apply the stated rule, or fall back to the closest-unit protocol when the rule genuinely does not resolve the location.
Why Boundaries Belong in Map Reading
A dispatcher's map is not just streets and addresses — it is also an overlay of who responds. City limits, county lines, township borders, and mutual-aid zones all sit on top of the same grid a candidate learns to read for routes and addresses, and sending the wrong agency to an incident wastes minutes that matter in an emergency. Boundary-recognition questions build on the same underlying skill as address and route items: read a stated rule, apply it to a specific location, and never guess when the rule is unclear.
Core Terms
- Jurisdiction — the geographic area a specific agency (city police, county sheriff, township fire district, and so on) is responsible for responding to.
- Boundary line — the map line separating two jurisdictions; common boundary markers are a named road, a river or waterway, a section line, or a municipal or county limit.
- Centerline rule — the common convention that a boundary running along a road is legally defined as the road's centerline, meaning one side of the road belongs to one jurisdiction and the opposite side belongs to the other.
- Split-jurisdiction address — an address sitting exactly on or extremely close to a boundary line, where the correct responding agency depends on which side of the centerline the structure or incident actually falls on.
- Mutual aid — a standing agreement where a neighboring agency responds to a call outside its normal jurisdiction, typically whichever unit is closest, used specifically to avoid dangerous delays caused by boundary-line disputes.
Applying a Stated Boundary Rule
Just like the even/odd address convention, boundary rules on the CritiCall test are always stated in the problem, never assumed. A typical item names a road as the dividing line and states which side belongs to which agency.
Worked example: A dispatch note states, "Cedar Creek Road is the boundary between Fairview city jurisdiction (north side) and Bell County jurisdiction (south side)." A caller reports a break-in at 2210 Cedar Creek Road, on the south side of the road. Applying the stated rule directly, the correct responding agency is Bell County, not Fairview, regardless of how close the address might appear to the city limits on a map.
The Centerline Trap
The hardest boundary items place an incident exactly on the stated dividing line rather than clearly on one side of it. If the boundary is defined as the centerline of Cedar Creek Road, and a reported incident is a collision occurring in the middle of the roadway itself — not at a building address on either side — there is no single "correct" side to assign from the address alone.
| Boundary Scenario | Correct Dispatcher Approach |
|---|---|
| Incident address clearly on one side of the boundary road | Apply the stated rule directly; dispatch the agency for that side |
| Incident occurring on the roadway itself, exactly on the centerline | Follow the agency's mutual-aid or closest-unit protocol rather than guessing a side |
| Incident near, but not exactly at, a boundary | Use the stated rule for the actual address; do not treat "close to the line" as ambiguous when the address clearly falls on one side |
| Two neighboring jurisdictions with a standing mutual-aid agreement | Dispatch the closest available unit regardless of the jurisdiction line, per the agreement, and notify the jurisdiction of record |
The teaching point behind this table is one of the most consequence-heavy in the entire Map Reading module: a boundary-line ambiguity should never delay dispatch. Agencies build mutual-aid and closest-unit protocols specifically so a dispatcher is not stuck debating which side of a line an emergency falls on while someone waits for help. The correct answers reward recognizing when to apply the stated rule cleanly, and when the scenario instead calls for a closest-unit fallback.
A Second Boundary Convention: Even/Odd by Jurisdiction
Some jurisdictional boundaries are defined the same way street-side parity is defined for addresses, by the address number's parity rather than compass direction. For example: "On Lake Shore Drive, even-numbered addresses fall within Milltown Township, and odd-numbered addresses fall within Grantham Township." A call reporting a disturbance at 1417 Lake Shore Drive is odd, so it falls within Grantham Township under that stated rule, the same even/odd lookup skill used for street-side addressing, applied here to jurisdiction instead of physical side of the street.
Boundaries Can Change: Annexation
One more source of boundary items worth knowing about is annexation — the process by which a city legally extends its limits to absorb adjacent county or township land, moving the jurisdictional line without moving a single street or address number. A block that was county jurisdiction for decades can become city jurisdiction after an annexation vote, even though nothing about the road, the address numbering, or the physical boundary marker (such as a named road) visually changes. CritiCall items reflect this reality by always giving the current, stated boundary rule for the scenario rather than expecting a candidate to know which side of any real annexation line a given address falls on. The practical takeaway for a working dispatcher is the same lesson repeated throughout this chapter: trust the rule stated in the call notes or CAD system for that day, not an assumption based on how a boundary "used to" run.
Common Traps
- Assuming a universal boundary rule instead of reading the specific rule stated in the problem.
- Trying to assign a single side to an incident that occurs exactly on a stated centerline, rather than recognizing that scenario calls for a mutual-aid or closest-unit protocol.
- Assuming a boundary line never moves, when annexation can shift which agency has jurisdiction over a block without changing any street name or address number.
- Delaying a dispatch decision over jurisdiction instead of defaulting to the closest available unit when the boundary rule genuinely does not resolve the location.
A dispatch note states: 'River Road is the boundary between Ashford city jurisdiction (east side) and Deer County jurisdiction (west side).' A caller reports a fire at 3312 River Road, on the west side of the road. Which agency should be dispatched?
A two-vehicle collision is reported in the middle of a roadway that is itself defined as the exact jurisdictional boundary line between two agencies. What is the most appropriate dispatcher action?
A dispatch note states: 'On Lake Shore Drive, even-numbered addresses are in Milltown Township and odd-numbered addresses are in Grantham Township.' A call comes in for 2260 Lake Shore Drive. Which jurisdiction should respond?