If you searched this because your paycheck looks smaller than the hours you worked, here’s the direct answer: on flat rate, you are not paid for hours worked. You’re paid for hours flagged. Those are two different numbers, and the gap between them is the entire subject of this post.
Flat rate: pay follows the job, not the clock
Flat rate — also called flag-hour pay, book pay, or piece-rate in payroll paperwork — assigns every job a fixed number of hours before a wrench ever touches the car. A labor guide (or the shop’s own pricing, if it writes its own) says a water pump is 2.4 hours. The tech gets paid 2.4 hours of flag time for that job, whether it took 90 minutes or four hours fighting a seized bolt.
That’s the whole mechanism. Pay = flagged hours × the shop’s flat rate, summed across every job a tech touched in the pay period. Clock time never enters the math. A technician who works six hours and flags nine earns for nine. One who works ten hours and flags six earns for six.
This is why flat rate rewards speed and experience so directly, and why it punishes slow days so directly too. A tech who knows an alternator cold and can beat book time consistently is, in effect, being paid more per clock hour than the flag rate states. A tech stuck on a comeback, a diagnostic that won’t cooperate, or a day with three cars waiting on backordered parts is earning far less per clock hour than that same rate implies.
Hourly: the clock is the whole answer
Hourly pay needs no explaining beyond its name, which is precisely its appeal. A tech is paid for time on the clock, full stop, regardless of how many jobs got flagged or how fast any of them went. There’s no book-time lookup, no dispute over whether a job should have flagged at 1.2 hours or 1.8, and no incentive to rush a diagnostic to protect a flag rate.
The tradeoff runs the other way. A shop paying hourly is paying for attendance, not output — a technician moving at half speed costs the same per hour as one moving at full speed, and the shop absorbs that difference directly in lower billed hours per bay per day, which shows up on the labor half of its profit margin whether anyone’s watching for it or not.
Hybrid: a guarantee under the flag rate
Most shops that outgrow pure hourly don’t jump straight to pure flat rate. They land on some version of hybrid: a guaranteed hourly floor, with flag pay kicking in once a technician’s flagged hours for the period exceed what the guarantee alone would have paid. Below the line, the tech is paid hourly. Above it, they’re paid flat rate on the difference.
The appeal is obvious — a slow week doesn’t wipe out a paycheck, and a fast week still rewards speed. The cost is just as real: someone has to run two pay calculations every period instead of one, and reconcile them against whatever the payroll system actually cuts. That reconciliation is where a lot of shop owners quietly give up and default to straight hourly, not because it’s the better system, but because it’s the one their bookkeeping can survive without a spreadsheet nobody else understands.
What each system actually rewards
This is the part that matters more than the definitions. Flat rate and hourly aren’t just two ways to calculate a check — they’re two different sets of instructions for how a technician should behave, and techs respond to instructions.
Flat rate rewards speed, and speed under time pressure has a known failure mode: the comeback. A tech racing to beat book time on a brake job has every incentive to skip the extra five minutes checking a caliper slide pin that isn’t (yet) making noise, because those five minutes aren’t flagged and don’t pay. If the pin seizes three weeks later, that’s a comeback — a second visit, a second diagnostic, often unpaid warranty labor for the shop and the tech both. Flat rate doesn’t cause comebacks by itself, but it removes the only thing that was slowing a rushed tech down.
Hourly rewards the opposite failure mode: pace that never has to justify itself. A tech with no flag-rate pressure has no built-in reason to move with urgency, and a shop that doesn’t watch billed-hours-per-tech closely can go months without noticing that “busy all day” and “productive all day” have quietly stopped meaning the same thing.
Hybrid tries to blunt both edges and mostly does, but it doesn’t eliminate either. A tech comfortably above their guarantee still faces the same comeback incentive flat rate creates. A tech who never clears the guarantee faces almost none of flat rate’s upside and most of hourly’s lack of pressure. It’s a real improvement over picking one extreme, not a solution that erases the tradeoff.
What small shops actually run
There’s no single answer here, and anyone who states a national percentage with confidence is guessing — this is one of the areas where the honest move is to say so rather than print a number with no source behind it. What tends to hold true across independent 1–5-bay shops, based on how the pay conversation actually goes: newer or less experienced technicians usually start hourly or on a hybrid guarantee, because pure flat rate is unforgiving to someone still building speed. Experienced techs who know their numbers often prefer flat rate outright, because it’s the only system where their skill shows up directly in the check instead of getting averaged into an hourly wage set for the whole shop. And diagnostic-heavy or European-focused shops frequently keep diagnostic time hourly even when repair labor is flat rate, because diagnosis doesn’t compress the way a brake job does — an extra hour spent finding an intermittent short is time well spent, and a flag-hour system has no way to reward chasing it properly.
Fair flat rate needs to know who worked on what
Flat rate only works as advertised if the shop can actually tell who flagged which hours — and on a lot of estimates, that’s harder than it sounds. Jobs move between techs mid-repair. One tech starts a job, gets pulled onto something urgent, and a second tech finishes it. If the shop’s system only tracks “this RO has labor lines” and not which technician is attached to each one, the flag-hour math for a split job comes down to memory and a conversation at the end of the week — which is exactly how pay disputes start. BayDocket tracks a technician on every individual labor line, not just on the repair order as a whole, and rolls that up into a per-technician report of billed hours and labor revenue — the same billed-hours-per-tech data behind your shop’s own effective labor rate — so a shop running flat rate, hourly, or hybrid can see the actual flagged hours behind a technician’s pay instead of reconstructing them from memory.
That’s where our part ends, and it’s worth saying plainly: BayDocket has no payroll module. It tells you the flagged hours and the labor revenue per technician for a period; turning that into an actual paycheck — taxes, deductions, the guarantee-versus-flag reconciliation if you run hybrid — still happens in whatever payroll system you already use. We’d rather say that up front than let anyone assume otherwise.
Whichever system you run, the number underneath all of it is the same one covered in our labor rate post and its free calculator: what a flagged hour is actually worth once your real costs are in the math. Flat rate, hourly, and hybrid are three ways of splitting that number between the shop and the tech. None of them fix a door rate that’s already wrong.