Somewhere in your city's fleet right now, there is a vehicle that has not had an oil change in 14,000 miles. The engine hours are racking up. The check engine light came on two weeks ago. Nobody reported it because nobody officially owns it.
It belongs to the department. It belongs to whoever signed it out that morning. It belongs to the city. Which means, in practical terms, it belongs to no one.
This is the core accountability problem in municipal fleet operations. Shared vehicles with rotating operators have no natural owner. No one feels the consequence of deferred maintenance. No one calls in the DTC because that is not their job. And when the engine finally fails -- at an intersection, on the way to an emergency call, or in the middle of a public works job -- the costs are real and the root cause is invisible.
A municipal fleet vehicle custodianship program is the structural fix. It assigns every vehicle to a named custodian who is responsible for its condition, reporting issues, and ensuring maintenance happens on schedule. It does not eliminate shared use. It creates accountability where none existed.
Done right, a custodianship program reduces vehicle condition complaints, improves first-time maintenance completion rates, and gives fleet managers a clear audit trail for every vehicle in the fleet. Done poorly, it is just a paperwork exercise.
Here is the difference, and how to build a program that actually works.
Why Municipal Fleets Break Down Differently
Municipal fleets have structural characteristics that make vehicle condition management uniquely difficult.
Vehicles are shared across crews and shifts. A public works dump truck might be driven by six different operators in a week. An inspection vehicle might be grabbed by whichever inspector is on duty. Nobody drove it into the ground. Nobody is responsible for the rattling noise that started on Tuesday.
Drivers are not employees who see vehicle maintenance as part of their job. They are inspectors, utilities workers, public health employees, or administrative staff who happen to use fleet vehicles. Maintenance is not in their job description. Reporting issues requires extra effort with no obvious personal upside.
Fleet departments are chronically understaffed. The American Public Works Association consistently reports that municipal fleet departments operate with fewer staff than they need relative to fleet size. A fleet manager covering 80 vehicles with one assistant is not unusual. Manual tracking of vehicle condition across the entire fleet is not possible.
Budget cycles punish reactive spending. When a transmission fails because a worn seal was never flagged, the unplanned repair competes with other line items that were planned. Emergency repairs are expensive and disruptive. But the incentive to invest in prevention is weak because prevention does not show up as a line item with an obvious ROI.
Procurement and maintenance are often separate silos. The department that buys vehicles is not always the department that maintains them. Lifecycle data does not flow cleanly between procurement and operations. Decisions about when to replace vs. repair are made without complete information.
The result is that most municipal fleets are reactive. They respond to breakdowns rather than preventing them. They conduct annual inspections but do not track vehicle condition continuously. They know which vehicles are in the shop but not why the same five vehicles keep coming back.
What a Vehicle Custodianship Program Actually Is
A municipal fleet vehicle custodianship program assigns each vehicle in the fleet to a named custodian -- an employee (or team lead) who is the designated point of contact for that vehicle's condition.
The custodian is not a mechanic. They do not perform maintenance. What they do:
- Conduct pre-trip inspections and report any new issues
- Report warning lights or unusual behavior through a defined channel
- Confirm that scheduled maintenance appointments happen
- Sign off on the vehicle's readiness at the end of each week
This sounds simple. The reason it works is that it converts a shared-accountability problem into a named-accountability problem. When Unit 42 develops a fluid leak, there is one person whose name is attached to that vehicle. That person gets the notification. That person is expected to act.
The custodian does not need authority to fix the problem. They need authority to escalate it. The fleet manager handles the actual repair coordination. But the custodian closes the information gap between vehicle condition and fleet manager awareness.
The Data Gap Custodianship Solves
In most municipal fleets, vehicle condition data flows in one direction: from the shop back to the fleet manager. A vehicle goes in for a repair and the fleet manager learns what was wrong after the fact.
Telematics platforms have expanded this. A DTC fires, the fleet manager sees it on the dashboard, and can theoretically act before the vehicle fails. But telematics data alone does not capture everything. It does not capture the door seal that is letting in water. It does not capture the squealing brake that the operator noticed but did not report. It does not capture the windshield crack that was small last month and is now a safety issue.
Custodians are the human sensor layer that telematics cannot replace.
When a custodian submits a report that Unit 12 has a new noise from the front right wheel, the fleet manager can decide whether to dispatch a mobile mechanic for a diagnostic visit or wait for the next scheduled PM. When the report does not come in despite three consecutive use days, the fleet manager knows to follow up. The silence itself is information.
How Government Fleet Management Software Enables This
A custodianship program without software to support it becomes a paper trail that lives in someone's email. Reports come in as text messages. Escalations get buried. Vehicles get flagged and then forgotten because the fleet manager's inbox has 200 other things in it.
Government fleet management software changes the infrastructure. It gives custodians a defined channel for submitting condition reports. It routes those reports to the fleet manager with the right context. It tracks which issues are open, which have been addressed, and which have been outstanding for too long.
This is where platforms like HoneyRuns add specific value for public works fleet accountability. HoneyRuns connects to the fleet's telematics data and creates automated workflows called Runs when a vehicle health signal fires. A DTC generates a Run automatically. But a custodian's condition report can also trigger a Run -- routing the issue through the same workflow as a telematics alert, with the same tracking, follow-up, and closure process.
The fleet manager does not need to check two different systems. Telematics-generated issues and custodian-reported issues flow into the same queue. Everything has a status. Nothing gets lost.
Building a Program That Sticks: Step-by-Step
Most municipal custodianship programs fail not because the concept is wrong but because implementation is weak. The assignment is made, the expectation is announced, and nothing changes because the new process does not integrate with how people actually work.
Here is how to build one that holds.
Step 1: Map your fleet to departments and primary operators.
Start with the vehicles that have a consistent primary user -- even if they are technically shared. The heavy equipment that one crew uses every day has a natural custodian: the crew lead. The inspection vehicle that three inspectors rotate through needs a designated point of contact even if different people drive it.
Create a spreadsheet. Vehicle ID, department, custodian name, custodian contact. This is the foundation of the program.
Step 2: Define what custodians are responsible for.
Be specific. "Maintain vehicle condition" is not an assignment. "Submit a weekly condition report by Friday at 3pm using the HoneyRuns vehicle check form, and immediately report any warning lights or unusual behavior" is an assignment.
Give custodians a checklist. Fluid levels, tire condition, interior cleanliness, warning lights, unusual noises, visible damage. The list should take 5 minutes to complete. If it takes 20 minutes, it will not get done.
Step 3: Connect custodian reports to your existing maintenance workflow.
This is the step most programs skip. Custodians submit reports. Fleet managers receive them. Nothing happens.
For the program to work, a custodian report that identifies a real issue needs to generate a real service action. That means routing the report into your maintenance coordination workflow, creating a service request, and tracking it to completion.
With HoneyRuns, this happens automatically. A custodian submits a report flagging a new fluid leak. The report creates a Run. The Run is routed to the fleet's mobile mechanic with the vehicle ID, the reported issue, and the maintenance history. The mechanic schedules a diagnostic visit. The Run closes when the issue is resolved. The custodian gets a confirmation.
Closing the loop is what makes custodians take the program seriously. If they report issues and nothing ever happens, they stop reporting. If they report issues and they see them get fixed, they become more reliable.
Step 4: Make accountability visible.
The most effective custodianship programs tie vehicle condition to performance reviews or operational metrics. This does not mean punishing operators for mechanical failures. It means making vehicle condition a tracked responsibility, the same way response time or project completion are tracked.
A simple monthly report showing vehicle condition scores by custodian -- based on the number of issues reported vs. the number of issues caught late or after failure -- creates visible accountability without being punitive.
Custodians who score well are recognizing problems early. Custodians who score poorly might need coaching, better tools, or a clearer understanding of expectations.
Step 5: Integrate telematics data so custodians see the same picture as the fleet manager.
When a DTC fires on a custodian's vehicle, that custodian should know about it. Not necessarily the full telematics report, but a plain-language notification: "Unit 42 has a new engine warning light. A service request has been created. Please confirm the vehicle is drivable and any other symptoms you have noticed."
This does three things. It reinforces that the fleet manager is watching. It prompts the custodian to provide context that telematics cannot. And it creates a documented record of the communication that supports both maintenance tracking and liability management.
What This Looks Like for the Fleet Manager
The fleet manager's daily reality changes in measurable ways when a custodianship program is running with automated fleet maintenance tools backing it up.
Before: The fleet manager checks the telematics dashboard manually each morning. Flags new DTCs. Texts service providers. Follows up on open service requests. Handles incoming calls from operators reporting problems. Tries to remember which vehicles are overdue for PMs.
After: The fleet manager opens a unified queue of open Runs. Most were generated automatically from telematics. Some were generated from custodian reports. Each has a status, a priority, and an action. The fleet manager reviews exceptions, approves or adjusts service assignments, and closes out completed work.
The information is the same. What changed is that the fleet manager is no longer the collection point for vehicle condition data. The custodians are. Telematics is. The fleet manager is the decision-maker for anything that requires judgment.
For a public works fleet department with one fleet manager covering 80 vehicles, this shift is the difference between being reactive and being proactive. You cannot be proactive when you spend 12 hours a week chasing down information. When the information comes to you automatically, you have time to use it.
What This Looks Like for City Leadership
Municipal fleet operations are a budget item that city councils and administrators rarely think about until something goes wrong. A vehicle fire because a known electrical fault was not addressed. An accident because a brake issue went unreported. A missed contract deadline because three vehicles were unexpectedly in the shop.
A documented custodianship program with traceable records is a liability management tool as much as a maintenance tool. When an incident happens, the question "who knew what and when" can be answered. The run history shows when the issue was first flagged, what action was taken, and by whom.
This is not just protection from litigation. It is the documentation that supports budget requests for fleet modernization. When you can show a city council that a vehicle failed because it was 22,000 miles past a scheduled PM that was never completed, you have a case for the maintenance software investment that prevents the next one.
The Difference Between a Program and a Policy
Many cities have something that looks like a custodianship program on paper. There is a policy. There is a form. There might even be a training session from two years ago.
The difference between a policy and a program that works is infrastructure.
A policy says custodians are responsible for vehicle condition. A program gives custodians a simple, low-friction way to report issues, connects those reports to automated service workflows, closes the loop with confirmations, and makes condition data visible to supervisors.
Without the infrastructure, the policy is performative. Operators do not report because reporting does not visibly change anything. Fleet managers do not follow up because there is no system surfacing which reports need follow-up. Vehicles continue to degrade because the accountability that exists on paper does not exist in practice.
Municipal fleet vehicle custodianship programs work when they are supported by the right software. The software does not need to be complicated. It needs to connect the custodian's report to the service workflow, and the service workflow to a completion record. That loop -- report, action, confirmation -- is what turns a paper policy into a functional program.
Get Started with HoneyRuns
Municipal and government fleet departments are under pressure to do more with fewer staff and tighter budgets. A well-run custodianship program backed by automated maintenance workflows can cut vehicle downtime, reduce emergency repair costs, and give fleet managers the time to be proactive instead of reactive.
Visit honeyruns.com to learn more, or schedule a demo to see it in action.
For municipal fleet managers: HoneyRuns connects your telematics data and custodian reports into a single automated workflow, so nothing falls through the cracks between your 80 vehicles and your two-person department.
For city administrators and directors of operations: HoneyRuns gives you a documented audit trail for every vehicle in your fleet -- when issues were reported, what action was taken, and when work was completed.
HoneyRuns is a fleet intelligence platform that automates operational workflows by turning vehicle telematics data into executed actions. We integrate with DIMO, Samsara, Geotab, Motive, and other major telematics providers. Founded by operators who built and managed a 50-vehicle fleet across three states.