When a Car Could Not Be Scheduled
Sometimes there is no honest place for a vehicle today. Rather than invent one, BayWise puts it in the action centre under Could not schedule, with a reason.
This is the feature working, not failing. A shop that is genuinely full needs to know at 09:00, while there is still time to do something about it.
Who can do this: Workshop Controllers, Location Managers, Org Admins and Account Owners.
Reading the reason
Open the action centre and choose the Could not schedule lens
Read the reason on each row
| Reason | Means | Usually |
|---|---|---|
| No bay | No bay free today that can do this service | A capacity or capability problem |
| No bay/tech | Neither an eligible bay nor a technician is available | Short-staffed, or a specialism nobody available holds |
| No slot | Resources exist but no workable time remains | A genuinely full day |
| Too long | Not enough of today’s window left to fit it | A late arrival with a long job |
| Stuck | Not yet seen by the scheduler | Usually clears on the next refresh |
| Unplaced | Could not be placed, for another reason | Worth opening |
Read the context
Each row also shows how long the vehicle has been unscheduled and where its promise stands — “promise in 2h · unscheduled 40m”, or “promise passed 15m ago · unscheduled 3h”.
That distinction decides your order of work: a vehicle that arrived ten minutes ago is not the same problem as one that has been unplaced since half past eight.
What to do today
Four options, roughly in order of preference.
Make room by handing over. Check the Unblock lens first. Finished vehicles holding bays are the cheapest capacity in the building.
Place it by hand. If you know a bay will free earlier than the plan assumes, or you are willing to run a job across the changeover, assign it yourself. Your override stands.
→ Move a car to another bay or technician
Re-promise. Ring the customer and agree a realistic time, then update the promise. A vehicle promised for tomorrow morning stops being today’s problem, honestly.
Book it for another day. If the customer can bring it back, the day it can be done is the day to promise.
Do all of this before 10am if you can. The same conversation is easy at 09:15 and expensive at 16:15, and the vehicle has been sitting there either way.
Telling a busy day from a broken description
A vehicle appearing here occasionally, on your busiest days, is a full shop.
The same vehicle type appearing here repeatedly is a configuration signal. Check, in this order:
| Check | Look for |
|---|---|
| Bay capabilities | Is any bay actually described as able to do this work? |
| Bay descriptions | Are exclusions too broad — has a bay been excluded from work it can do? |
| Technician skills | Is the skill recorded on only one person, who was not in? |
| Certifications | Has a certification expired, taking the only qualified person out? |
| Service durations | Is the catalogue duration so long that nothing ever fits? |
| Operating hours | Are your recorded hours shorter than the day you actually work? |
At Müller Werkstatt in Berlin, ADAS calibration jobs kept appearing under No bay/tech on Wednesdays. The cause was neither capacity nor skill: the one technician holding the ADAS qualification worked Monday to Tuesday and Thursday to Friday. Recording the skill against a second technician who was already doing the work fixed it permanently.
Day close
A vehicle still unplaced at day close is asked about: still wanted tomorrow? Keep it, and it goes into tomorrow’s plan. Drop it, and it leaves.
Answering this honestly is what stops a queue of forgotten vehicles accumulating.
Common questions
Why not just squeeze it in? Because the squeeze would be a lie. Every vehicle already placed would have a finish time that could not happen, and you would find out at 5pm rather than at 9am.
“Stuck” — is that a bug? It means the vehicle has not been seen yet, usually because it was checked in a moment ago. It normally clears by itself. If it persists across several refreshes, report it.
Can I ask for it to be tried again? Yes — Re-plan on the row asks for it to be placed again. Worth doing after you have freed capacity.
Everything is here every morning. Your shop is over-committed relative to how it is described. Compare your promise adherence and bay utilisation in analytics — if utilisation is above 90% and promises are missing, you are short of capacity, not of configuration.