When a fleet has several vehicles needing body work, the default outcome is that they all go in together and the operation absorbs the whole hit at once. It does not have to work that way. Staging, batching and parts sequencing are scheduling decisions, they usually cost nothing extra, and they change the operational impact more than any discount would.

Staging: one or two units at a time

If six vehicles need work, the question is not how fast all six can be finished. It is how few can be out of service simultaneously while still clearing the backlog in reasonable time.

Sequencing them so one or two are in the shop at any point means the operation keeps running. Total elapsed time is longer. Total disruption is much lower, and disruption is what actually costs.

This matters most after a multi-vehicle incident, where the reflex is to send everything at once.

Batching: same work, several vehicles

Staging and batching pull in opposite directions and the balance depends on the work type.

Batching groups identical work across units: six bumper repairs, a run of mirror replacements, a set of roof reseals. Doing them together costs less per unit because setup happens once, and it is faster per vehicle.

The rule of thumb: batch fast work, stage slow work. Bumper and seal jobs batch well because each unit is only in for a day or two. Structural work should be staged, because those units are in for weeks.

Parts sequencing is where weeks get lost

On commercial repair, parts lead time drives the calendar far more than labor does. A vehicle sitting in a bay waiting for a panel is downtime that produced nothing.

Ordering against the teardown schedule rather than after teardown is the single largest lever. That requires assessing thoroughly enough up front to predict what will be needed, which is another reason documented assessment before authorization is worth the time it takes.

Ask any shop when they order parts relative to teardown. The answer tells you a lot about how the schedule will actually go.

Schedule into your own low points

Every fleet has a rhythm. Delivery operations have peak seasons. Contractors have weather patterns. Municipal fleets have budget cycles.

Planning body work into the trough rather than discovering it during the peak is straightforward and rarely done, because body work is usually reactive. Moving even part of it to planned work changes that.

A fleet condition survey is what makes planning possible: it tells you what needs doing now, what can wait a quarter, and what to watch.

What to ask a shop

Can you stage this so I am down fewer units at once? If the answer is that everything starts Monday, the shop is optimizing its own bay utilization rather than your operation.

When will parts be ordered? Against teardown, or after it.

Is that completion date against confirmed parts availability? An optimistic date that slips is worse than a realistic one, because you planned around it.

Can we batch the small jobs separately? Grouping the quick work keeps it from queuing behind a structural job.

The underlying point

Repair cost is visible on an invoice. Downtime cost is not on any invoice, and on most fleets it is the larger number. Scheduling is where you attack it, and it is nearly free.

The arithmetic behind that is in what a day of fleet downtime actually costs.

Building a rolling plan instead of a queue

The fleets that handle this best do not have a list of vehicles needing work. They have a schedule.

The difference is that a list gets worked through whenever there is capacity, which in practice means whenever something breaks badly enough to force the issue. A schedule assigns each unit a slot, which means the work happens before it becomes urgent and at a time you chose.

Getting from one to the other requires knowing what actually needs doing across the fleet, which is what a condition survey produces. Without that, planning is guesswork.

Sequencing rules that work

Never send two units doing the same job at once, unless the work is genuinely quick. Losing both vehicles covering a particular route or site at the same time doubles the disruption for no gain.

Put structural work in your quietest period. Those units are gone for weeks, so put them where weeks hurt least.

Group the fast work into a single push. Bumpers, mirrors, seals and lighting can move through in days. Doing eight of them across one fortnight is far less disruptive than eight scattered through the year, and cheaper per unit.

Keep one slot free. Something will get hit. If the schedule is completely full, an unplanned repair displaces planned work and the whole thing unravels.

What to give the shop up front

Scheduling well requires information the shop does not have unless you supply it.

Tell them your unit count and what each one needs. Tell them which days or weeks are your low points. Tell them which vehicles cover each other, so they know which pairs must not be in at the same time. Tell them whether anything is time-critical.

A shop that has that can build a sequence around your operation. A shop that just gets vehicles arriving will schedule around its own bay availability, which is a perfectly reasonable thing to do with the information it has.

Measuring whether it worked

Track vehicle-days out of service per month, not repair spend.

Repair spend goes up when you start doing planned work, which looks like the plan failing. Vehicle-days out of service is the number that should fall, and it is the one that reflects what the change was actually for.

How to Put Six Vehicles Through a Shop Without Losing Six Routes