In this guide
A service counter can receive a quick information question and a complex request on the same day. If both count as one contact, the total describes contacts. It does not necessarily describe equal effort, equal difficulty or equal benefit to the public. The unit is useful only when its meaning remains intact.
Phoenix’s public service categories span different kinds of issues, while its data-and-evidence resources describe performance reporting across City functions. Those public facts support caution about combining unlike work. They do not establish a weighting formula for Phoenix employees or departments.
Write the noun after the number
“Twenty” is incomplete. Twenty calls, requests, inspections, visits or resolved cases are different observations. Even a familiar noun may have a technical definition. A request may contain several tasks; several contacts may concern one request. Check the source before treating those counts as interchangeable.
For an employee learning how work is recorded, the key question is what event creates one unit. Do not change counting practices based on this editorial guide. The official measurement owner determines the definition and any corrections.
Test for repeats and bundles
Imagine a fictional service where one case generates an initial call, a clarification and a status question. A contact count may record three interactions while a case count records one case. Neither is inherently wrong. A summary that calls three contacts “three residents helped” would add an unsupported interpretation.
The reverse can also occur: one submission may contain several distinct work items. Counting submissions can therefore hide the amount of downstream work. A fair workload explanation says which level of the service chain is being counted.
Keep complexity visible without inventing scores
It can be tempting to assign points to every item and produce a precise workload index. Without an agreed method and evidence, the precision is decorative. Different tasks may require different expertise, equipment, scheduling and review. A homemade score can conceal those differences rather than explain them.
A safer analytical approach is to describe the service mix and identify which comparisons are valid. If the source separates categories, preserve them. If it does not, acknowledge that the total may combine unlike work.
Recognize work outside the visible count
Preparation, documentation, coordination and required review may support a public result without appearing as separate requests. A low count is not proof that a role was idle. A high count is not proof that the work was effective. Individual performance conclusions require evidence and authority well beyond a public total.
The useful output is a unit note: what counts once, what can repeat, what can be bundled and what remains outside the measure. Put that note beside any comparison. It gives the reader a way to understand workload without turning a simple total into an unsupported staffing or performance claim.
Read next
- Read a Phoenix Service Measure Before Reading Its Trend
- Two Equal Queues Can Contain Very Different Waits
- A Budgeted Position Is Not a Service Appointment
Sources and limits
Public sources checked October 5, 2026. Editorial examples are hypothetical; official instructions and case-specific decisions remain with the responsible City service.
- City of Phoenix: Improving Phoenix with Data and Evidence
Official data and evidence initiatives; not a definition of every individual metric.
- City of Phoenix: myPHX311
Public service categories and issue-reporting entry points. Not an emergency dispatch or employee HR interface.