Contact

GlossaryDispatch and call records

Call type

A call type identifies the reported reason for a public-safety response. Learn how original and final types differ from offenses and dispositions.

A call type is the category assigned to a public-safety request or event, such as a noise complaint, traffic collision, or welfare check. It describes information available at a particular stage of the response. A call type is not, by itself, confirmation of a crime, injury, or other reported condition.

What the category tells you

Call types help communications staff describe the reason for a response and organize assignments. A category may begin with what a caller reports, then change as dispatchers or responders learn more. Some systems preserve both an original and a final category; other public files expose only one.

San Francisco explicitly documents original and final call-type fields. Its explanation notes that changes made after officers arrive may depend on operational needs, such as requesting additional resources. Consequently, even a field named “final” should not be read as a complete investigative conclusion. San Francisco's call-type explanation.

The category is also separate from the descriptive notes. A standard code may sit beside text explaining circumstances unique to the request. Reading only the short label can remove that context. Conversely, free-text notes are not necessarily standardized enough to compare as though they were formal categories.

Example

Hypothetical example: A caller reports loud banging from a closed shop and worries that someone is breaking in. The original call type is “possible burglary.” Responders find an authorized maintenance worker repairing a damaged door. The final call type becomes “service assistance,” and the handling outcome indicates that no report was taken.

The original category accurately records the concern that prompted the response. It does not establish a burglary. The later category supplies different information, but the outcome and any narrative are still needed to understand what responders did.

If a monthly chart counts original categories, this event belongs in the possible-burglary group. If it counts final categories, it belongs in service assistance. Both charts can describe their selected fields correctly while producing different totals. Their titles should make that choice visible.

Common confusion

Call type and offense are different classifications. A dispatch category describes a request or operational event. An offense category belongs to the agency's crime-reporting process and its applicable definitions. A call about a suspected theft does not automatically become a recorded theft offense.

Call type and priority answer different questions. Type describes the nature of the request; priority expresses its assigned urgency. Two calls with the same type can receive different priorities because their circumstances differ.

Call type and disposition describe different stages. A type might be “alarm.” A disposition might indicate that the premises appeared secure. The second field explains how the response ended; it does not replace the first field's description of why responders went.

Using a local codebook

San Diego publishes separate references for call types, dispositions, and dispatch priorities. That separation is useful: a number or abbreviation should be interpreted using the correct field's reference. San Diego dataset and dictionaries.

Check the reference's date as well as the code. Categories can be renamed, divided, or combined, so a historical export may require a historical codebook. Do not silently map two agencies' similarly named categories together. Explain any grouping used for comparison and preserve enough detail to show what each agency included.

Sources

  • City and County of San Francisco — Law Enforcement Dispatched Calls for Service, revised September 10, 2021, original/final call-type sections. Supports category changes and interpretation boundaries.
  • City of San Diego — Police Calls for Service. Provides distinct call-type, disposition, and priority references, including historical code links.