Split shifts, constant churn, and nobody at a computer
Hospitality runs on rotating and split shifts, seasonal peaks, and a workforce that turns over faster than the paperwork does.
What hospitality actually needs
Split shifts and rotations
A morning and an evening block on the same day, held as one shift rather than as two half attendances.
Onboarding at speed
Invite-based joining with documents read from photographs, because you will do it again next week.
Night shifts across midnight
A shift starting at 22:00 stays one working day, which is what makes the overtime figure defensible.
Everything on a phone
Punching, leave and payslips for staff who have no desk and no company email.
Several properties, one view
Headcount and cost per property, without asking each property for a sheet.
Statutory across categories
PF, ESI and professional tax resolved per workplace, for permanent and contract staff together.
The split shift is the defining problem
A restaurant employee working 11:00 to 15:00 and again 19:00 to 23:00 has worked one day. A system that records two attendances produces two half days, breaks the overtime calculation, and generates an argument every month.
Split shifts have to be a first-class shift pattern rather than something modelled around. So do rotating weekly offs, which in hospitality rarely fall on the same day twice.
Churn is the operating condition
Hospitality turnover is high and seasonal. Onboarding that takes an afternoon of typing per person does not survive a season; onboarding by invite, with documents read rather than transcribed, does.
Exit needs to be equally routine. A property manager will not run a careful clearance process for the fifth leaver this month unless the system runs it for them.
Be deliberate about tips and service charge
How service charge is distributed, whether it is treated as wages, and how it appears on a payslip are decisions with statutory consequences — and they are decisions, not defaults. Whatever your arrangement, it should be configured once and applied consistently rather than handled property by property.
A day that has two halves
Split and rotating shifts
Two blocks in one day held as a single shift, with rotating weekly offs.
Punch from a phone
No device per outlet. Bounded by the property, working on poor wifi.
Fast joiners and leavers
Invite onboarding and checklist exits, because both happen constantly.
One payroll, several properties
A single run, with cost and headcount visible per property.
Hotels, restaurants and hospitality FAQs
How are split shifts handled?
As one shift with two blocks, so the day counts once and overtime computes correctly against the total. Recording them as two separate attendances is what causes the monthly argument.
Can staff punch without a company device?
Yes, from their own phone, bounded by the property location. Any existing biometric at a staff entrance can also push punches in.
How is service charge handled?
As a configured pay component with the treatment you decide. Because its statutory treatment follows from that decision, it is worth setting deliberately rather than leaving to each property.
We have seasonal staff. Does pricing follow headcount?
Yes — pricing is per employee and adjusts monthly, which is the point for a business whose headcount doubles in season.
Split shifts and high turnover are our normal.
Split shifts are handled as scheduled rather than as two attendance events, and onboarding is built for volume — self-service before day one rather than a form on arrival.
Tips and service charge — are those payroll?
How they are treated affects the wage base for statutory purposes, so they need a decision recorded rather than being handled informally each month.
Can we start with one site and expand?
Yes, and most do. Start where the pain is, prove a month, then roll out. A big-bang rollout across every location is how a project acquires a reputation before it has results.
What does it take from our team each month?
After setup, the monthly job becomes reviewing what the system drafted rather than assembling it. The teams who see the biggest change are the ones who were retyping attendance into a spreadsheet.
See it on your own data
Fourteen days, no card, no consultant. Import your spreadsheet and watch it compute.