Guide: Rotaking
How Do Core Concepts Map to Tenzo?
Key: ✅ Supported 🚸 Work in Progress ❌ Not supported
 |
|
|---|---|
| Location | ✅ Locations |
| Shift (actual) | ✅ Worked shifts (approved or not) |
| Shift (planned) | ✅ Published shifts |
| Hours | ✅ Shift hours |
| Employee | ✅ Employees |
| Role | ✅ Job titles |
| House Part | ✅ Departments |
| Leave (holiday, sickness) | ✅ Sickness & other paid leave — loaded as paid time off, kept separate from worked labour |
| Pension | ✅ Employer pension contribution |
| Salaried workers | ✅ Cost provided per shift by Rotaking |
| Shift cost | ✅ Provided per shift by Rotaking |
| Holiday accrual | ✅ Accrued on each worked shift (salaried absorbed into salary) |
| Breaks | ✅ Paid and unpaid break minutes |
| Employer taxes (NI) | ✅ Provided per shift by Rotaking |
| Overtime | ❌ Not supported |
Data Ingestion
| Real-time optionally available? | ❌ |
| Default polling frequency | Every 8 hours |
| Data retrieved on each poll | This week Forward two weeks Back two weeks |
| Historical data | All data since you started using the system |
How Do I Connect This Data to Tenzo?
Rotaking can be connected directly inside the Tenzo app using your Rotaking API username and password.
Paid leave such as sickness and other paid time off is loaded as paid time off in Tenzo, kept separate from your worked labour hours and cost.
If you have an Enterprise Account, you can talk to your Customer Success Manager, who will connect this for you.
How Do I Compare Rotaking Data to Data in Tenzo?
Compare against the Financial overview in Rotaking (the same figures shown on your Rotaking Financial page). Total worked hours should match closely.
Labour cost is provided per shift by Rotaking (wage, pension and employer National Insurance) and should match closely. Paid leave such as sickness is loaded as paid time off rather than worked labour, so it sits outside each department's worked labour cost. Paid holiday accrual for salaried staff is absorbed into their salary in Tenzo rather than added on top, so Tenzo's worked total can sit slightly below Rotaking's raw figure.
Note that shifts crossing midnight are attributed to the day they start in Tenzo, which can shift a small amount of time between days versus Rotaking's own view.
In Tenzo, the Labour by House Part view breaks worked hours and cost down by department (for example FOH and Kitchen), so you can compare each department against the equivalent split in Rotaking:
You can also compare actual labour against your forecast. Worked shifts in Rotaking load as Tenzo's actual labour and published shifts load as the forecast, so you can track worked labour against the planned schedule:
