When a vehicle is off the road waiting for parts, control comes from one thing above all else. Treat it as a live maintenance decision, not a parked-up job that can be picked up later. The moment it is stood down, we need one record that says what failed, whether it affects roadworthiness, what parts are needed, who owns the next action, and when the case must be reviewed again.
That is the practical answer to how to track vehicles waiting for parts in the workshop. Not a complicated system. A clear board, one agreed status for each vehicle, dates that mean something, and a routine for updating ETAs without three people asking the same question all day. If that record is weak, vehicles disappear into corners of the yard, PMI dates drift, MOT bookings get missed, and nobody can show DVSA why a decision was made.
Why waiting for parts becomes a control problem
Vehicles waiting for parts are easy to lose because they sit between normal workflows.
A booked service has a slot, a technician, and a handover point. A finished repair gets invoiced and leaves. A breakdown is noisy enough that everyone knows about it. A parts delay is different. The job has started, but it cannot move. The vehicle is present, but unavailable. The defect may be safety-critical, or it may not be, but either way somebody has to keep making decisions while nothing physical changes on the floor.
That is where control starts to slip.
In a five to 100 vehicle operation, the same person often covers transport planning, supplier chasing, customer calls, and O-licence responsibility. If the workshop writes “WFP” on a job card and leaves it at that, the transport office still needs to know whether the vehicle can be returned to service temporarily, whether the booked PMI needs moving, whether the MOT slot should be protected, and whether a replacement vehicle is needed. If those answers are not recorded properly, people fill the gaps with memory.
Memory is not an audit trail.
The cost is not only downtime. It is also bad communication. Drivers ask when the vehicle is coming back. Planners promise work on a unit that is still missing a brake chamber or NOx sensor. Customers are told “we’re waiting on parts” for three days in a row, with no better answer than yesterday. Technicians strip another vehicle because they assume the first one will not be ready this week. Then the part arrives and the bay is full.
There is also a compliance problem. If a vehicle is stood down because of a defect that affects roadworthiness, the record must show that it was not put back on the road until repaired. If the defect sits close to a PMI, preventative maintenance inspection, or MOT date, the maintenance plan needs adjusting. If DVSA asks why an inspection interval was exceeded, or why a prohibition-related issue was not dealt with promptly, “we were waiting for parts” is not enough on its own. We need dates, decisions, and evidence of control.
That matters even more in the UK because operator licensing expectations are specific. A workshop can be busy and still be judged on whether systems are effective. The Traffic Commissioner is interested in control, not excuses. OCRS is influenced by outcomes, not by whether the parts supply chain was frustrating that week.
What to record the moment a vehicle is stood down
The key point is simple. Record the stand-down as an operational event, not just a workshop note.
At minimum, we should capture these fields straight away:
Vehicle identity Registration, fleet number, trailer number if relevant, and location. If the vehicle is at a dealer, tyre supplier, bodyshop, or parked at an outstation, say so clearly.
Date and time stood down Not “today” or “this morning”. Use the actual date and time the decision was made that the vehicle could not return to service.
Reason for stand-down A short plain-English fault description. For example, “NS rear brake chamber leaking”, “AdBlue pump failed”, or “cracked spring hanger found during PMI”.
Roadworthiness decision This is the important one. State whether the vehicle is:
- off the road, not to be used
- restricted use only, pending repair and management decision
- waiting for parts but still serviceable
If restricted use is ever allowed, the reason and limits need recording. In many cases the correct answer is simply off the road. If the defect affects roadworthiness, say so.
Source of defect Driver report, walkaround check, PMI, MOT preparation, roadside breakdown, tachograph defect, DVSA encounter, or workshop finding during another job.
Parts required List the actual parts needed, quantities, and if known the supplier. “Brake parts” is useless. “1 x Type 24 brake chamber, 2 x mounting nuts, 1 x air line fitting” is usable.
Parts status Ordered, quoted, awaiting authorisation, back order, no ETA, due next day, collected, delivered, wrong part supplied, or superseded part issue.
Expected date Not just for the part. Record the current expected date for the vehicle to be ready, even if it is provisional.
Owner One named person for the next action. Usually parts desk, workshop controller, transport manager, or service advisor. Not “workshop”.
Next review date and time This stops the job being reopened every hour. If the supplier says they will update at 3pm tomorrow, the review point is 3pm tomorrow, not ten random chases before then.
Related bookings and deadlines Next PMI, preventative maintenance inspection due date if that is how you label it internally, MOT booking, tyre inspection, LOLER if relevant to ancillary equipment, and any planned route commitments that are already affected.
Authority and cost status If authorisation is needed, record who must approve and whether approval has been requested or received. We covered this in more detail in our piece on repair authorisation that stops cost drift in the workshop.
That may sound like a lot, but in practice it is a few disciplined lines. The point is to make the first record strong enough that everybody else can work from it.
How to build a waiting-for-parts board that people will actually use
If the board takes ten minutes to update, it will not be updated. If the statuses are vague, people will interpret them differently. Keep it simple enough for a busy workshop floor.
A workable waiting-for-parts board needs one row per vehicle and a small number of columns that answer the real questions. We recommend:
- Vehicle
- Job number
- Defect
- Roadworthiness status
- Parts status
- ETA date
- Ready date estimate
- Owner
- Next review
- Notes
That is enough.
The status list matters more than the layout. We would keep it to no more than seven live statuses:
- Stood down, diagnosis complete
- Awaiting quote
- Awaiting authorisation
- Ordered
- Back order or no ETA
- Parts received, awaiting workshop slot
- In rework for completion
Those statuses reflect what actually happens. Avoid catch-all labels like “pending” or “open”. They hide the problem instead of showing it.
Roadworthiness should be a separate field, not buried in notes. A simple red, amber, green approach works if everyone understands it:
- Red, off the road
- Amber, restricted or managed use only
- Green, serviceable while awaiting non-safety parts
But do not let colour replace words. If DVSA asks later, “amber” is not evidence. The note behind it is.
The board also needs dates that have owners behind them. “ETA Friday” is too loose. Use a date and, if relevant, a time. If the supplier says “Friday PM”, record that. If there is no ETA, say “No ETA, supplier review due 14:00 Thursday”. That is honest and actionable.
Keep the board visible to both workshop and office. A whiteboard can work for a very small operation, but only if someone updates it every time the electronic record changes. Once you have more than a handful of vehicles and mixed responsibility between workshop and transport, one live record is safer. That is exactly why we built one set of records for workshop and transport office. The workshop should not be maintaining one truth while the office keeps another in a spreadsheet.
The other thing that makes people use a board is trust. If technicians know that updating “wrong part supplied” will trigger a real supplier chase, they will bother recording it. If the board is just management wallpaper, it dies.
How to update parts delays without chasing the same answers twice
Most wasted time around parts delays comes from bad update discipline.
One person asks the supplier at 8am. Another asks at 10am because they did not know. Transport asks the workshop at 11am. The customer rings at midday and gets a different answer again. By 2pm somebody says “still waiting on parts” and nobody is any wiser.
The fix is a simple update routine.
First, set the next review point every time the record is touched. If the supplier has promised an update tomorrow, we do not chase again before then unless the case is urgent enough to justify escalation. “No new information” is still information if it is recorded once, properly.
Second, give each vehicle one owner for the next step. The owner is not responsible for the whole repair forever. They are responsible for the next movement. That might be:
- parts desk to confirm ETA
- workshop controller to reserve a bay once parts land
- transport manager to decide on substitute vehicle
- service advisor to obtain customer approval
Third, separate supplier updates from customer or planner updates. The supplier conversation should answer:
- was the part ordered
- what is the ETA
- is the ETA confirmed or estimated
- is there a substitute, supersession, or split delivery
- if delayed, what is the next promised update time
Then the internal update should answer:
- can the vehicle remain stood down
- does the workshop slot need moving
- does the customer or planner need to be told now
- what is the next review point
That avoids forwarding raw supplier noise around the business.
Fourth, only re-open workshop planning when something has changed. If parts are due Tuesday and there is no slot before Wednesday, the board should say that. There is no value in repeatedly asking the foreman whether the vehicle can go back in sooner if nothing has moved.
This is where good job tracking pays for itself. A vehicle that is waiting for parts should not vanish from the workshop list just because no spanners are on it today. We covered that problem in job tracking that stops work going missing.
If you want a practical rule, use this one. Every waiting-for-parts vehicle must have:
- a current status
- a named owner
- a next review date and time
- a latest expected ready date
If any of those four are blank, the job is not under control.
How to tie parts delays back to roadworthiness and O-licence risk
This is where many fleets come unstuck. The waiting-for-parts list is treated as a workshop convenience, when it should also support compliance decisions.
If a vehicle is off the road because of a defect affecting roadworthiness, the stand-down record should show:
- what the defect was
- who made the decision to stand it down
- when that happened
- that it was not released before repair
- when the repair was completed and checked
That matters if there is later a complaint, a roadside stop, or a question from DVSA.
The same record should link to maintenance planning. If a vehicle is due a PMI while already off the road, decide whether the inspection will be brought forward, carried out while waiting, or rescheduled. Do not let it drift because “the vehicle was in the yard anyway”. The maintenance planner should show the reason for any movement and keep the planned interval under control. We go into that in keeping maintenance plans right when vehicles go off the road.
MOT bookings need the same treatment. If a vehicle is waiting on parts close to test date, protect the booking if the repair can still be completed in time. If not, rebook early enough that there is a clear record of active management. Missing a test because nobody joined up the parts delay with the diary is avoidable.
The same applies to tachograph defects. Not every tachograph issue means the vehicle is immediately off the road, but the decision must be based on the actual fault and legal position, not guesswork. Record what the defect is, what advice was taken if specialist input was needed, and what use, if any, is permitted until repair.
For O-licence purposes, the main question is whether we can show proper systems. If DVSA looks at records after a roadside issue or investigation, they will want to see that defects were identified, assessed, controlled, and closed out. If a vehicle sat waiting for parts for nine days, that is not automatically a problem. Nine days with no clear record of decisions is.
And remember the wider pattern. Repeated delays on the same safety-critical items, repeated use of vehicles under vague “temporary” arrangements, or repeated PMI rescheduling because repairs overrun can all start to tell a story about weak maintenance control. That is the kind of story that can end up in front of the Traffic Commissioner.
What good looks like for a five to 100 vehicle operation
Good does not mean complicated.
For a smaller UK fleet or commercial vehicle workshop, a workable model usually looks like this:
One live list Not a whiteboard in the workshop, a spreadsheet in the office, and parts notes in somebody’s inbox. One live list for all vehicles waiting for parts.
A daily review Ten to fifteen minutes is often enough. Run through every stood-down vehicle in status order. Confirm ETA, owner, next review, and whether roadworthiness status is unchanged.
Clear handoffs Diagnosis complete goes to parts. Parts received goes to workshop control. Authorisation issues go to whoever controls spend. Nobody should have to guess who moves the job on.
Compliance dates on the same screen or report Whoever owns the O-licence side needs to see upcoming PMI and MOT dates against off-road vehicles. If those dates sit in a different system and are not checked together, problems creep in.
A stand-down rule If a defect affects roadworthiness, the vehicle is marked off the road immediately and the record is created there and then. Not at the end of shift.
A release rule The vehicle does not come back into service because “the part is on order” or “it seems better now”. It returns only when repaired, checked, and signed back into use.
Evidence kept with the job Supplier ETA notes, authorisation, fitter findings, and completion details should sit with the maintenance record. If somebody asks six months later why the vehicle was down, we should not be piecing it together from memory.
For a five vehicle operation, that may be one person doing most of this, but the discipline is the same. For a 100 vehicle operation, the names change and there may be a dedicated workshop controller, but the structure still holds.
What does not work is pretending this can stay informal once the fleet grows. The moment you have several jobs open, mixed suppliers, and fixed compliance dates, vehicles waiting for parts need active control. Otherwise the yard fills with half-finished decisions.
We built our systems from running Woolpit Truck Repairs, not from drawing process charts in an office. On a real workshop floor, the best method is the one people will keep using on a busy Wednesday when three extra defects turn up before lunch. That means short records, clear ownership, and one place to look.
If you want to know how to track vehicles waiting for parts in the workshop, that is the answer in plain terms. Record the stand-down properly. Keep one live waiting-for-parts board. Update to agreed review points, not constant noise. Tie every delay back to roadworthiness, PMI, MOT, and O-licence decisions. If we can do that consistently, vehicles do not disappear just because the parts have not arrived yet.
What is the most important thing to record when a vehicle is waiting for parts?
The reason it is off the road, the part needed, who made the decision, and whether the defect affects roadworthiness. Without that, the rest becomes guesswork.
Should waiting for parts be a separate status from work in progress?
Yes. If you mix them together, you cannot see whether delays come from workshop capacity or supply. That makes planning and customer updates much harder.
Do I need to keep evidence of supplier delays?
Yes, where it affects bookings, downtime or customer disputes. Keep ETA changes, order dates and supplier messages with the job so the history is clear.
Can a vehicle stay booked for use while parts are on order?
Only if the defect does not affect roadworthiness and the vehicle is safe and legal to use. If it is not roadworthy, it should be clearly stood down.
How often should the waiting-for-parts list be reviewed?
Daily in most workshops. The point is to catch missed ETAs, rebook work quickly and stop vehicles sitting untouched because everyone assumed someone else was dealing with them.
