Many California employers in hospitality and retail run Homebase for scheduling and time tracking. When a wage-and-hour audit is on the table — whether triggered by a PAGA notice, a settlement negotiation, or proactive due diligence — the first step is pulling the right data. Homebase gives you a workable foundation, but a few setup choices in how you export it determine whether an audit can actually run.
What a break audit needs from your data
Before exporting anything, it helps to know exactly which fields a California meal and rest break audit requires. The same core dataset applies regardless of which time-tracking system you use:
- Employee identifier and name — a stable ID (not just a name, which can change) plus the display name for the report.
- Work date — the calendar date of the shift, used to apply the correct daily break thresholds.
- Shift start and end times — the actual clock-in and clock-out timestamps for each shift, not rounded totals.
- Meal break punches — the start and end time of each meal break taken during the shift. Without these, the audit cannot determine whether meal periods were timely or long enough.
- Hourly or regular pay rate — needed to calculate premium pay at the correct rate under Ferra v. Loews.
- Rest break attestation — if your Homebase setup captures rest break acknowledgments, include them. Most do not, which matters (see below).
Exporting from Homebase
In Homebase, the timesheet data lives in the time tracking or time-clock section of the dashboard. To get audit-ready data:
- Navigate to the Timesheets area and select the pay period you need to audit. For wage-and-hour exposure analysis, auditors typically want at least the past year; PAGA look-back periods can extend to three years.
- Export a detailed CSV — the export that shows individual punches, not a payroll summary. Summary exports show total hours per employee per period but omit the individual break punches the audit depends on.
- Include all employees for the date range, including terminated employees if the look-back period covers their tenure.
- If Homebase lets you choose between a timesheet report and a time clock report, prefer the time clock export — it is more likely to carry individual punch timestamps.
The exact menu labels may vary across Homebase plan tiers and product updates. If you are unsure which export includes break detail, download a small date range and open it in a spreadsheet to confirm that individual break punches appear as separate rows or columns before pulling the full dataset.
Homebase-specific notes
A few things about how Homebase records time that affect a California audit:
- Meal breaks as clock-out/clock-in. Homebase records meal breaks as an employee clocking out for a break and then clocking back in. Whether that break time is paid or unpaid depends on how your account is configured. Confirm your break type settings before interpreting the data — an unpaid 30-minute break punch is the meal break; a paid short break is typically a rest break, if captured at all.
- Rest breaks are usually not punched. In a standard Homebase setup, employees do not punch in and out for rest breaks. This means the export will have no rest-break records for most shifts. This is normal — it does not mean rest breaks were taken or missed. A defensible audit treats those shifts as record gaps (rest break compliance cannot be confirmed or denied from the data alone) rather than automatic violations.
- Automatic break deductions. If your Homebase account applies an automatic meal break deduction — subtracting a fixed number of minutes from every shift — the export may not show actual punch times for the meal break. Automatic deductions are a common source of California compliance problems because they don't reflect when (or whether) a meal period actually occurred.
Using it in BreakAuditor
Once you have the export, BreakAuditor auto-detects the Homebase CSV format. Column mappings — which field is the employee ID, which timestamps are shift versus break punches — are recognized automatically and then saved per client. For a consultant running repeat audits on the same employer's data, the second and subsequent audits take only minutes to run.
The output flags missed, late, and short meal periods; notes shifts where rest break records are absent; and calculates estimated premium exposure using each employee's pay rate. Every finding is traced back to its source row so the report is defensible if the numbers are challenged.
See what a Homebase break audit looks like
BreakAuditor reads a client's Homebase export and produces a report that flags every non-compliant shift with the estimated premium exposure — traceable to the source data.
Get a sample reportFrequently asked questions
What Homebase export do I need for a break audit?
You need a detailed timesheet CSV that covers the full pay period and includes all employees. Export the punch-level detail — not a totals-only summary — so the audit can see individual shift start and end times plus any meal break punches.
Does Homebase track rest breaks?
Homebase does not typically require employees to punch in and out for rest breaks. Rest break records are usually absent from a standard Homebase export. A defensible audit treats shifts with no rest-break record as a record gap to investigate, not an automatic violation.
What fields does a California break audit require?
Employee identifier and name, work date, shift start and end times, recorded meal break punches (start and end), the employee's regular pay rate, and any rest-break attestation data if your setup captures it.
Can BreakAuditor read Homebase exports automatically?
Yes. BreakAuditor auto-detects Homebase CSV exports and maps the columns without manual configuration. Field mappings are saved per client so repeat audits take only minutes once the initial setup is done.