Every transit maintenance director eventually hits the same fork in the road: do you pull a bus in for service when the odometer hits a number, or when the calendar says it's time? Get it wrong in either direction and the cost shows up somewhere — a stranded route during morning peak, a brake job that turns into a tow, or a wrench-hour spent on a bus that didn't need it yet. FleetRabbit's maintenance engine runs both triggers side by side so your shop never has to guess which one matters more. Book a live walkthrough or start a free trial to see your own fleet's PM compliance in real time.
Mileage-Based vs. Time-Based PM: Which Trigger Should Pull Your Bus Off the Road?
A buyer's guide for transit maintenance teams weighing odometer thresholds against calendar intervals — with the hybrid rule top-performing agencies actually run, and what FTA auditors expect to see either way.
Why This One Scheduling Choice Moves Your Whole Budget
Pick mileage-only and a bus that sits half the week for months at a time will quietly age past its service window while the odometer barely moves — rubber perishes, fluids break down, and seals dry out regardless of distance. Pick time-only and your highest-utilization buses run thousands of miles past the point where brake pads and engine oil actually need attention. Neither mistake is cheap.
Mileage-Based vs. Time-Based, Head to Head
Both triggers are measuring real wear — they're just measuring different kinds of it. Here's where each one actually wins.
Mileage-Based PM
Triggers off the odometer — Class A, B, C, and overhaul thresholds tied to distance.
- Matches wear that scales with distance: brake pads, tires, transmission fluid, belts
- Ideal for high-utilization urban routes and JIT-style duty cycles
- Catches real-world wear events that a fixed calendar would miss entirely
Time-Based PM
Triggers off the calendar — every 30, 90, or 180 days regardless of distance run.
- Catches degradation that happens whether or not the bus moves
- Keeps seasonal and spare-ratio vehicles from falling through the cracks
- Simple to plan shop labor and parts ordering around a fixed cadence
The Hybrid Rule Top Fleets Actually Run
Agencies with the strongest PM compliance rates don't choose one trigger — they track both for every vehicle and act on whichever threshold arrives first.
This is the same logic FTA-accepted PM frameworks are built on: track mileage, time, and engine hours per vehicle, and let the first threshold reached set the due date — never leave it to a shop foreman's memory.
A Standard Three-Tier PM Structure
Most transit fleets run a tiered PM structure like the one below, adjusted for their own OEM specs and duty cycles. Each tier carries its own dual trigger.
Fluid levels, visual walkaround, tire pressure and tread, ADA lift cycle test, lighting and belt checks.
Brake inspection and adjustment, coolant system check, steering and suspension, HVAC servicing.
Transmission service, propulsion diagnostics, full drivetrain inspection, annual DOT inspection alignment.
Where This Ties Back to FTA and NTD Reporting
Whichever trigger fires the work order, the paper trail is what your Triennial Review actually grades. Auditors are checking documentation discipline as much as wrench work.
TERM condition ratings need documented maintenance history tied to age and mileage — a Fair or Poor rating without a service log is a finding waiting to happen.
Vehicle inventory reported to NTD has to reconcile with your asset database — a bus with no logged PM history is a discrepancy auditors flag fast.
Standard urban buses carry a 12-year or 500,000-mile minimum useful life standard — vehicles pushed past that without a documented condition assessment invite capital-funding complications.
Lift and ramp cycling is one of the most commonly cited gaps in FTA reviews — it needs its own inspection trail, not a footnote in a general PM record.
Common Questions
Should every vehicle in my fleet use the same PM intervals?
No. Applying one fixed schedule across a mixed fleet wastes shop hours on newer, lower-mileage buses while under-servicing older or harder-working ones. Segment PM templates by vehicle model, duty cycle, and usage pattern instead.
What happens if a bus sits idle for a season?
Its mileage trigger stalls, but its time trigger keeps counting — which is exactly why the hybrid rule matters. A seasonal or spare-ratio vehicle still needs its calendar-based PM even at near-zero mileage.
How does FleetRabbit decide which trigger to act on?
FleetRabbit tracks mileage and elapsed time per vehicle continuously and automatically opens a work order the moment either threshold is reached — no manual comparison required.
Can this data feed our NTD and FTA reporting directly?
Yes. Every completed PM, inspection, and work order is logged against the specific vehicle, so compliance reports and asset condition summaries can be generated on demand instead of assembled by hand before an audit.
Stop guessing which trigger is overdue
FleetRabbit runs mileage and time-based PM side by side for every vehicle, auto-opens the work order, and keeps the audit trail ready for your next Triennial Review.
