Autonomous Scheduling
Autonomous scheduling means nobody in your workshop builds the schedule. You describe the shop once; BayWise produces the plan, and keeps producing it as the day changes.
This is the single idea the rest of the product rests on. If you have used scheduling software before, it is almost certainly not the idea you are expecting, and the difference matters more than any individual feature.
The shape of the change
Most workshop software is an assignment tool. It gives you a grid, it warns you when you put two cars in one bay, and it may suggest a technician. A person still decides where each car goes, in what order, and what to move when the day goes wrong. The software is a better whiteboard.
BayWise inverts that. The controller does not place cars. They describe the floor once, and then spend the day on the handful of vehicles that need a human decision.
| Assignment tool | BayWise | |
|---|---|---|
| Who builds the plan | A person, every morning | Nobody — it is produced |
| Who rebuilds it after a problem | The same person, repeatedly | Nobody — it re-produces |
| What the controller does all day | Places and re-places cars | Resolves exceptions |
| What happens when they are away | The shop slows down | The shop runs |
| Quality of the plan depends on | How good that person is today | How well the workshop is described |
That last row is the trade. You are moving the effort from every day forever to once, carefully, at the start — and to keeping that description honest as the shop changes.
What BayWise needs from you
The plan can only be as good as the description it is planning against. Four things carry almost all of the weight.
1. What each bay can do
Each bay has a role (work, inspection, holding, or delivery), a set of capabilities, and a list of equipment. Together these decide what is allowed to land there.
A bay with no alignment equipment is never offered an alignment job, however busy the shop gets. A bay marked inspection-only never receives a repair. This is not a preference that can be outweighed — it is a boundary.
→ The Bay · Set a bay’s role and capabilities
2. What each bay is not for
Every bay also carries a written description, and the most valuable sentence in it is the exclusion. “General service and brakes. Not for bodywork, paint, or high-voltage work.”
The structured capabilities above handle the clear cases. The description is what separates two bays that look identical on paper — and it is read whenever the structured data does not decide the matter on its own.
3. Who is qualified for what
Each technician carries skills, certifications (with levels and expiry dates), a maximum number of jobs at once, and an availability pattern.
Safety-gated work only ever reaches a technician certified for it. High-voltage work is the clearest case: no certification, no assignment, regardless of who is free.
→ The Technician · Assign skills
4. When you are open
Operating hours per day of the week, break times and how breaks are treated, closures for holidays, and whether technicians must clock in to be counted as available.
If you do one thing before going live, spend an hour writing honest bay descriptions with explicit exclusions. Workshops that skip this step get a plan that is technically valid and operationally wrong, and they usually blame the engine before they blame the description.
What BayWise guarantees
Some things are not preferences, tendencies, or suggestions. They are boundaries the plan cannot cross:
- A bay holds one vehicle at a time. Buffer time between vehicles is respected as part of the bay’s occupancy, not squeezed when the day gets busy.
- A technician works one job at a time, up to the maximum number of concurrent jobs you set for them.
- Work fits inside your operating hours. Nothing is planned to start before you open or run past close without carrying over deliberately.
- A bay in maintenance receives nothing. Taking a bay out of service takes it out of the plan.
- Capability and certification are absolute. A job never lands somewhere that cannot do it, or with someone not qualified for it.
- An absent technician is not planned. Marking someone absent removes them and their work is re-placed.
If you have configured your shop such that a car genuinely cannot be placed today, BayWise does not quietly bend one of these rules. It tells you the car could not be scheduled, and why.
→ When a car could not be scheduled
What BayWise will never do on its own
The plan is automatic. The decisions with a customer on the other end are not.
It will not call your customer. When a promise is at risk, the vehicle is raised in the action centre with how much time is left. Whether to call, what to offer, and whether to move the promise is a human judgement with a relationship attached.
It will not decide that work is finished. A stage is complete when the person who did it says so.
It will not hand a vehicle over. A finished vehicle sits in its bay, visible as finished and holding capacity, until somebody hands it over.
It will not cancel work. A job leaves the plan only when a person cancels it and says why.
It will not overrule you. Every placement can be overridden — move a car to a different bay, swap the technician, pause the work. Your override stands.
The division is deliberate. Everything that is a matter of capacity, qualification and time is handled for you, continuously and without fatigue. Everything that is a matter of judgement, cost or a customer relationship stays with the person who owns that relationship.
How the plan changes through the day
The plan is not made once in the morning. It is the current answer to “what should be happening”, and it is revised whenever the floor tells BayWise something new:
- A vehicle is checked in
- Work starts, pauses, resumes or completes
- A technician reports that a job is running longer, and by how much
- A technician is marked absent, or clocks in late
- A bay is taken out of service
- A promise time is changed
- Work fails a quality check and goes back for rework
- A job is cancelled or a vehicle is handed over
After any of these, the rest of the day is re-planned around the new reality. Vehicles that can still make their promise keep their place. Vehicles that cannot are raised for a human.
The board reflects this on its own — it refreshes as the shop changes, and it tells you what moved and why in the change feed.
What this looks like across a full workshop
The value grows with the number of different things happening at once. A shop running one kind of work can be held in one person’s head. A shop running five cannot.
Al Futtaim Auto in Dubai runs five zones under one roof:
- Rapid / express — oil services, tyres, bulbs, basic diagnostics. Short jobs, high turnover, several vehicles through the same bay in a morning.
- Mechanical — engine, transmission, brakes, suspension. Longer occupancy, lift-dependent.
- Electrical and diagnostics — fault-finding, ECU work, sensor faults, ADAS calibration. Skill-sensitive and hard to estimate.
- Body and collision, with paint — multi-day work moving through strip, repair, prep, spray and cure, holding a bay across days.
- Detailing and valet — final preparation before handover, and a standalone service in its own right.
Each of these has a different rhythm, and left alone they compete: the collision job holds a bay for three days while rapid service needs turnover; paint cannot start until prep finishes; detailing has to fit after repair but before handover, on a vehicle that is already late.
Planned together, they stop competing. The multi-day body job holds its bay across days without anyone re-planning it each morning. Rapid jobs pack into the bays that turn over. High-voltage work goes only to the ring-fenced zone and only to certified technicians. Detailing lands after the repair completes, not hopefully alongside it.
When the description is wrong
The commonest cause of a plan you disagree with is not the engine. It is a description that no longer matches the shop.
Symptoms and their usual cause:
| What you see | Usually means |
|---|---|
| Work landing in a bay that cannot really do it | The bay’s capabilities are broader than reality, or its description has no exclusions |
| One technician overloaded, others idle | Skills are recorded on one person and not on colleagues who also hold them |
| Cars regularly unplaceable | Capabilities too narrow, hours too short, or too few technicians marked available |
| Jobs consistently running over | Service durations in the catalogue are optimistic |
| A bay never used | Its role, capabilities or equipment exclude it from work it can actually do |
All five are fixed in configuration, not by overriding the plan every day. An override fixes one car; the description fixes every car after it.