We are here for you
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
.webp)
The decision to move from self-managed fleet maintenance to a coordination program is straightforward compared to the execution. Most fleets that struggle with the transition do not fail because the coordination program is wrong for them. They fail because the switch was treated as a single event rather than a four-phase process, and the gaps that opened during the transition, untracked service windows, dispatcher confusion on the new call-in protocol, and maintenance records that were not transferred before trucks started moving through the new network, took weeks to close.
A fleet of 20 trucks that transitions cleanly has done four things in sequence before any truck goes through a vetted partner shop under the new program. A fleet that does not follow that sequence spends the first 30 days of the new program managing the same fires it was managing before, with the added friction of a new process being learned while those fires burn.
The two weeks before the program goes live determine whether the transition creates a documentation gap or closes one. Three things need to happen in this window, and all three can be completed with data the fleet already has.
Build the per-unit maintenance file. Every truck in the fleet needs a single consolidated file before the coordination program begins scheduling its first service events. That file contains the last PM-A date and mileage, the last PM-B date and mileage, the next service trigger mileage for each, the annual DOT inspection expiration date, any open DVIR defects, and a copy of the last three service invoices. This is the baseline the coordination program uses to schedule the first service events correctly. A fleet that hands off without this file forces the coordination program to discover the service history reactively, through the first breakdown or the first overdue PM.
OxMaint's fleet transition research documents the most common failure mode precisely: switching without first establishing the maintenance cost and compliance baseline that will be used to measure improvement. The per-unit file is that baseline. Twelve months of repair invoices per unit, sorted by date and category, gives the coordination program the service history it needs and gives the fleet the cost-per-event data that measures whether the program is delivering after 90 days.
Identify service windows closing within 60 days. Any truck within 1,500 miles of its next PM-B trigger at the time of transition is a scheduling risk. If the coordination program is not aware of these trucks from day one, they will run past their service windows during the first four to six weeks while the new scheduling process is being established. Review the current odometer for every unit, calculate the mileage remaining to each truck's next PM-B trigger, and give the coordination program a priority list of units that need to be scheduled before anything else.
Clarify the existing shop relationships. The fleet has been using shops informally for months or years. Some of those shops may be in the coordination program's vetted network. Some will not be. The pre-switch audit identifies which current shops to continue routing work through under the new program and which to sunset. This is not about burning bridges. It is about avoiding the confusion of the first 30 days where the dispatcher is not sure whether to call the old shop in Memphis or route through the new program. A clear, written list of which shops are in the network, which are not, and what to do for each repair type resolves that ambiguity before it becomes a missed event.
Go-live week is not the start of the program. It is the start of the new call-in protocol. The coordination program is operational at this point. The fleet's job is to ensure every person who interacts with maintenance knows what changed and what did not.
The dispatcher workflow change. Before the switch, the dispatcher found shops, called shops, negotiated rates, chased repair documentation, and tracked PM windows manually across whatever system the fleet was using. After the switch, the dispatcher calls one number for any breakdown event and confirms service window alerts for units approaching their PM trigger mileage. The mechanics of each repair are handled by the coordination program. The dispatcher's job narrows from maintenance management to maintenance notification and oversight.
This change is not self-evident. A dispatcher who has been managing maintenance for three years knows every shop on the fleet's corridors by name and has personal relationships with several of them. The go-live communication to the dispatcher needs to be specific: here is the single number to call, here is what to tell them when a driver calls in a breakdown, here is what to expect back within 15 minutes, and here is how to escalate if the response is not what was promised. Upper Inc's fleet management transition research recommends defining communication protocols explicitly at go-live: who contacts the program, for what issues, and through which channel. Ambiguity on this in week one produces dispatchers who fall back to old habits because the old habits are faster.
The driver communication. Drivers need one sentence before the transition: "When you have a breakdown or a maintenance issue, call dispatch as you always have. Dispatch handles it from there." What changes is what dispatch does with that call. From the driver's perspective, nothing changes about how they report a problem. What changes is everything that happens after they report it. Keeping that framing simple reduces driver friction to zero.
For after-hours breakdown calls specifically, drivers should know the new program is active 24 hours a day and that calling dispatch outside business hours still triggers a live response. The after-hours support page covers what that response process looks like for drivers stranded at night. The key point to communicate is that coverage does not stop at 5 PM.
The first eight weeks of a new coordination program are where most of the friction concentrates. Shops in the network that the fleet's drivers have not used before need to be trusted. Documentation that the coordination program produces needs to be checked against the 49 CFR Part 396 standard to confirm it builds the defect-to-repair chain correctly. And service windows that were overdue at go-live need to be cleared.
The active management task during this phase is not fixing problems. It is identifying them before they become patterns. Two specific checks in weeks two through eight.
First, pull one work order per week from a service event the coordination program managed and verify it meets the documentation standard. It should show vehicle ID, odometer at service, inspection points with measured conditions, parts replaced with part numbers, technician identification, and repair certification. If it does not, that is a conversation with the program's account contact, not a search for a new provider. It is data about documentation quality that should be corrected at the shop level during the stabilization phase, not discovered six months later at a DOT audit. The FMCSA fleet maintenance records article covers precisely what a compliant work order contains and why each element matters in an audit context.
Second, confirm that every PM-B service triggered during this period was completed within the correct window. A coordination program that is scheduling trucks for service should be catching windows before they close, not after. If two trucks during the stabilization phase ran past their PM-B triggers before a service event was scheduled, that is a tracking gap in the program that needs to be raised and corrected, not accepted as normal.
The 90-day mark is the first point at which the coordination program's performance can be measured against the baseline established in Phase 1. Three metrics determine whether the program is delivering what was promised.
PM compliance rate should be above 90% for any truck whose service window fell due during the 90-day period. A fleet that switched because its self-managed compliance was running at 78% should see a measurable improvement by day 90 if the program is executing correctly. If the rate has not improved, the scheduling process has a gap that needs to be identified and fixed before the 90-day mark becomes six months of the same result.
Cost per managed repair event should be lower than the average repair cost per event from the 12 months before the switch, adjusted for the coordination program service fees. The net number, repair cost minus coordination fee, should show savings against the pre-switch baseline. If it does not, the pre-negotiated network pricing is not performing as it should, and that conversation belongs at the 90-day review, not at the annual renewal.
After-hours coverage should have produced at least one resolved breakdown event if any occurred. A coordination program that answered a midnight breakdown with a confirmed vendor dispatch and a resolved repair within the same event window is demonstrating the capability it was evaluated for. A program that responded with an answering service and a callback the next morning is not.
If your fleet is at the point where the decision to switch has been made and you want to understand what the transition sequence looks like specifically for your fleet profile, OEM mix, and operating corridors, the fleet maintenance plans page covers the plan tiers and what each one includes at go-live.
This is the question most fleet managers do not ask until the first week of the new program, when a driver breaks down near a shop the fleet has used for two years and is not sure whether to go there or call the coordination program's dispatch line.
The answer depends on whether that shop is in the vetted network. If it is, the coordination program routes work there with pre-negotiated pricing and its documentation standards applied. The shop relationship continues, but the rate and documentation structure are now governed by the network rather than negotiated informally each time. If the shop is not in the network, the fleet can still use it for certain work if they choose, but that work will be outside the coordination program's oversight. Rates, documentation, and repair quality on those events are the fleet's responsibility to manage directly, which is exactly what the fleet was doing before the switch for all of its repair spend.
The practical recommendation for most fleets is to route all repair spend through the coordination program for the first 90 days. The 90-day review then shows, on a per-event basis, whether the network is producing better outcomes than the informal shop relationships it replaced. Fleets that make exceptions for favorite shops during the transition period contaminate the baseline and make the 90-day comparison harder to draw cleanly.
A coordinated preventive maintenance program through a vetted nationwide truck repair network handles the per-unit record transfer, service window identification, go-live dispatcher briefing, and documentation standard as part of the onboarding process. If you are ready to begin the transition for your fleet or want to understand what the Phase 1 audit looks like for your specific unit count and OEM mix, reach out through the contact page. Bringing your current service history and fleet profile into that conversation produces a more specific onboarding plan than a general overview would.
This article draws on the following sources:
