A flag hour is a price, not a measurement.
That’s the whole confusion, and it explains why a technician can work an eight-hour day and get paid for six, or for eleven. The job is assigned a number of hours before anyone touches it. That number gets billed to the customer and paid to the tech. The clock on the wall is not consulted.
So: a water pump flagged at 2.4 hours bills 2.4 hours of labor and pays the technician 2.4 flag hours. Finish it in ninety minutes and it still flags 2.4. Fight a seized bolt for four hours and it still flags 2.4. Multiply flagged hours by the technician’s flag rate — say 2.4 × $32 — and you have that job’s share of the paycheck. Sum every job in the period and you have the check.
Flag hours vs flat rate vs book time: same thing, different half of the sentence
These come up as separate searches, so it’s worth being direct: they are not different systems.
“Flat rate” describes the pricing side — the job costs a flat, pre-set amount of labor no matter how long it runs. “Flag rate” or “flag pay” describes the payroll side — what the tech earns is their rate times the hours they flagged. “Book time” is the number itself, named after the printed labor guides shops used before the guides moved onto screens. “Flagged hours” and “flag time” are the same unit again.
If a shop tells you it pays flat rate and a tech at the same shop tells you he’s paid flag hours, nobody is contradicting anybody.
Flag hours calculator: the arithmetic, by hand
There is no calculator to buy here, because the whole computation is one multiplication per job and one sum per period. Flagged hours × flag rate, job by job, added up:
| Job | Flagged hours | Clock time | Flag rate | Pays |
|---|---|---|---|---|
| Water pump | 2.4 | 1.5 h | $32 | $76.80 |
| Front brakes | 1.4 | 1.2 h | $32 | $44.80 |
| Intermittent electrical | 1.0 | 3.1 h | $32 | $32.00 |
| Oil service | 0.5 | 0.4 h | $32 | $16.00 |
| Day | 5.3 | 6.2 h | $169.60 |
That day flagged 5.3 hours against 6.2 on the clock. The electrical job is why — it flagged one hour and ate three — and it is the shape of every flat-rate complaint you will ever hear. The shop’s side of the same table is different arithmetic: those 5.3 flagged hours billed to customers at the door rate are the day’s labor revenue, and billed hours against collected dollars is the shop’s effective labor rate. The labor rate calculator runs that side for free; the technician side is the table above, and a spreadsheet is enough.
Where the number actually comes from
A flag hour has to come from somewhere, and where it comes from decides how many arguments a shop has about it. The clean answer is a licensed labor guide — Mitchell 1, ALLDATA, MOTOR — which publishes times per operation per vehicle, researched and updated, so that “2.4 hours for a water pump on that engine” is an external fact both the writer and the tech can point at. A shop with a guide subscription has settled the question before it comes up.
A great many small shops don’t have one. The subscriptions are priced for shops with more bays than a two-lift operation has, and the owner-operator who’s also the service writer has usually decided that money buys something else this year. So the shop sets its own times, and the source is memory: this job took about this long the last three times, call it two hours, write two.
That works. It is genuinely how a large share of independent shops price labor, and there’s nothing dishonest about it. But it changes what a flag hour is. It stops being an external number the shop looks up and becomes a shop policy the shop authored — and shop policies drift, because the person authoring them is doing it from memory at eight in the morning with a customer waiting.
Some shop owners will disagree with this, and that’s fine: if your book time isn’t written down somewhere the technician can see before the job starts, you don’t have flag hours. You have a negotiation.
The tech finishes a job in forty minutes that was quoted at 1.5 and gets a raised eyebrow. Next month the same job is quoted at 1.0 by a different writer on a busy morning, and the tech notices, because techs always notice. Neither number was wrong. There just wasn’t a number — there was a habit, and habits vary by who’s holding the pen and how the morning is going. A written time can be argued with, revised, and agreed to. An unwritten one can only be resented.
The fix is boring and it works: keep your repeat jobs as saved templates with their hours already on them, so the front counter drops in the same 1.4-hour brake job every time instead of re-deciding it. That’s what canned jobs are for in BayDocket, and it’s the closest thing a shop without a guide subscription has to a book — your own times, written once, applied identically.
Comeback labor sits off to the side of all this. Plenty of flat-rate shops flag a comeback at zero, which means the tech redoes the work unpaid. Whether that’s fair discipline or a way of making one person absorb a shop-wide quality problem is an argument that goes both ways, and nothing in this post settles it.
The other half of fair flagging: who gets the hours
Assigning a time is one job. Attaching it to the right name is another, and it’s the one that quietly breaks.
Jobs move. A tech starts a control arm, gets pulled onto a car the customer is waiting on, and someone else finishes it. At the end of the week, three hours are flagged on that repair order and two people remember doing the work. If the shop’s system only knows that the repair order has labor lines on it, the split comes down to a conversation, and that conversation is where pay disputes are born.
BayDocket attaches a technician to each individual labor line rather than to the repair order as a whole, so a split job splits its hours the way it actually happened. A tech can claim the unassigned labor lines on a job from their own phone; the claim only takes lines nobody is on yet, so it can never pull a line off another technician. The reporting side rolls that up per technician — hours, labor revenue, and how many repair orders they touched over a date range — and a technician can open their own numbers without seeing anyone else’s, because comp is nobody else’s business.
The honest half
Three things, since this post has spent a section telling you to write your times down.
BayDocket has no labor guide. If you want researched times per operation per vehicle, you’ll be buying that from Mitchell, ALLDATA or MOTOR and reading it alongside us. Canned jobs hold your times, which is a real answer for a shop already setting its own, and not an answer at all for a shop that wants the book.
Technician attribution is read live rather than frozen onto the invoice. That was a deliberate call — it means you can still fix an assignment after a job is invoiced, on the Friday when payroll surfaces the mistake. The cost is that reassigning a technician after the fact changes how a past period’s hours split between techs when you re-run the report. The money totals don’t move; the names under them can. Know that before you use a two-month-old report to settle an argument.
And there’s no payroll module. We can tell you the flagged hours and labor revenue per technician for a period. Turning that into a check — taxes, deductions, the guarantee-versus-flag reconciliation if you run hybrid — still happens wherever it happens today.
If you’re deciding between flat rate and hourly rather than trying to define the unit, flat rate vs hourly mechanic pay covers what each system rewards and where each one fails. And if flagged hours are landing but the money isn’t, the gap between the rate you charge and the rate you keep is effective labor rate — usually a bigger number than anyone expects, and the labor rate calculator does that arithmetic for free.