Move a Car to Another Bay or Technician
You can always overrule the plan. Three overrides cover almost every case.
Who can do this: Workshop Controllers, Location Managers, Org Admins and Account Owners. Moving a vehicle between bays and changing the technician are separate permissions.
The three moves
| Move | Use when |
|---|---|
| Reassign | Both the bay and the technician should change |
| Swap tech | The bay is right, the person is not |
| Override bay | The person is right, the bay is not |
Making the move
Open the vehicle
From its bay card, or from a row in the action centre.
Choose the move
Reassign, Swap tech or Override bay.
Choose the destination
Only genuinely eligible destinations are offered — a bay that can do the work, a technician qualified for it. A bay the vehicle is already in is not offered.
Confirm
The board updates and everything behind the change is re-planned around it.
Your override is a decision, not a suggestion. BayWise will not quietly move the vehicle back on the next refresh.
When you should override
A customer has asked for a specific technician. A relationship BayWise does not know about.
You know something the plan does not. A bay that will free earlier than expected, a technician who is better with this particular make, a vehicle that must not go outside.
Something physical has changed. A vehicle that will not start and cannot be moved to the bay it was given.
You are recovering a bad morning. Concentrating the recoverable work on your fastest people is a judgement call, and it is yours.
When you should not
If you make the same override every day, stop overriding and fix the description. An override fixes one car; a bay’s capabilities and exclusions fix every car after it.
Three patterns worth catching:
| You keep doing this | Change this instead |
|---|---|
| Moving a job type out of a particular bay | That bay’s capabilities, or the exclusion in its description |
| Moving work off one technician onto another | Record the skill on the colleagues who also hold it |
| Moving vehicles into a bay the plan never picks | That bay’s role, capabilities or equipment — something is excluding it |
Assigning a vehicle that has no bay
A vehicle in the Could not schedule lens has no bay at all. The row offers Assign — choose the bay and technician yourself.
This is the manual placement of a vehicle the day could not fit, and it is entirely legitimate when you know the day better than the description does.
→ When a car could not be scheduled
What moving does not do
It does not move work in progress off a lift. Reassigning a running job changes who and where it continues; the physical vehicle still has to move, and that is your call, not the software’s.
It does not change the promise. If moving a vehicle makes it late, the promise still says what it said. Update the promise if you have agreed a new one with the customer.
It does not lose the record. Time worked, stages completed and delays reported stay with the job.
Common questions
A bay I want is not in the list. It is not eligible — wrong capabilities for this work, no required equipment, in maintenance, or already occupied for that window. Check the bay’s setup.
A technician I want is not offered. They lack the skill or a required certification, are not available or clocked in, or are already at their maximum concurrent jobs.
Can I move a vehicle to a bay in another zone? Yes. Zones organise the floor; they do not restrict where work can go. Capabilities do.
I moved it and the rest of the day rearranged. That is expected — the vehicles behind it were planned around the old arrangement. The change feed lists what moved.
Can a technician move their own job? No. Moving work is a controller action.