Skip to content
Prompt CRM

Planning board and diary

Workshop planning board software that knows each technician's shift, skills and break

Prompt CRM includes a workshop planning board and a workshop diary for the service department of a car dealer. The diary books each car against the hours your technicians can sell that day. On the day, the workshop controller drags each job line onto a technician's row, or asks for a proposed plan built from skills, shifts, breaks and promise times. A live screen on the workshop TV shows every car with its stage and marks the promise times at risk. It is built for the workshop controller who plans the day and the service manager who answers for the promise times.

The demo is Autohaus Musterstadt, a fictional dealer with today's job lines on the board. Sign in as Marco Klein, the workshop controller, for the planning board, or as Anna Berger, the service advisor, for the diary.

01The planning board

Technicians in rows, the day in 15-minute steps

Each technician on today's roster has a row with their shift, break and skills. Job lines sit on the rows as blocks, from the planned start to the end of their sold time. On the left, approved lines without a technician wait in order of the customer's promise time. Each shows its hours, the skill it needs, and whether the customer is waiting on site or a part is missing.

A bright workshop with two cars raised on lifts. One technician works under a car, two others at a tool trolley and a workbench.
  • Drag a line onto a technician's row. Where you drop it sets the start, rounded to 15 minutes, and the sold time sets the end.
  • Every waiting line also has a short form with technician, bay or lift and start time, for the keyboard or a touch screen.
  • The board refuses a line for a technician who lacks a skill it needs, such as high-voltage work.
  • Work that needs a lift, an alignment rig or an ADAS calibration rig reserves a free one for the same time, and is refused when none is free. Bays, lifts and equipment have their own rows.
  • Two lines that overlap on one technician split the row into lanes, so a double booking shows instead of hiding behind another block.
  • A block shows when the technician is clocked on, a part is missing or the customer is waiting. The board updates without a reload when a technician clocks on or someone else allocates a line.
  • On the right are the orders waiting on the customer, on parts or carried over, and sublet work out at a partner with its expected return. At the end of the day, one button carries an unfinished order over to tomorrow.

02Allocation proposal

A proposed plan for every line still to allocate

Press Propose plan and Prompt CRM suggests a technician and a start time for each waiting line. Nothing is saved until the workshop controller accepts. The controller accepts, changes or rejects each proposal, or accepts them all at once, and every accept goes through the same checks as a manual allocation.

Who can do the job.
A technician who holds every skill it needs, is rostered today, is not absent and is free for the whole job. If the job needs a lift or a rig, one must be free for the same time.
Which job goes first.
Cars whose customers are waiting on site, then the earliest promise time, then the longest job.
Who gets it.
The technician who would finish first. Hours already planned that day, a missing skill that fits the work, and safety work for an apprentice count against a technician, so the work spreads over the team.
When it starts.
Not before now, inside the shift, and not across the break unless the job fits nowhere else.
What the controller sees.
The technician, start and end, whether the skills match, the hours already planned, and a warning when the job would finish after the promise time. A line without a proposal shows why, for example that no free time is left today.

03Roster, breaks and idle time

One roster for the diary, the board and the technician app

Each technician has a weekly roster with shift times and a break. The diary's capacity, the rows on the planning board, the allocation proposal and the technician app's automatic break all read it.

  • The break shows as a hatched band on the technician's row. The workshop controller moves it or changes its length, from 0 to 120 minutes, on the board, and the change applies to that weekday from then on. A change for today cannot cover minutes already clocked.
  • A clocking that runs into the break ends when the break starts and resumes on the same job when it ends, so break time is never booked to a job.
  • When a technician clocks on, a gap of five minutes or more since the start of the shift or their last clock-off, not counting the break, is recorded as idle time. The people report shows idle hours and idle share for each technician, and the performance report shows them for the workshop.
  • An absent technician's row is greyed out and takes no jobs. The allocation proposal shows the hours each technician already has planned, so you see who is loaded before you accept.

04Live screen

A live screen for the workshop TV

The live screen is a dark view for a TV on the workshop wall. It lists every car from check-in to collection in order of promise time, with plate, make and model, stage, technician, promise time and whether the customer is waiting on site. A car whose promise time has passed, or whose last planned job ends less than 30 minutes before it, is marked Promise at risk. The screen updates when something changes and refreshes every minute to move the clock on.

Default tasks around the planning board
A car is checked inWorkshop controller allocates its job lines15 min
A job is clocked off more than 25 % over its sold timeWorkshop controller asks the technician for a reason15 min
A promise time is at riskService advisor agrees a new time with the customer15 min
The final check is dueWorkshop controller runs the final check20 min

05Workshop diary

Workshop diary software that books against the hours you can sell

The diary shows the next seven days, each with the hours still free and the share already booked. A day's sellable hours are each technician's rostered hours, minus breaks and absences, times a productivity factor of 85 % by default. Bookings at the service desk, on the phone and on the online booking page all take their hours from the same pool.

  • For the chosen day, the diary lists each drop-off with its time, plate, customer, booked work and stage, and how many of the day's sellable hours are booked.
  • For a phone booking, the agent finds a known customer by name or plate, or enters a new one with the vehicle, then picks services with their hours or notes the concern in the customer's words.
  • While the customer is on the phone, the form suggests additions for that car: open recalls, due dates, the seasonal tyre change and work postponed at the last visit.
  • Drop-off times come in reception slots, each with a limit on how many cars can arrive.
  • A booking is refused when the day has too few hours left, the drop-off slot is full, or the lift or rig the work needs has no hours left that day.
  • Each booking records whether the customer waits on site or needs a courtesy car, pick-up and delivery or a transport voucher.
  • Customers who want an earlier day can join a waiting list. When a booking is cancelled or moved, the freed slot goes to them as an e-mail offer, and the first to accept takes it.

Further reading

Guides for planning the workshop day

Work a full day at Autohaus Musterstadt

The demo workshop is a fictional dealer with today's orders in every state. One waits for a part, one has waited 47 minutes for the customer, and one is ready to collect. Sign in as the advisor, the technician or the back office and work them.

Prompt CRM is new, and we are looking for pilot workshops.

Analytics

May we measure visits to this site with Google Analytics? It loads only if you accept.

Details in the privacy policy