A shift with nobody checked in after the grace period is flagged, and the people who could cover it are ranked, so the manager works down a shortlist instead of a group chat.
Shift swaps
Staff request a swap from their phone; the manager approves it with the compliance check already done.
Owners and managers with venue-scoped access, custom role titles, and a trail of who changed what.
How the parts fit together
These are not twelve products in one login. They are one loop that a shift goes through, from the moment it is planned to the moment it is paid:
Plan. The roster is built and published. Staff see their shifts on their phones.
Show up. Staff scan the venue’s code to check in. If somebody does not, the no-show is caught and a ranked shortlist of cover is ready for the manager.
Work. The dashboard shows who is on the floor. Swaps and last-minute changes are handled with the rules already checked.
Close. Staff check out and record their break. Anything unusual is flagged for a manager, in words, the same day.
Pay. The pay run is built from those verified hours, and the same hours feed the analytics.
Because every step reads the same records, there is nothing to reconcile between them. The rota, the attendance log and payroll cannot drift apart, because they are not three copies of the truth.
Built for the way hospitality works
Split shifts, overnight shifts that cross midnight, staff who work at more than one venue, a new starter added at the door mid-service, a phone with no signal in the cellar: these are the normal case in hospitality, and the product treats them that way. Every venue records hours in its own local time, so a Dubai hotel and a London restaurant in the same group each pay and report on their own day.
Access and accountability
Owners see and manage the whole organisation, including payroll and billing. Managers see the venues they are assigned to and nothing else; payroll and billing stay with the owner. Every organisation’s data is kept apart from every other’s. Changes to people, roles, venues and settings are written to an activity log that names what changed, without copying sensitive values such as pay rates into it.
Plans
One venue is free, permanently, for a small team. Larger teams and more venues are priced per venue, published on the pricing page, with no sales call.
Where to go next
If you run more than one kind of operation, the use cases show how hotels, restaurants, event teams and staffing operations each use the same features differently.
