Vatra
Who is on shift, what they are cleared to do, and what just broke — in one loop.
An operations system for hotels and restaurants: rotas, training that gates shift access, maintenance tickets and a POS.
Who it is forCafé and restaurant groups, hotels and catering: venue managers, shift leads, floor and kitchen staff, and the maintenance service.
Discuss a projectThe task
A venue runs on tools that never talk to each other: the rota lives in a messenger, training in files, a broken fridge in a phone call to someone in particular. A manager cannot quickly answer whether a person is cleared to take a shift, and the maintenance team sees neither the queue nor who is busy with what. High staff turnover makes the whole cycle repeat month after month.
Solution
Three working clients share one interface language: a staff app and a maintenance-service app built on Expo / React Native with an identical token set, plus a manager back office on Next.js. The rules were lifted out of the screens and into code — a permission matrix, an SLA clock that stops while a ticket waits on someone else, shift statuses, course versions; a screen asks what is currently allowed instead of deciding for itself. A tablet POS terminal is designed in full: floor and tables, orders, fiscalised payment, kitchen display, cash drawer and X/Z reports. The service and event map of the platform is written up on the product's own documentation site.
Outcome
The product is in development: the clients run on demo data and the server side is still ahead. They already carry a shift end to end — published rota, confirmed shift, closing checklist with a photo, a maintenance ticket closed by the person who raised it — so reviews are about how the system behaves, not how it looks.
Capabilities
- 01Shift scheduling: publication, swaps and drops, employee confirmation, manual punch corrections
- 02Versioned training courses with quizzes: a passed quiz opens shift access, a failed one blocks it
- 03Maintenance tickets: impact chosen by the requester, priority set by the service, an SLA clock that pauses, an append-only event log and a work report
- 04Shift checklists by phase — opening, service, closing — with photo proof and incident reporting
- 05Documents sent for signature, staff records, invite links and access requests
- 06Role builder: separate permission sets for the back office and the app, plus an audit log recording before and after
Roles
- Employee
- Shift lead
- Venue manager
- Maintenance technician
- Service dispatcher
Industry
hospitality and food serviceScreens
A similar task at your company?
This system was built around one client's process. Describe yours and we will tell you what carries over from what you see here and what has to be built anew.