Skip to main content
FieldTime runs a full compliance audit every time a timesheet is saved or submitted for the week. The engine evaluates California Labor Code §510 overtime rules, California Labor Code §512 meal break requirements, and DIR prevailing wage obligations in a single pass, then surfaces any issues as compliance findings directly on the timesheet — before the timesheet ever reaches a supervisor or payroll. This lets employees and administrators resolve problems while the time data is still fresh, rather than after payroll has already run.

Finding categories

FieldTime groups every compliance finding into one of four categories so you can filter and prioritize issues quickly.

OVERTIME

Flags California §510 daily overtime (over 8 hours), daily double-time (over 12 hours), weekly overtime (over 40 punched hours), and 7th-consecutive-day rules. Shifts that span midnight are automatically split at 00:00 Pacific so hours land on the correct calendar day.

MEAL_BREAK

Tracks first and second meal break obligations under California Labor Code §512. Findings are generated when a required 30-minute break was missed, taken too briefly (under 30 minutes), or when a waiver is on file. See Meal Breaks for the full rule set.

PREVAILING_WAGE

Generated for every time entry on a prevailing wage project. Prompts the payroll team to verify the employee’s hourly rate against the applicable DIR determination and flags Saturday, Sunday, and holiday premium requirements — as well as night shift differentials and zone pay reminders. See Prevailing Wage for details.

DCAA

Informational warnings generated when a time entry is recorded more than three calendar days after the date of work. DCAA timekeeping standards require same-day or next-day recording of time charges. These findings do not block submission but should be addressed before payroll runs.

Severity levels

Each finding carries one of three severity levels that determine whether the timesheet can be submitted.
SeverityColorMeaningBlocks submission?
ERRORRedA rule violation that must be resolved — for example, a missed California meal break that triggers mandatory premium pay, or daily double-time that must be reclassified before payroll runs.Yes
WARNINGAmberA condition that warrants review but does not block submission — for example, a DCAA late-entry notice or an informational project-switch note.No
NOTICEBlueAn informational flag generated on prevailing wage entries — for example, a DIR rate appendix reminder or a night-shift differential calculation. No action is required unless the underlying rate is incorrect.No

How findings appear on your timesheet

When you open a timesheet week, FieldTime automatically runs the compliance audit in the background. Any open findings appear in the Compliance panel beneath the time entry grid.
1

Review the finding

Each finding shows the rule code, a plain-language description of the violation, and a suggested fix. Read the description carefully — it includes the specific date, hours worked, and the applicable rule that was triggered.
2

Correct or acknowledge the issue

If you can fix the underlying time entry (for example, add a meal break that was omitted), edit the entry and re-run the audit. FieldTime will clear the finding automatically if the correction resolves the violation.
3

Resolve the finding

If the finding reflects an approved exception or a situation you have already handled outside FieldTime, select Accept or Dismiss to mark it resolved. Resolved findings are kept in the audit trail but no longer block submission.
4

Submit your timesheet

Timesheets with one or more open ERROR-level findings cannot be submitted. Resolve all errors before clicking Submit. WARNING and NOTICE findings do not block submission.
Every finding resolution — whether accepted, dismissed, or cleared by a corrected entry — is permanently recorded in the audit log with the resolver’s identity, timestamp, and action taken. This audit trail satisfies SOX 404, DCAA, and DIR certified payroll requirements.

Re-running the audit

The audit runs automatically when you save a time entry. If you edit an entry after the audit has already run, FieldTime detects the change and marks the timesheet as needing a fresh audit. You can also trigger a manual audit at any time by clicking Run Audit in the Compliance panel. The engine clears all prior open findings and regenerates a current snapshot — previously-resolved findings are preserved so the audit trail remains intact.

Meal Breaks

California §512 rules, first and second meal break thresholds, premium pay, and how to record a mutual-consent waiver.

Prevailing Wage

DIR prevailing wage determinations, labor classifications, Saturday/Sunday/holiday premiums, and project setup.

Annual policy attestation

FieldTime requires all employees to complete an annual policy attestation before they can submit timesheets for the new policy year. The attestation presents the exact certification text — including the federal false-statements notice under 18 U.S.C. § 1001 — and records the employee’s IP address, browser, and the policy version in an immutable attestation record. If your attestation has lapsed, FieldTime will prompt you to re-attest when you next open a timesheet. Contact your administrator if you need a copy of the attestation text you signed.