Pacific Technology SolutionsTraining & software for the motor industry

Bay & Classroom / Time in the Bay

32Time in the Bay

Flat Rate and Clock Time: Two Clocks, Two Different Questions

One clock says what was sold, the other what happened. Most workshop reporting confuses them, and the gap between the two is where the money is. For a practical comparison of clock-based work records, see employee time clock software.

A dealer workshop runs two clocks at once and most reporting mixes them.

Book time — the flat-rate allowance for an operation — is what the customer is charged and, in most pay plans, what the technician is paid. It is a standard, set by the manufacturer or by a published guide.

Clock time is what actually happened.

They are different measurements answering different questions, and the gap between them is where workshop economics live.

Pay structures and warranty rules differ substantially by market and by manufacturer. What follows describes the general mechanics; the specifics for your network are in your own agreements.

What each one is for

Book time answers: what was this job worth? It is the unit of sale. Capacity, pricing, scheduling and technician pay are all denominated in it.

Clock time answers: what did it cost us? How long a bay was occupied, how long a technician was engaged, when the vehicle can be returned.

Confusing them produces specific errors:

Scheduling in book time overfills the workshop, because the day contains clock hours and the schedule was built from sold hours.

Promising a customer a return time from book time produces late deliveries, because book time excludes the waiting, the road test and the write-up.

Assessing a technician on clock time measures how busy the workshop kept them rather than how they performed.

Where book time comes from and what it assumes

Book times are established from timed observation under defined conditions: a competent technician, correct tooling, the vehicle accessible, parts to hand, no diagnosis required beyond what the operation covers.

Three consequences follow.

Routine operations are generally achievable and a practised technician beats them consistently, which is how efficiency above 100% is normal rather than exceptional.

Diagnostics are the weak point. A published time for "diagnose fault" assumes an average that does not exist. This is the single biggest source of unpaid workshop time, and it falls disproportionately on the best technicians because they get the difficult work.

Age and condition are not in the book. A ten-year-old vehicle in a corrosive climate does not release its fasteners on schedule. Warranty times in particular are set for the vehicle as designed, not as it has aged.

Warranty times are frequently tighter than customer-pay times for the same operation, which is a structural feature of the arrangement rather than an anomaly, and it is worth being explicit about with technicians rather than letting them discover it.

The gap, and what it tells you

Track sold hours against worked hours per technician, per job type, over time. The differences are informative.

Consistently above book on one job type across several technicians usually means the published time is wrong for your conditions — climate, vehicle age, or a tooling gap. That is a case to make to the manufacturer, and it is a case that needs data.

Consistently above book for one technician on work others beat is a training or tooling question.

Wide variance on the same operation points at the vehicles rather than the people — mixed model years, or a fault that presents differently.

Diagnostics far above book, always. Expected. The question is whether it is being absorbed as lost time or priced.

Where time disappears

The recorded gap between book and clock is only part of the loss. The rest is time that was never on a job at all.

Waiting for parts, which for many workshops is the largest single item.

Waiting for authorisation on additional work found during inspection.

Waiting for dispatch — the job exists, the technician is free, and nobody connected them.

Moving vehicles.

Comebacks, which consume time twice and are usually unbilled the second time. See comeback rate.

Helping another technician, which is valuable and invisible.

None of this appears in an efficiency figure. It appears as low productivity, and only if it is being recorded at all.

Pay plans and what they do to behaviour

Not a recommendation of any structure — an observation that each one produces predictable effects worth watching.

Flat-rate pay rewards speed against the book. It creates a strong incentive toward high-volume routine work and away from diagnostics, and it transfers the risk of parts delays and slow dispatch onto the technician, who is not paid while waiting.

Hourly pay removes that risk and removes the speed incentive.

Hybrid structures — a guaranteed base with flat-rate above it — are increasingly common precisely because the pure flat-rate model has become harder to recruit into.

The relevant point for measurement: whichever structure is in use, the numbers must be honest about what a technician can control. Holding someone on flat-rate pay accountable for productivity, when productivity is determined by dispatch and parts, is holding them accountable for the workshop's performance while also not paying them for it.

Recording it so the numbers mean something

Clock on and off at the job, not at the day. Otherwise clock time is an estimate made at 5pm.

Have codes for non-job time, and use them. Unrecorded waiting looks identical to unrecorded idling in the data, and the two need very different responses.

Record the operation, not just the repair order. A repair order with four operations gives you nothing about which one ran over.

Make it fast at the point of work. See time recording technicians will actually use.

And review the data with the technicians. They know why a job ran long, and that explanation is the part the system cannot capture.

What to actually do with the gap

Price diagnostics separately where the market allows, rather than absorbing them into an operation time that was never meant to cover them.

Take the evidence to the manufacturer where a published time is consistently unachievable across your workshop. This requires records, which is a reason to keep them properly.

Fix the productivity losses first. In most workshops there is more recoverable time in parts and dispatch than in technician speed. See the three ratios.

Schedule in clock hours and sell in book hours, and keep the two apart in every report.

The short version

Book time is the unit of sale. Clock time is what happened. They answer different questions.

Schedule in clock hours; quote and pay in book hours — mixing them overfills the workshop and produces late deliveries.

Diagnostics are where the book fails, and the cost falls on your best technicians.

Track the gap by job type, because a consistent gap across technicians is evidence about the standard rather than about the people.

And record non-job time with codes, or waiting and idling look the same in the data.

For official federal wage-and-hour guidance, see Fair Labor Standards Act guidance.