Beyond the scene: The importance of time consumed on incident report task components in workload-based patrol allocation and deployment assessments
Bibliographic record
Abstract
Based on the conclusions of a workload-based assessment of patrol staffing needs conducted at a Canadian police force between 2012 and 2016, this article highlights the importance of capturing time spent on components of calls for service (CFS) that result in an incident report for police allocation and deployment analyses. Initial Computer-Aided Dispatch System (CAD) data analysis suggested that CFS that results in an incident report have a significantly higher completion time than other types of calls. In order to account for CFS handling phases that were not captured by CAD data, a survey was conducted to measure the time spent on the scene, the time spent by backup units on the call, the time spent with the person arrested or taken in charge and time spent on subsequent administrative duties. Research findings suggest that CFS that require the completion of an incident report generate most of the reactive workload of patrol officers, even if they frequently constitute a minority of calls. Results also reveal that the use of supplemental data to assess the workload generated by incidents reports may allow the use of a workload-based approach in police agencies that record less than 15 000 citizen-initiated calls for service per year.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.006 | 0.032 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".