Guide: Stint

How Do Core Concepts Map to Tenzo?

Key: ✅ Supported   🚸 Work in Progress   ❌ Not Supported

Locations	✅ Site
Shift (actual)	✅ Paid shift (clocked-in / out)
Shift (planned)	✅ Scheduled shifts (Labor Planned tab)
Hours	✅ Worked Duration / Calculated Paid Hours
Salaried workers (Pay Rate /year)	✅ Salary pay type
Employee	✅ Profile / employee record
Role	✅ Position
House Part	✅ Schedule Group (e.g. "Front of House")
Overheads	✅ Overhead cost per shift, where included in the sheet
Holiday	❌ Not Supported
Breaks	❌ Not Supported
Overtime	✅ Overtime minutes and cost, where included in the sheet
Exception costs	❌ Not Supported
Borrowed / loaned employees	❌ Not Supported

Data Ingestion

How Do I Compare Stint Data to Data in Tenzo?

Tenzo's labour cost for your venue should align closely with the headline "Actual labour cost" you see in Stint Reporting. To verify:

1. Log into reporting.stint.co.
2. On the Reporting dashboard (the default landing page), use the granularity selector in the top-right to pick the period you want to compare. Options are Week, Month, Quarter, Year, and Multiple Weeks.
3. Use the period chip (e.g. "Week of 11 May 2026") to choose the specific window. The dashboard updates live.
4. If you have multiple venues, switch to the site you want by clicking the sites selector (look for the venue name above the metric cards).
5. The headline cards show:
   • Actual labour cost (WTD) — total labour cost for the period
   • Actual hours (WTD) — total worked hours for the period
   • Actual labour % (WTD) — labour cost as a % of sales
6. Compare these to Tenzo's labour view for the same venue and date range. The numbers should match within ~1% if the Overheads setting in Tenzo is enabled and the Stint Reporting view is showing Week-to-Date (not Run-Rate).

If you only see the dashboard "Welcome" view rather than the cards, you may need to switch to Week-to-Date mode (the tab next to "Run-Rate" near the top of the dashboard) — Run-Rate is a forward projection and will not match Tenzo's actuals view.

Exceptions

• No separate break or holiday breakdowns. Stint's sheet does not carry breaks or holiday as distinct fields. Worked hours include all paid time; if a shift records 8.5 paid hours, Tenzo treats it as 8.5 hours of worked labour regardless of whether some of that was paid break time. Overtime minutes and cost come through when they are included in the sheet.
• Pay rate changes mid-period. Stint applies the rate that was in effect on the day of each shift. Tenzo's per-employee aggregates take the latest non-zero rate seen across the loaded window. If an employee's pay rate changed during the period being compared, the per-employee cost figures may differ slightly between Stint Reporting and Tenzo — the totals at the venue level should still match.
• Non-service shifts. Stint distinguishes between service and non-service shifts; Tenzo includes both in the "Actual labour cost (incl. non-service)" rollup. If you're cross-referencing with Stint's "Service-only" view, the numbers will be lower by the non-service component.
• Newly added employees without a contracted rate. Stint may emit shift rows for employees who have been created but not yet had a pay rate assigned. These rows carry £0 cost in both Stint and Tenzo. If your reports look light, check Stint's employee admin for any rows missing a Pay Rate field.
• The "Lock Week" requirement does not apply. Unlike some other labour partners, Stint pushes shift data continuously through the period — you don't need to lock the week before Tenzo will see it. Data refreshes automatically each night.