For public safety agencies and communications centres
No emergency call is taken, routed, triaged, prioritised or dispatched by anything on this page, and no decision about an emergency response is made by it. What can be moved is the other volume — report copies, case status, permits, parking, records requests — that currently lands on the most trained and scarcest staff in your building.
The centre is authorised for a headcount it has not held in a long time. Positions stay open because the training pipeline is long, the certification is demanding, and the work is genuinely hard in a way that a hiring bonus does not address. Overtime fills the gap, and overtime is the same people working more.
Into that arrives a category of contact that has nothing to do with an emergency. Somebody wants a copy of a report. Somebody wants to know whether a case has been assigned. Somebody wants to ask about a parking rule, a permit, an impound, a noise ordinance, or an animal complaint from three days ago. Every one of those is a legitimate request from a resident, and every one of them is answered by a person qualified to talk somebody through CPR.
Some of that volume arrives on the emergency line, because the resident did not know another number or could not get through on it. Staff handle it, because the alternative is refusing a resident, and the handling time is recorded as call volume without any note that it did not need this desk.
On the field side, the administrative tail is the same story with a different uniform. Reports written at the end of a shift, records requests, court paperwork, follow-up calls to complainants — necessary work, done by people whose scarce capability is being somewhere else.
And the after-effects accumulate. Attrition in this sector is not primarily about pay. People leave because of what the work does to them over years, and every avoidable hour of it is an hour that did not have to be spent.
Non-emergency administrative contact is handled by emergency-certified staff because there is no separate path for it — and nobody can currently quantify how much certified capacity that consumes.
The staffing conversation in this sector is almost always about headcount, and headcount is the hardest thing to move: the pipeline is long, the certification is real, and the funding is annual. Which means the practical lever is not how many certified people you have. It is what fraction of their time requires certification at all.
That fraction is currently unknown in most centres. Call volume is measured. Handle time is measured. What is not measured is the split between contact that needed a trained emergency professional and contact that needed a competent person with access to a records system — because both are recorded the same way.
Establishing that split is the first move, and it requires nothing to change. It is a measurement of contact your centre is already handling, categorised against your own definitions rather than a vendor’s. Some centres will find the number smaller than they assumed, and that is a legitimate outcome that should stop the project.
Where the number is large, the correction is a separate path for non-emergency contact — answered properly, in your language, with your escalation rules, and with an unconditional rule that anything sounding like an emergency goes immediately to your certified staff rather than being handled.
How much certified time goes to non-certified work — measured by contacts categorised against your own definitions, with handle time attached — a split most centres cannot currently produce.
Non-emergency contact arriving on the emergency line — measured by administrative contacts received on the emergency number, before and after a separate path exists.
Records and report requests against their statutory clock — measured by elapsed time from request to fulfilment, and the count approaching or exceeding the deadline.
Complainant follow-up that currently slips — measured by follow-ups completed against follow-ups owed, where owed is defined by your own policy.
Administrative contact resolved outside counter hours — measured by requests handled outside business hours, against abandoned administrative contacts in the same window before.
Overtime attributable to administrative volume — measured by overtime hours against the measured administrative share, on comparable periods.
The evidence behind a staffing request — measured by a categorised time profile produced from the work itself rather than estimated for the budget hearing.
anything to do with emergency response. No emergency call is taken, answered, routed, triaged, prioritised or dispatched. No unit is assigned. No CAD entry is created or modified. No call is classified by severity. No investigative judgement is made and no case detail is interpreted. If a vendor offers your centre any of that, the correct response is not to negotiate the scope — it is to decline.
The most important integration decision here is a refusal: no write path into computer-aided dispatch, and no involvement in the emergency call flow. That is an architectural boundary rather than a configuration setting, because a configuration setting is something somebody can change on a Tuesday.
Where records access is required — to answer whether a report is available, or to intake a records request — it is scoped read access to the records system, not to dispatch, and not to anything live.
Criminal justice information carries its own obligations, and they attach through your agreements and the data class rather than through any certification. Where a scope would touch that data, the requirement is established before anything is connected and the honest answer may be that the scope must be narrower.
The boundary between emergency and administrative is not enforced by good judgement in the moment. It is enforced by scope: the emergency path is not connected, so it cannot be reached, and ambiguity in the administrative path resolves toward your certified staff unconditionally rather than toward attempting to resolve it.
That rule is deliberately asymmetric. Transferring an administrative call to a certified person costs a small amount of your scarcest capacity. Handling an emergency call on an administrative path costs something that cannot be recovered. The rule is written so the cheap error is the one that happens.
Every action carries a receipt naming who did it, under what authority, at what time. In this sector that record answers three separate readers — your command staff, your oversight body, and a public records request — and it is produced during the work rather than assembled afterwards.
Operational access is not permission to train. Agency data does not become material improving anything serving another organisation, and given what a records system contains, that boundary is architectural rather than contractual language.
Command staff will want the boundary in writing and will be right to. It should be stated in the scope document in terms your certified staff would recognise as correct, and reviewed by the people who run the floor rather than only by the people who sign.
Criminal justice information obligations attach through your agreements and the data class. Where a proposed scope would touch that data, it is established before anything is connected, and the honest outcome may be a narrower scope rather than an accommodation.
The conversation that is often skipped is with the bargaining unit. The scope should be able to survive that conversation on its merits: what is being moved is the administrative contact, the effect on certified staff is fewer parking questions on a short-staffed shift, and if that is not what the scope actually says, it should be rewritten until it is.
We do not claim certifications we do not hold. We hold neither a FedRAMP authorization nor a FedRAMP certification, and where a state or federal programme requirement flows down to your agency, that is a scoping question with a real answer.
Observation of your non-emergency administrative contact only — categorised against your own definitions, with nothing handled, nobody contacted, and no connection to the emergency path.
The first phase answers one question: what share of your certified staff’s time goes to contact that did not require certification. Nothing is handled and nothing changes. The categories are yours, written by your command staff, because a vendor’s definition of "administrative" is not one your floor would accept.
If that share turns out to be small, the correct decision is to stop, and you will have learned it cheaply. Not every centre has this problem at the size it is assumed to have, and a project justified on an assumption is worse than no project.
If it is large, the first delegation is a single administrative request type — report copies is the usual starting point, because it is high-volume, entirely non-investigative, and cleanly separable — on a separate path, with the transfer rule enforced before a single contact is handled.
Correct, and neither is this. The emergency path is not connected at all — not taken, not routed, not triaged, not dispatched, and there is no write path into CAD. That is a scope boundary rather than a setting, so it is not something anybody can change on a Tuesday. What is proposed is the administrative contact that currently lands on your certified desks: report copies, case status, permits, ordinance questions. If any part of a proposed scope would touch the emergency path, decline it.
They will, and that is the case the rule exists for. Anything ambiguous transfers to your certified staff immediately, without attempting to resolve it — the rule is deliberately asymmetric, because transferring an administrative call costs a small amount of scarce capacity and handling an emergency on the wrong path costs something that cannot be recovered. The threshold for transfer is set by your command staff, and it should be set conservatively.
That conversation should happen early and on the merits rather than after a decision. The honest position is that the scarce thing in your building is certified capacity and you cannot hire your way out of the gap quickly, so the lever is what fraction of that capacity requires certification. If the scope as written does not obviously mean fewer parking questions on a short-handed shift, it has been written wrong and should be rewritten before it is presented.
Then the scope may need to be narrower, and that is established before anything is connected rather than negotiated afterwards. Those obligations attach through your agreements and the data class — there is no certification that substitutes for them. If a proposed scope cannot meet the requirement for your agency, the correct outcome is a smaller scope or none, and you should have that answer in week one.
The observation phase is aimed at exactly that, because a failed staffing request usually failed for lack of evidence rather than lack of need. A measured split — this much certified time went to contact that did not require certification, categorised by your own definitions — is a different object at a budget hearing than a headcount request supported by an estimate. Whether it succeeds is not something anybody can promise you, but it is a stronger case than the one that failed.