A pothole crew closes eleven work orders on a Tuesday. That number means nothing on its own — it only becomes useful once it rolls up into a street maintenance division total, and that division total only means something once it rolls up into a citywide public works scorecard the city manager can defend to council. Most municipalities have all three levels of data. Almost none of them have a system that connects them automatically, which is why the monthly performance briefing still gets built by hand. A connected roll-up changes that; see how at Oxmaint.
MUNICIPAL PERFORMANCE MANAGEMENT · CREW TO DIVISION TO CITY · KPI ROLL-UP
Municipal KPI Roll-Up Software: The Division-To-City Guide
Crew-level work order data, division-level maintenance metrics, and citywide performance scorecards should be the same numbers viewed at three altitudes — not three separate reports built by three separate people every month.
City Council Scorecard
Division Performance Reports
Crew Work Order Data
Why Most Municipal KPI Programs Break Down Within Two Years
Public works tracks one set of numbers on one spreadsheet, utilities keeps another, and parks maintains a third that nobody reconciles against the other two. Every metric that reaches the council packet is a manual pull, assembled the week before the meeting by a staffer who has a full-time job that isn't reporting.
70–85%Reduction in reporting time when performance data is automated
5–8KPIs per department recommended for a dashboard that stays readable
11+U.S. cities running a CitiStat-style weekly performance review
By the time the numbers reach the dais, they're often a month stale and difficult to defend under a single pointed question from a council member. Once elected officials stop trusting the dashboard, department heads stop updating it consistently, and a performance program that started with good intentions quietly becomes a compliance exercise instead of a management tool.
The frustrating part is that the underlying data usually exists somewhere. A crew closed the work order, a supervisor logged the hours, a dispatcher noted the response time — the raw material for a good performance program is generated every single day. What's missing is the connective tissue that turns that daily activity into a number a city manager can stand behind at the podium without a caveat.
Three Tiers, One Number, Different Altitudes
A roll-up model works when the same underlying data point can answer a crew supervisor's question, a division manager's question, and a city manager's question without anyone re-entering anything. Think of it less as three separate reports and more as one dataset viewed through three different lenses, each one filtering for the level of detail that lens actually needs.
Crew Level
What Happened Today, On This Route
Work orders closed, response time per call, hours logged, and materials used — captured on a mobile device at the point of work, timestamped and geotagged for accuracy.
Example: 11 pothole repairs closed, average 42 minutes per repair
What's Trending Across This Function
Division Level
Crew totals aggregate into division metrics — PM compliance rate, backlog count, average cycle time — trended month over month against a target threshold.
Example: Street Maintenance Division, 94% PM compliance, backlog down 8%
What The City Is Delivering, Overall
City Level
Division scorecards roll into a citywide public works view with red-yellow-green status, ready for the council packet without a single manual recompilation.
Example: Public Works overall, 4 of 5 department KPIs on target
Build The Roll-Up Once. Stop Rebuilding It Every Month.
Oxmaint aggregates work order data from crew to division to citywide scorecard automatically, so the numbers a council member sees are the same numbers a crew supervisor saw that morning.
Where The Roll-Up Actually Breaks
01
Crew Data Never Leaves The Paper Route Sheet
Field crews still complete work on paper or in a tool that doesn't feed anything upstream, so the division's numbers are reconstructed from memory or a supervisor's end-of-week tally instead of the actual work performed.
02
Every Division Defines Its Own Metrics
Street maintenance measures cycle time in business days, utilities measures it in hours, and parks doesn't track cycle time at all — so a citywide "average response time" figure is either meaningless or requires a manual normalization step every single reporting cycle.
03
The Roll-Up Happens Once A Month, Not Continuously
Because assembling the citywide view takes real staff time, it only happens right before the council meeting — which means the number presented is already three to four weeks old by the time anyone acts on it.
04
Nobody Owns The Reconciliation Step
When numbers from two systems disagree, resolving the discrepancy falls to whoever notices first, and there's rarely a documented process for deciding which source is authoritative.
05
The Roll-Up Survives Turnover Poorly
When the one staffer who understands how the spreadsheet formulas connect crew data to division totals leaves the organization, the roll-up process leaves with them, and the next report starts from a blank template built by whoever inherits the job.
Building Trust In The Numbers Before You Build The Dashboard
A dashboard that shows the wrong number confidently is worse than no dashboard at all, because it takes exactly one wrong figure in front of council to make every subsequent report suspect. Before rolling out a citywide scorecard, the numbers underneath it need a clear governance model — who defines each metric, who owns data entry, and who has authority to correct an error when one is found. Getting this right up front costs a few hours of meetings; getting it wrong costs months of rebuilding trust after a single embarrassing correction in a public meeting.
Single Metric Owner
Every citywide KPI has one department accountable for its definition, so "average response time" means the same thing in every report it appears in.
Source Of Record
When two systems disagree, there's a documented answer for which one is authoritative, decided in advance rather than argued about during a council prep meeting.
Change Log
Any correction to a published figure is recorded with who made it and why, so a revised number doesn't look like a cover-up months later.
The CitiStat Discipline, Without The CitiStat Staff
Baltimore's CitiStat program popularized the weekly, data-driven performance review — a structured meeting where department heads present current numbers against targets, and unresolved problems get a documented follow-up date rather than disappearing into the next agenda. Baltimore has attributed hundreds of millions of dollars in savings to the discipline of that weekly review, and more than a dozen U.S. cities have adopted a version of the model since.
What made CitiStat work wasn't the meeting format — it was that the data going into the meeting was current, comparable, and owned by someone. Most cities that try to replicate the model without a connected data source end up recreating the original spreadsheet problem, just on a weekly instead of monthly cycle, which burns out the staff assembling it even faster.
A connected roll-up is what makes the weekly cadence sustainable rather than punishing. When the division scorecard already reflects last night's data automatically, the weekly review becomes a genuine conversation about what's trending in the wrong direction, instead of a status update on whether the spreadsheet got built in time for the meeting.
Manual Roll-Up vs. A Connected KPI Pipeline
| Stage | Manual Monthly Roll-Up | Oxmaint Connected Pipeline |
|---|
| Crew Data Capture | Paper route sheets, re-entered later | Mobile work order closeout, timestamped at the job |
| Division Aggregation | Spreadsheet built the week before reporting | Nightly aggregation into division scorecards |
| Metric Definitions | Vary by department, reconciled manually | Standardized metric library across departments |
| Citywide Scorecard | Assembled by hand for the council packet | Exported directly from live data, always current |
| Trend Tracking | Recreated each cycle from prior reports | Automatic month-over-month trend lines |
| Public Transparency | Separate effort to publish public-facing data | Same source data powers the public dashboard |
What Belongs At Each Level Of The Roll-Up
Applying the same KPI list uniformly at every level makes the report unreadable at every level. A crew supervisor doesn't need a citywide cost-per-service-delivered figure, and a council member doesn't need to see individual work order numbers — each tier needs the altitude that matches the decision being made there.
The table below is a starting point, not a fixed template. Parks and utilities will weight these differently than streets or facilities, but the principle holds everywhere: fewer metrics, chosen deliberately for the audience reading them, beats a long list nobody actually reviews.
| Level | Typical Metrics | Primary Audience |
|---|
| Crew | Work orders closed, response time, materials used, hours logged | Crew supervisor, dispatcher |
| Division | PM compliance rate, backlog count, average cycle time, cost per work order | Division manager, department director |
| City | Department scorecard status, 311 resolution time, capital plan progress | City manager, mayor, council |
The Monthly Briefing, Rebuilt As A Pipeline Instead Of A Project
1
Daily
Crews close work orders in the field; data lands in the system same-day.
2
Nightly
Division scorecards recalculate automatically against target thresholds.
3
Weekly
Department heads review red and yellow metrics before they become a surprise.
4
Monthly
Citywide scorecard exports directly into the council packet — no rebuild required.
Questions To Ask Before Your Next Council Packet Deadline
These six questions surface most of the roll-up gaps described above, and most public works directors can answer all of them honestly in under five minutes if they're willing to.
✓
Can a crew's work order data reach the citywide scorecard without anyone re-typing it?
✓
Do all departments define cycle time, backlog, and compliance the same way?
✓
If a council member asks about a red metric, can staff explain it without pulling three reports?
✓
Does the public transparency dashboard use the same data as the internal scorecard?
✓
Is there a documented owner for reconciling numbers when two systems disagree?
✓
How many hours does one staff member spend assembling the report each month?
A Realistic Rollout: One Department, Then The Rest
Cities that succeed at building a real roll-up almost never attempt all departments at once. They prove the model with the department that already has the most consistent work order discipline, then extend it once staff can see the monthly time savings for themselves.
1
Days 1–30
Stand up one department's crew-to-division roll-up, usually public works or streets, where work order volume is highest.
2
Days 31–60
Validate the numbers against the old manual report for one full reporting cycle before retiring the spreadsheet.
3
Days 61–90
Add a second and third department, standardizing shared metric definitions as each one comes online.
4
Ongoing
The citywide scorecard grows department by department until every function reports through the same pipeline.
This sequencing matters more than it looks. A city manager who sees one department's report go from a two-day manual assembly to a same-day automatic export becomes the strongest advocate for extending the model — far more persuasive than any pitch from outside the organization.
Municipal KPI Roll-Up Questions
Does a roll-up system force every department to use identical KPIs?+
No. Each department keeps metrics relevant to its own operations, but shared metrics like cycle time and backlog use standardized definitions so they can be compared and aggregated accurately across departments and up to the citywide view.
Can this replace our existing council packet format?+
The roll-up produces the data behind the packet; most cities keep their existing packet format and simply export current figures into it instead of rebuilding numbers from scratch each month.
Sign up to see a sample export.
How does crew-level data get into the system if field staff don't use smartphones?+
Mobile work order closeout works on basic devices and tablets, and route sheets can still be entered by a dispatcher at day's end for any crew that works without a field device at all.
Can council members or the public see the same dashboard staff use internally?+
A public-facing summary view can be published from the same underlying data as the internal dashboard, so the transparency portal and the staff view never drift apart or contradict each other.
Book a demo to see both views side by side.
How long does it take to set up the crew-to-city roll-up for a mid-size city?+
Most public works departments have their first department scorecard live within a few weeks, with additional departments added incrementally rather than migrating the entire organization at once.
One Set Of Numbers, From The Route Sheet To The Council Dais
Every level of your organization already generates the data a performance program needs. The roll-up is what turns crew activity into a citywide story council can trust — without anyone spending the last week of the month rebuilding a report by hand.
