Two techs do the same brake job on the same bus — one takes three hours, the other six — and without a standard time you can't tell a hard job from a slow one. That gap is what flat rate labor times close. Bus shop flat-rate labor times give every repair an expected number to cost, estimate, and measure actual hours against. Book a demo to see actual labor hours captured on every work order.
How to Set Flat-Rate Labor Times in a Bus Shop
A flat-rate (standard repair time) is the expected hours a job should take — the backbone of consistent costing, honest estimates, and technician measurement. Here's where those times come from, how to build your own from your data, and how to use actual-vs-standard the right way.
Flat-Rate vs. Actual Time: What You're Really Choosing
There are two ways to account for labor, and knowing the difference is the whole foundation. Flat-rate bills a fixed, expected time for a defined job; actual bills the exact hours the tech spent. Most fleet shops use standards for planning and actuals for reality.
A fixed number of hours a defined job should take. Predictable to cost and schedule, and it rewards an efficient tech who beats it. But it assumes a clean job with the failure already identified.
The real hours spent on the repair. Always accurate to what happened, but unpredictable up front — you can't quote or plan a bay around a number you don't know until the job is done.
A standard time is a reference for a defined operation under stated conditions — a starting point, not a promise. It assumes the failed part is already identified and excludes surprises found mid-repair. Treat it as the plan; capture the actual to see how it held.
The Four Sources of a Flat-Rate Labor Time
A standard time can come from four places, and the best shops mix them. Each has a use — but only one is truly tuned to your buses, your techs, and your bays.
Commercial labor guides
Published references that distill thousands of real-world hours into per-task times. A fast benchmark — but generic to the vehicle, not your shop.
OEM repair procedures
Manufacturer times for a specific operation. Precise for that model, though often set for warranty reimbursement rather than your reality.
Industry SRT surveys
ATA's Technology & Maintenance Council runs an annual Fleet & Service Provider Average SRT Survey — the 2023 edition covered 103 common tasks, coded to VMRS standards.
Your own repair history
The times your techs actually post on your buses in your bays. The most accurate source there is — and the one only your own work-order data can give you.
Here's the bus-specific catch: most published SRTs are built around heavy trucks, not passenger buses. Use a guide as a starting benchmark, then tune it against what your own shop actually posts — that's where the real accuracy lives. Sign up free and start building the repair history your standards need.
How to Build Bus Shop Flat-Rate Labor Times From Your Data
The most defensible standards are the ones you build from your own actuals. It's a four-step loop, and it gets more accurate every time you run it. Start with the jobs you do over and over.
Capture actual time on every job
Log the real hours a tech spends on each work order. No captured actuals, no data to build a standard from.
Group by repeatable job
Pull the recurring repairs — brake jobs, alternators, door actuators — and look at the spread of actual hours across techs and buses.
Set a fair standard
Pick a time a competent tech should hit under normal conditions — not the fastest, not the slowest. Get your foremen to agree it's fair.
Refine as data grows
Every job you post sharpens the average. Revisit standards as the sample grows and as bus models and conditions change.
The loop only works if the actuals are captured cleanly in the first place — which is exactly what a work order is for. The more jobs flow through the system, the more accurate your standards become. Book a demo to see recurring-job actuals ready to build standards from.
Actual vs. Standard: What the Gap Is Telling You
A standard time is only useful once you compare actual hours against it. But the gap isn't a pass/fail grade — it's a diagnostic. The same variance can mean three very different things, and reading it wrong hurts morale and misses real problems.
Beat the time
An efficient, experienced tech routinely beats book time. That's the system working — recognize it, and consider whether the standard is too loose.
On the number
Actuals clustering around the standard means it's set right. This is the baseline you want most jobs to land near.
Missed the time
Could be a newer tech still learning, a genuinely harder job than the standard assumes, or real inefficiency. Look before you judge.
Newer or training techs normally start over the standard and beat it as they gain reps. A consistent overage on one job across every tech usually means the standard is too tight, not that everyone's slow. Use the gap to coach and to refine — not to punish. Sign up free and see actual-vs-standard on every completed job.
The Four Times You Have to Keep Separate
Flat-rate costing goes wrong when different kinds of time get blended together. Keep these four distinct on every job and your labor numbers stay honest — and your invoices stay defensible.
- 1
Quoted time
The standard hours you estimated for the defined job before work started.
- 2
Authorized time
What was approved — including any additional work found and signed off mid-repair.
- 3
Worked time
The actual hours the tech spent turning wrenches on the job.
- 4
Billed time
What lands on the final invoice — consistent with the approved scope, not a surprise.
Standards don't include work discovered as the repair progresses — that's a separate line with its own time and its own authorization. Blur these together and you either eat cost or surprise the budget. Keep them clean and every labor dollar traces to a decision.
Why a Bus CMMS Makes Flat-Rate Times Actually Work
Flat-rate standards are only as good as the labor data behind them — and that data has to be captured on the job, cleanly, every time. That's the part a paper work order or a memory can't do. Here's the difference.
- Standards guessed or pulled from a generic truck guide
- No clean record of the hours techs actually spend
- Can't tell a slow job from a genuinely hard one
- Labor costing varies by whoever wrote the ticket
- No way to refine a standard as the fleet changes
- Actual labor hours logged on every work order, per tech
- Recurring-job history ready to build your own standards
- Actual-vs-standard visible on completed jobs
- Consistent labor costing across every ticket and tech
- Standards you can refine as the data and fleet grow
This is the Work Orders and Team Management side of BusCMMS doing the unglamorous work: capturing the labor hours that let you set fair standards and see when actual drifts from them. The software gives you the data — you set the standard.
A Maintenance Manager Who Stopped Guessing at Labor
"I used to cost brake jobs off a truck labor guide and hope. Then I actually looked at what my guys were posting: our door-actuator job ran anywhere from two to five hours with no rhyme or reason, and I couldn't tell if it was the tech or the bus. Once every work order captured real labor time, I built our own standards off six months of actuals — and the variance told a story. One older model genuinely took longer; one tech needed coaching. Same jobs, but now I can quote them, plan the bay around them, and know what 'fair' looks like."
That's the shift: from a guessed number off a generic guide to a fair standard built from your own shop. The data was always there in the work — it just had to be captured.
Bus Shop Flat-Rate Labor Times: The Bottom Line
Bus shop flat-rate labor times turn "it took as long as it took" into a number you can cost, schedule, and measure against. Start from a guide or the TMC survey for a benchmark, but tune it to your buses — published SRTs lean toward heavy trucks, not passenger fleets.
The most accurate standard is the one you build from your own captured actuals, read as a diagnostic, not a grade. Keep quoted, worked, and billed time separate, capture labor on every work order, and your shop runs on data instead of hope. Book a demo and see your labor standards built from your own shop's data.
Frequently Asked Questions
What are flat-rate labor times in a bus shop?
Flat-rate labor times — also called standard repair times (SRTs) — are the expected number of hours a defined repair should take under normal conditions. Instead of billing the exact hours a technician spends, the shop uses a fixed standard for that job, which makes costing predictable, lets you quote a price up front, and gives you a benchmark to compare actual hours against. A standard time is a reference point for a defined operation, not a guarantee: it typically assumes the failed part is already identified and does not include additional work discovered as the repair progresses, which is quoted and authorized separately.
Where do bus repair labor time standards come from?
There are four main sources. Commercial labor guides distill thousands of real-world repair hours into per-task times and make a fast benchmark, though they are generic to the vehicle. OEM repair procedures give precise times for a specific model, but are often set for warranty reimbursement. Industry surveys — notably ATA's Technology & Maintenance Council annual Fleet & Service Provider Average SRT Survey, whose 2023 edition covered 103 common tasks coded to VMRS standards — provide aggregated fleet data. The most accurate source, though, is your own repair history: the actual hours your technicians post on your buses in your bays. Because most published SRTs lean toward heavy trucks, bus shops should use a guide as a starting point and tune it against their own data.
How do I build my own flat-rate labor times?
Build them from your own actuals in a four-step loop. First, capture the real labor hours a technician spends on every work order — without captured actuals you have nothing to build from. Second, group the recurring jobs (brake jobs, alternators, door actuators) and look at the spread of hours across technicians and buses. Third, set a fair standard: a time a competent technician should hit under normal conditions, agreed on by your foremen — not the fastest or slowest observed. Fourth, refine it as the sample grows and as bus models and conditions change. Every job you post sharpens the average, so the standards get more accurate the more you use the system.
How should I compare a technician's actual hours to the standard?
Treat the gap as a diagnostic, not a pass/fail grade. A technician who routinely beats the standard is efficient — recognize it, and check whether the standard is too loose. Actuals clustering near the standard mean it's set right. Going over the standard can mean three different things: a newer or training technician still gaining reps (they normally start over and beat it later), a genuinely harder job than the standard assumes, or real inefficiency. A consistent overage on one job across every technician usually signals the standard is too tight rather than that everyone is slow. Use the variance to coach and to refine the standard, not to punish.
How does a bus CMMS help with flat-rate labor times?
A purpose-built bus CMMS like BusCMMS supports flat-rate labor management by capturing the actual labor hours a technician spends on every work order. That gives you two things you can't get from paper: the accumulated repair history to build your own standards from what your shop really posts, and the ability to see actual hours against your standard on completed jobs so you can spot training needs, genuinely hard repairs, or standards that need adjusting. The software captures and compares the labor data and keeps quoted, worked, and billed time organized per work order — the standard-setting judgment stays with the shop, but it's now made from real data instead of a guess or a generic truck guide.
