How Many Employees Should I Schedule Each Shift at My Quick Lube?

The end-to-end process that turns receipts into a roster

Most quick lube schedules are built backward: the manager opens last week's grid, copies it forward, and adjusts only when someone requests time off. That produces a roster shaped by habit and seniority politics, not by demand. The fix is a repeatable five-step process you run once to install and then re-run quarterly.

Step one: set the per-tech daily gross-profit floor. Get ownership and management in one room and settle on the gross profit an average, competent tech should generate on an average day — turning bays, pulling cabin and engine air filters, checking fluids, and closing the recommended services the vehicle actually needs. In a lube shop this number is modest by design because the model is volume, not ticket size. A $200/day floor is a sane starting point for a shop with a typical mix of oil changes and moderate upsell attachment. Say it out loud to the floor in plain English so nobody is guessing what "good" means.

Step two: pull the real per-shift gross profit. Reach back three to six months in your POS or shop-management system and export gross profit — not revenue — by day and by day part. Revenue lies to you because a $110 full-synthetic ticket and a $110 conventional-plus-filters ticket carry very different margin. Average each block across the rolling window so one freak Saturday or one rained-out Tuesday doesn't warp the plan.

Step three: divide. Shift gross profit ÷ per-tech floor = techs for that shift. Run it down every block on the board. There is no room left for "we always put three on Saturday."

Step four: constrain by bays. The ratio produces a labor budget, not a floor plan. Two to three bodies per bay is the practical ceiling before people are tripping over each other and throughput actually drops. If the math orders five and you own two bays, you staff four or five and split them across lube, filter and fluid work, the greeter/upsell conversation, and the second bay's turnover — or you cut to what the bays can absorb and bank the labor.

Step five: place the counts on the traffic curve. The ratio hands you a quantity; ticket timestamps hand you the placement. Pull hourly car counts, find your pre-commute rush, lunch pop, after-five wave, and weekend wall, and stack the crew there. A backed-up line at 7:30 a.m. sends that car to the competitor two blocks over, and you never see it again.

Where the schedule creates or leaks revenue

Labor in a quick lube is not a fixed cost you minimize — it is the throughput valve. Under-staff and you leak revenue at the top of the funnel; over-staff and you leak it out of the bottom line. Both leaks are measurable, and knowing which one you have determines whether you add a body or cut one.

The under-staffing leak is bounce. A quick lube's entire promise is speed. When the line backs up past two or three cars deep, a meaningful share of arrivals simply drive on. You never see them in the POS, which is exactly why this leak is invisible in a P&L review — the missing revenue never became a record. The tell is a car-count curve that flattens or dips during your busiest hour instead of peaking. If Saturday 9-11 a.m. shows fewer cars than Saturday 8-9 a.m. despite being your heaviest traffic window, you are almost certainly turning cars away rather than running out of demand. Watch drive-off patterns directly for a week: park someone at the door counting cars that pull in, look at the line, and leave.

The second under-staffing leak is upsell abandonment. When the crew is buried, the recommended-service conversation is the first thing that gets skipped. Nobody walks the customer to the bay to show them the filter. Nobody explains why the coolant looks the way it does. That conversation is where the gross profit above the base oil change lives, and it is the single most compressible part of the job under time pressure. A shop running one body short during peak will often show normal car counts and quietly degraded average ticket — which is why you should track average gross profit per car by hour, not just car count by hour.

The over-staffing leak is straightforward but usually under-measured. An idle tech on a slow Tuesday middle costs you their fully loaded hourly rate — wage plus payroll taxes, plus any benefit load — for every hour the bay sits empty. Over a year, one unnecessary body on four slow weekday middles is a real number that comes straight out of owner's discretionary earnings. The ratio catches this automatically: if a shift's gross profit divides to less than one, the shift is telling you it barely justifies opening the bay door.

There is a third, subtler leak: mis-timed labor. You can be at the correct total weekly headcount and still lose money if the bodies are in the wrong hours. Five techs spread evenly Monday through Friday is not the same as five techs concentrated on the two mornings that produce forty percent of the week's gross profit. This is the leak most schedules have, because copying last week forward preserves headcount totals while quietly ignoring when the register fires.

Cross-training is the hedge against all three. A tech who can run the pit, the upper bay, the greeter conversation, and the register lets you flex a thin shift without losing the upsell. A single-skill crew forces you to over-staff just to guarantee every station is covered, which means you are paying for redundancy the ratio never asked for.

Concrete numbers, ratios, and benchmarks to anchor the math

Every number below is a starting anchor to be replaced by your own data within one quarter. The point is to give you something defensible to divide by on day one, not a permanent truth.

Per-tech daily gross-profit floor. Start at $200/day for a standard quick lube with a conventional-to-synthetic mix. Adjust upward if your ticket skews heavily synthetic or you attach filters, wipers, and fluid services at a high rate. Adjust downward if you are carrying trainees or running a bare-bones oil-only menu. The floor is a *team average*, not a per-person quota — a veteran will clear it before lunch and a three-week rookie will not clear it at all, and that is fine as long as the crew average holds.

Bay throughput. A well-run quick lube bay turns a car in roughly 10 to 15 minutes of bay time for a standard service, which sets a hard theoretical ceiling of four to six cars per bay per hour. Real-world sustained throughput lands well below that once you account for check-in, upsell conversations, payment, and vehicle-specific complications. Plan against your own measured cycle time, not the theoretical ceiling.

Bodies per bay. Two to three. Below two and you cannot run pit-and-upper simultaneously on a two-level bay. Above three and marginal productivity per added body goes negative — they queue for tools and step on each other's work.

Rolling window for averages. Three to six months. Shorter than three and one bad week distorts the plan; longer than six and you are scheduling against a demand curve that no longer exists.

Recalculation cadence. Refresh per-shift gross-profit averages quarterly. Revisit the per-tech floor annually, or immediately when average ticket or car count moves hard enough that you feel it without checking a report.

Worked example — a two-bay shop. Say the rolling three-month pull produces these averages:

• Saturday open (7 a.m.–1 p.m.): $1,000 GP → ÷ $200 = 5 techs → capped at 6 by bay math, so staff 5.
• Saturday close (1 p.m.–6 p.m.): $600 GP → 3 techs.
• Friday open: $800 GP → 4 techs.
• Weekday opens (Mon–Thu): $600 GP → 3 techs each.
• Weekday middles (Mon–Thu): $400 GP → 2 techs each.
• Sunday, if open: $300 GP → 1.5, round to 2 for safety coverage.

Total weekly labor-hour demand falls out of that grid directly, and you can now see the shape of the week: the weekend and the weekday opens carry the business, and the Tuesday middle is a candidate for consolidation.

The rounding rule matters. Round up when the shift is a peak block where a backed-up line costs you a bounced car. Round down when the shift is a lull where an idle body costs you nothing but wage. Peak hours round up; dead hours round down. That single asymmetry is worth more than any refinement to the ratio itself.

Labor as a percentage sanity check. Whatever the ratio produces, cross-check total scheduled labor cost against gross profit for the week. If the ratio is producing a labor line that is drifting out of the range your P&L can sustain, your per-tech floor is set too low — raise it and re-divide rather than manually overriding individual shifts.

Pitfalls that break the ratio and how to avoid them

Dividing revenue instead of gross profit. This is the most common failure. Revenue-based staffing over-staffs low-margin volume shifts and under-staffs high-margin ones. If your system only exports revenue easily, do the work once to build a gross-profit export — it is the difference between the ratio working and the ratio quietly lying to you.

Setting the floor as a stretch goal. If you set $200 as an aspirational target nobody currently hits, every shift divides to a headcount below what the work actually requires, and you chronically under-staff. The floor must describe what an ordinary tech giving ordinary effort actually produces today. Ambition belongs in the comp plan, not in the denominator.

Letting one outlier week set the average. A single Saturday with a fleet account dropping eight vehicles will inflate a three-month average enough to permanently over-staff that block. Trim obvious outliers before averaging, or extend the window.

Ignoring the bay ceiling. The ratio does not know how many bays you own. A shop that mechanically staffs whatever the division produces will eventually put six people in a two-bay shop and watch throughput fall while payroll rises. The bay cap is a hard constraint applied after the division, every time.

Scheduling to headcount instead of to hours. "Five techs on Saturday" is not a schedule. Five techs where two arrive at open, two at 8, and one at 10 is a schedule. Staggered starts are how you match a smooth headcount number to a spiky traffic curve without paying for coverage during the ramp.

Forgetting breaks and lunches. A five-tech shift is not five techs for the entire block. Build in overlap so the peak hour is never covered by four people because the fifth is at lunch. In practice this means adding a partial shift that spans the break window rather than adding a full body.

Not accounting for seasonality and local disruption. Road construction that reroutes traffic, a large employer opening or closing nearby, or a seasonal swing in commuting patterns will move your curve underneath you. Quarterly re-averaging catches most of this; a major local event warrants an immediate re-pull rather than waiting for the quarter.

Overriding the ratio for personnel reasons. The moment a manager pads a shift to give a favored tech hours, the system stops being a system. If someone needs more hours, the answer is to give them a shift the ratio says needs a body, not to inflate one it says doesn't.

Treating a labor shortage as a math failure. The ratio gives you the ideal. A tight hiring market gives you a shortfall. When you cannot fill the plan, feed the richest hours first — weekend mornings before weekday middles — let the thin shifts run thin, and cross-train so one body covers more stations. The objective is maximum gross profit per available body, not forcing a headcount you cannot hire.

A selection checklist for the shift you are about to publish

Before a schedule goes out, run it through a fixed sequence of questions. This takes five minutes and catches the failures above before they cost you a week.

Ask, in order: Is the gross-profit figure I divided by current within the last quarter? Did I use gross profit, not revenue? Does the resulting headcount respect the two-to-three-per-bay cap? Are the start times staggered against the actual hourly car counts, or did I just assign everyone the same open? Is peak coverage protected through the break window? Did I round up on peaks and down on lulls? If any shift divides to less than one, have I considered folding those hours into an adjacent block instead of opening thin?

That last question is the one owners skip. A shift that produces $150 in gross profit is not a staffing problem — it is an hours-of-operation problem. The honest move is often to consolidate two weak blocks into one solid one rather than propping up a shift that barely earns the lights.

Choosing the software that carries this. The method matters more than the app, but tooling differs in one respect worth checking: whether it can pull sales or car-count data automatically. Tools that connect to a POS can suggest coverage against projected demand, which is the closest off-the-shelf relative of the ratio you are running. Lighter tools handle publishing, availability, swaps, and mobile punch-in but expect you to arrive with the headcount already decided — which is fine, because you will have. Match the pricing model to your shape: per-location pricing tends to favor shops with many part-time hourly techs, per-user pricing tends to favor a small, stable, veteran crew. And if you operate across county or state lines, prioritize built-in labor-law guardrails for breaks, overtime, and predictive-scheduling rules.

Related questions

Does this ratio work for a single-bay express shop?

Yes, but the bay cap dominates. With one bay you are choosing between two and three bodies regardless of what the division says. Use the ratio to decide *when* to run three versus two, and to identify which hours are not worth opening at all.

How do I handle a tech who consistently underperforms the floor?

The floor is a team average, so one person below it is a coaching issue, not a scheduling one. Pair them on high-traffic shifts where volume carries the average, coach the upsell conversation specifically, and re-evaluate after a full quarter of data.

Should managers count toward the headcount?

Only if they are actually turning bays. A working manager who runs the greeter conversation and closes upsells counts as a partial body. A manager doing inventory, hiring, and vendor calls does not — counting them creates a phantom tech and a chronically thin floor.

What if I run lube plus light mechanical work?

Split the analysis. Pull gross profit separately for lube versus mechanical, set a different per-tech floor for each, and staff them as two overlapping schedules. Mechanical work has longer cycle times and higher margin, so a shared floor will distort both sides.

How long before the numbers stabilize?

Expect one full quarter. The first pass gives you a defensible starting grid; the first quarterly re-average is where you find out which blocks you consistently misjudged and correct them.

FAQ

What if a shift's average gross profit is lower than my per-tech target?

Do the division anyway. If it comes back under 1.0, the shift is telling you it barely justifies opening. The usual right move is to fold those hours into an adjacent block and turn one strong shift into the plan rather than propping up a weak one. If you must stay open for brand or convenience reasons, run skeleton coverage and accept it as a marketing cost, not a profit center.

How do I handle wildly different weekend versus weekday volume?

Lean on rolling three-to-six-month averages per block so a single monster Saturday or a rained-out Tuesday doesn't distort the count. Weekends routinely divide to two or three times a weekday block — that's the math working, not an anomaly. Re-run averages quarterly, because seasonality, a new employer nearby, or a construction detour will move your traffic curve underneath you.

Does the formula still hold with mixed skill levels and pay rates?

It holds, because the ratio keys on gross profit per tech, not on anyone's hourly wage. A seasoned tech out-produces a rookie, but $200 is a crew average, not a per-person quota. If your bench is deep, raise the floor to reflect what that crew genuinely produces. If you are carrying trainees, ease it down until they are up to speed, then re-divide.

Does the math change with a dual-bay or multi-bay setup?

The division runs the same, but the bay count caps the answer. Figure two to three techs per bay as the practical ceiling. If the math orders five and you own two bays, staff four or five and rotate them through pit work, filters, fluid checks, and the upsell conversation so nobody stands idle. The ratio sets the labor budget; your bay count sets how you spend it.

How often should I recalculate?

Refresh per-shift gross-profit numbers quarterly off the latest three-to-six-month pull. Revisit the per-tech floor annually, or sooner if average ticket or car count moves hard enough to notice without a report. That cadence keeps the roster chasing the trend the shop is actually living rather than one from two summers ago.

Do I need scheduling software to run this?

No. A spreadsheet with one row per day part, a gross-profit column, and a division column is functionally complete. Software earns its cost on execution — publishing, availability, swaps, punch-in, and labor-law compliance — not on the arithmetic. Prove the method for a month before you pay for anything.

Sources

• U.S. Bureau of Labor Statistics, Occupational Outlook Handbook — Automotive Service Technicians and Mechanics: https://www.bls.gov/ooh/installation-maintenance-and-repair/automotive-service-technicians-and-mechanics.htm
• U.S. Department of Labor, Wage and Hour Division — Fair Labor Standards Act overtime pay: https://www.dol.gov/agencies/whd/overtime
• U.S. Small Business Administration — Manage your finances: https://www.sba.gov/business-guide/manage-your-business/manage-your-finances
• IRS — Understanding Employment Taxes: https://www.irs.gov/businesses/small-businesses-self-employed/understanding-employment-taxes
• Automotive Oil Change Association: https://www.oilchange.org/
• National Institute for Automotive Service Excellence (ASE) certification: https://www.ase.com/
• SCORE — Business planning and financial management resources for small business: https://www.score.org/
• Harvard Business Review — The Costs of Unstable Work Schedules: https://hbr.org/2015/03/employers-put-workers-on-call-and-that-hurts-productivity

Related on PULSE

• [How Do I Know Where, When, and How Many People to Schedule at Each of My Multi-Unit Retail Locations?](/knowledge/tl0001)
• [How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?](/knowledge/tl0002)
• [How Do I Know How Many Cooks and Servers to Schedule Each Shift at My Pizza Restaurant?](/knowledge/tl0003)
• [How Many Salespeople Should I Schedule Each Day on My Furniture Store Floor?](/knowledge/tl0004)
• [How Do I Decide How Many Reps to Schedule at Each Store in My Mattress Retail Chain?](/knowledge/tl0005)