Competence-aware allocation
Work is assigned according to what each person is qualified to do, not to who happens to look free.
Planner
Planner proposes a repair date from the work's complexity, the specialisation it needs and the capacity you actually have, then sequences the tasks so a waiting customer's car is not shunted between bays and technicians.
A concept repair-day sequence for sample order 4471: four tasks run back to back on Bay 2, with the specialist step called out before the planned collection. Positions show the order of work, not measured capacity or performance.
The problem
A wall chart filled in booking order leaves a vehicle waiting for a specialist, moving to another bay and waiting again. Planner reads the dependencies between tasks so the sequence serves the vehicle and the customer waiting for it.
Work is assigned according to what each person is qualified to do, not to who happens to look free.
Employees know what needs doing on an order and when, from the same live sequence.
Advice and assistance are part of the workflow, while the plan adapts instead of being rebuilt every morning.
How the plan is built
Select an input to see what Planner weighs before it proposes the date and the order of work.
An hour of diagnostics and an hour of bodywork are not interchangeable, and the plan reflects that.
The ideal repair date is proposed from what the work involves and the capacity the workshop genuinely has that week.
Responsibilities, working time, absences and unavailable periods feed the plan.
Competences are configured per technician, so certified work is allocated automatically rather than from memory.
With a customer waiting, activities follow one another without interruption instead of leaving the car between teams.
The sequence limits movement from bay to bay and technician to technician.
A late part, an absent technician or an overrun changes the current plan instead of leaving somebody to redraw the chart.
Communication is real time, so the advisor's promise and the workshop plan do not quietly diverge.
Capabilities
All twelve capabilities named by the current Planner product, grouped by the decision they support.
The ideal repair date from complexity, specialisation and capacity.
Every connection between an order's requirements handled.
Waiting-customer activities follow on without gaps.
Resources assigned according to what each person is qualified for.
Responsibilities and working time set per person and respected.
Planned holidays and unavailable periods excluded from the plan.
Planned repairs adapt as the situation develops.
Any change takes effect immediately for everyone.
Open and closed work visible to everyone looking at the plan.
Fewer moves from bay to bay and technician to technician.
Work planned across the company with permission-aware visibility.
Sales preparation competes honestly for the same bays.
By role
Stops rebuilding the day at eight in the morning and sees the consequence of every override immediately.
Promises a collection time the plan supports and hears about a delay before the customer does.
Knows what is next and why it is theirs without waiting for manual allocation.
Sees where capacity goes, including preparation work generated by sales.
Platform & data connections
The order and its items, including the dependencies between them.
Whether the parts a task needs will be there on the proposed day.
Working time, absences and the competences each technician holds.
Preparation work and workshop capacity on the same operating view.
System relationship
The sequence needs the order and its dependencies, real working time and competence, the parts a task needs and the other work competing for the same resources.
Outcome & proof
A mechanical consequence of the scheduling logic, described rather than quantified.
No throughput or utilisation gain is published without evidence.
Broken source copy about benefits and pensions was not carried over.
Slot reserved. Throughput per bay before and after would be the natural proof.
Questions foremen ask
Secondary product demonstration
Tasks follow dependencies, capacity and competence so the vehicle does not bounce between bays.
Review PlannerYour real bookings, your real technicians. We will plan it and show how many times each car would have moved.
See the plannerOne busy day with promised times and the work behind each promise.
Technicians, competences, working hours and known absences.
Bays, parts and task dependencies that make the day possible.