GlossaryResponse performance and resources
Workload
Workload describes the amount of work an agency or resource handles. Counts, time, complexity, and overlapping demand reveal different parts of it.
Workload is the amount of work handled by an organization, team, or resource during a defined period. In public safety, it can be described through calls, incidents, investigations, patient encounters, inspections, or time committed to assignments. The measure should identify whose work is counted and what activity it includes.
No single call total captures every dimension of workload. A brief service call and a prolonged incident each add one to an incident count, while using very different amounts of staff time and equipment.
Counts and time answer different questions
Incident counts describe frequency. Unit responses describe how often resources were assigned. Time-based measures describe duration, while staffing records help establish the personnel committed. Complexity and follow-up work may require further information.
San Francisco's calls-for-service explainer illustrates an important limit: timestamps for the first unit arriving and the last unit closing an incident cannot reconstruct every officer's time at the scene. Multiplying that interval by an assumed staffing count would invent detail the file does not supply. San Francisco documentation, revised September 2021
Example
Hypothetical: A department handles ten incidents in one shift. Nine require one unit for twenty minutes each. One requires four units for two hours each.
The nine shorter assignments account for three unit-hours. The longer incident accounts for eight unit-hours. Together they total eleven unit-hours, assuming the stated durations cover each unit's complete measured assignment.
An incident count alone gives each event equal weight. The time calculation shows that one event accounted for most of the recorded unit commitment. Neither measure alone establishes the difficulty of the work or its outcome.
Common confusion
Workload is not the same as community harm. More recorded calls can reflect service demand, reporting practices, proactive activity, or changes in coverage, not simply more crime or injury.
It is also not equivalent to utilization. Utilization compares activity with a defined capacity denominator. Workload can be reported as a count or duration without making that comparison.
Annual volume does not show concurrency. Work spread evenly across a year creates a different coverage problem from several demanding calls arriving together.
Interpreting workload reports
Identify the activity, counting unit, date range, and included organizational functions. Check whether aid responses, administrative work, prevention, and follow-up investigations are included or excluded.
Compare stable service areas and definitions. A rise after a department takes over another community can reflect added responsibility. A balanced account presents counts and time where supported, while clearly identifying work the available records cannot measure.
Related terms
Sources
- San Francisco calls-for-service explainer — Incident/unit distinctions and limits of first-arrival/last-close timestamps for calculating personnel workload.
- USFA mutual-aid guidance — Context for resource commitments across organizations.