block book lunch off
planned
C
Ciaran Dixon
Hi folks,
As much as I’d love to chain our mechanics to the workstand for nine straight hours, fuelled only by chain lube fumes and the occasional biscuit, I’m told this is “frowned upon” and “possibly illegal.” Apparently they need lunch. Every day. I know, I was shocked too.
At the moment the booking system thinks our mechanics are tireless robots who don’t need food. Customers get booked in at 12:30 while the mechanic is halfway through a sausage roll.
What I’d love is a way to give each mechanic an hour for lunch, blocked off like the workshop hours, so nobody can book a puncture repair into their sandwich.
Possible fix: split shifts
Instead of setting a mechanic’s shift as 9:00 AM – 6:00 PM, let us split it into two blocks:
9:00 AM – 12:00 PM (fixing bikes)
12:00 PM – 1:00 PM (fixing hunger)
1:00 PM – 6:00 PM (fixing bikes, now with renewed vigour)
This would keep the diary accurate, keep customers happy, and stop the mechanics gnawing on inner tubes by 2pm. It would also mean the dreaded “red line of death” actually tells the truth. Right now it cheerfully insists a mechanic is mid-service when they’re actually mid-panini. With split shifts, their diary would finally match their real day, sandwich and all.
Thanks in advance, from me and a team of very hungry wrenches.
E

Emma - Citrus-Lime
updated the status to
planned
Hi Ciaran,
Sadly, I don't have the power to change your contractual obligations for employee rest breaks, but I do have the power to change Cloud POS, and I have good news on that front.
We're currently building a new piece of functionality for the Workshop called Mechanic Working Hours, where you'll be able to set each employee's weekly schedule into the system. This will then display on the Calendar and will feed into new colour-coded availability indicators, which show you the amount of time remaining for scheduling work. Crucially, for your request, the setup includes the option for a break allowance each day (i.e. lunch breaks), so that their availability is reduced accordingly.
It's going through testing at the moment, but we're targeting the March release.