# Time tracking for restaurants, hotels and catering > Time tracking for hospitality. Split shifts, late nights past midnight, on-call staff and students, fast rosters, late-hour allowances and payroll exports. URL: https://timetracking.tech/for/hospitality Language: en Last updated: 2026-10-26 Hospitality hours do not fit a nine-to-five timesheet. A cook works lunch, goes home and comes back for dinner. The bar closes at one. An on-call waiter gets a call at four to come in at six. TimeTracking records those days as they really are. The roster can change fast, and payroll still gets the right hours and late-hour allowances. Start free for up to 5 users. ## How hospitality teams use TimeTracking 1. **Roster fast**: Build the week from shift templates and check who is available. Fill gaps with open shifts that on-call staff can pick up. 2. **Clock in at the staff entrance**: Staff clock in and out on a kiosk tablet with a personal PIN, or use the timer in the app. 3. **Split shifts and late nights stay correct**: Lunch and dinner are two blocks on one day. A shift that ends after midnight stays one shift with the right totals. 4. **Approve and export**: The manager approves the week. Hours, late-hour allowances and leave go to payroll in one export. ## Split shifts without workarounds In many kitchens and restaurants the working day has a gap. 11:00 to 14:30 for lunch, then 17:00 until closing. In TimeTracking that is just two blocks on the same day, each with its own start and end. The unpaid time in between does not count. The day total is right, and nobody has to subtract by hand. Breaks within a block are recorded as separate entries. The rule engine warns the planner when a roster breaks the working-time and rest rules you set. - Several blocks per day, each with start and end - Unpaid gap between blocks not counted - Breaks recorded clearly - Working-time warnings in the roster ## Late nights past midnight A bar shift from 18:00 to 01:30 is one shift. It is not a Friday that ends at midnight plus a Saturday that starts at 00:00. TimeTracking keeps it together with the right totals. The rule engine splits the hours into the allowance bands you set, for example after 22:00, or on Sundays and public holidays. Public holidays for the Netherlands, Germany and Belgium are built in. In hotels, a late closing followed by an early breakfast shift is a classic rest-time problem. Planners see a warning when a roster leaves too little rest between two shifts. They see it before the roster goes out. ## On-call staff and students Hospitality runs on on-call staff, students and seasonal workers who come and go. Invite new people by SMS. They log in with a one-time code. So a student is ready for a Saturday shift without a company email address. The apps come in 20 languages, and each person picks their own. Availability shows who can work when. That saves a round of messages before every roster. Busy evening, need an extra pair of hands? The manager publishes an open shift. On-call staff see it in the app and respond. The manager decides who gets it. Swaps only count after the manager approves them. - Invite by SMS, log in with a one-time code - Availability visible while planning - Open shifts and swaps approved by the manager - Pay only for active users ## A kiosk at the staff entrance Phones do not belong in the kitchen. Put a tablet kiosk at the staff entrance or by the lockers. Everyone clocks in and out with a personal 6-digit PIN, in their own language. You can tie each kiosk to one location. That helps groups with several restaurants, or a hotel with a separate catering kitchen. The kiosk takes no photos and uses no face recognition. After 5 wrong PINs it locks for 15 minutes. That stops people clocking in for a colleague. ## Catering and events at changing locations Catering teams work at a different venue every weekend. Set up each event location as a site. Hours are then recorded per event. Planned versus worked hours show which jobs ran over. Travel time and mileage to the venue are recorded separately. You pay them as your agreements say. For groups with several outlets, reports show hours per location, person and period. Head office exports all locations in one go. ## Focused on hours, open to your stack TimeTracking is not a POS, a booking system or a tip tool. It handles rosters, hours, leave and approvals. It sends approved periods to payroll. Live today: an SD Worx-format export, CSV, XLSX and JSON exports in your own layout, and the REST API. Connectors for Loket, Nmbrs and AFAS are coming soon. Free for up to 5 users, then €1 per user per month on Core. No add-ons, no seat minimum. When the season ends, deactivated staff stop counting. Start free today. ## Frequently asked questions ### Can TimeTracking handle split shifts? Yes. A split shift is two blocks on the same day, each with its own start and end. The gap in between is not counted as working time. ### What happens to shifts that end after midnight? They stay one shift with the right totals. Late hours are split into the allowance bands you set. ### Can on-call staff pick up extra shifts? Yes. The manager publishes an open shift. Available staff see it in the app and respond. The manager decides who gets it. ### Do students need a work email address? No. They can be invited by SMS and log in with a one-time code. ### Does TimeTracking connect to our POS or handle tips? No. TimeTracking records working time and exports approved hours. It does not connect to point-of-sale systems or distribute tips. ### What does it cost? Free for up to 5 users, then €1 per user per month on Core, including rosters, the kiosk, approvals and payroll exports. You only pay for active users.