Exact answer: request the Toast labor, timecard, or payroll-prep export that preserves row-level shift and break timing. Do not rely on a restaurant labor summary alone.

Toast support content and report access can vary by module, location setup, payroll configuration, and account permissions. Treat this as an audit-scoping guide: ask the client for the most detailed time and labor export available, then verify the columns before promising a report.

Fields to request

  • Employee identifier and name: stable enough to group shifts and corrections.
  • Location, job, and role: important for restaurant work where employees move between roles.
  • Work date, shift start, and shift end: required for meal-period timing.
  • Meal or break records: start, end, duration, and break type where available.
  • Rate, pay code, or wage field: needed for premium estimate and assumptions.
  • Source row or report ID: needed to trace findings back to the export.

Toast-specific checks

  • Restaurants often have role changes: preserve role and job columns so the client can see whether patterns cluster by job type.
  • POS labor reports are not always punch reports: confirm the file shows clock times and breaks, not only labor cost or sales/labor ratios.
  • Break rules depend on configuration: document whether breaks are punched, automatically deducted, attested, or missing from the export.

Using Toast data in BreakAuditor

BreakAuditor maps the Toast export, flags source-backed meal timing issues, separates record gaps, and returns the sample-style packet: branded PDF, correction rows, and assumptions log.

For restaurant clients, pair this page with the restaurant break audit checklist before requesting the file.