Understanding Timesheet Statuses
Every timesheet moves through a defined lifecycle from the moment it is created to final approval. The current status is displayed as a colored badge at the top of the Timesheet page.Draft
The timesheet exists but has not been submitted. You can freely add, edit, and delete entries. This is the starting state for every new week.
Pending PM Review
You submitted the timesheet and it is waiting for your Project Manager to review and approve it.
PM Approved
Your Project Manager approved the timesheet. It now moves to supervisor review automatically.
Pending Supervisor Review
The timesheet has passed PM review and is awaiting final approval from a supervisor.
Approved
All reviewers have approved the timesheet. It is locked and ready for payroll processing.
Rejected
A reviewer rejected the timesheet. You’ll see a banner with comments. Make corrections and resubmit.
Revision Requested
A reviewer wants specific changes before approving. You’ll see their comments in the Approval History. Make the requested edits and resubmit.
Once your timesheet reaches Approved status, it is locked. Contact Payroll if you need a correction after that point.
Reading the Weekly Time Grid
The main timesheet view is a grid with days of the week (Mon–Sun) across the top and time categories down the left side.- Time Worked row
- Leave rows
- Total row
Each cell in the Time Worked row shows punch-clock entries (or manual entries for exempt employees) for that day. Click any entry chip to open the Time Entry Detail panel below the grid, where you can view clock times, meal breaks, classification, notes, and — if the timesheet is still in Draft — edit the entry.
Reviewing Your Timesheet
Before submitting, scroll through each day’s entries and check for:- Missing entries — any day you worked that has a zero total
- Unassigned punches — entries without a project (shown in the entry detail with a red badge)
- Short meal breaks — breaks under 30 minutes that do not satisfy California §512
- Compliance warnings — flagged in the Compliance Audit panel (see below)
Running the Compliance Audit
Before the Submit button appears, you must run FieldTime’s California Labor Code compliance audit. Scroll down to the Compliance Panel and click Run Audit. FieldTime checks every entry for:- First and second meal break timing (CA Labor Code §512)
- Daily and weekly overtime thresholds
- Missing project assignments
- Any other rule violations configured for your organization
Submitting Your Timesheet
Resolve all compliance errors
Run the compliance audit and fix every flagged issue. The Submit section only appears when all errors are resolved and the audit is fresh.
Click Submit for Approval
In the Submit Timesheet panel at the bottom of the page, click Submit for Approval.
Read and certify
A certification modal appears with a compliance statement. Read the full text — by clicking I Certify & Submit, you are electronically signing that all reported hours are accurate and complete. This signature is recorded in the audit trail with a timestamp.
Tracking Approval Progress
Once submitted, click View History in the status banner to open the Approval History modal. It lists every action taken on the timesheet in chronological order — submissions, approvals, rejections, and revision requests — along with the reviewer’s name, role, and timestamp.Handling Revisions and Rejections
If your timesheet status becomes Rejected or Revision Requested, a colored banner appears at the top of the Timesheet page explaining what happened. You may also receive a notification on your dashboard.Read the reviewer's comments
Open the Approval History modal to see exactly what the reviewer noted. The comment appears alongside the rejection or revision-request action.
Edit the affected entries
Click any entry in the weekly grid to open the Time Entry Detail panel and make corrections. Because the timesheet was previously submitted, FieldTime will prompt you for a brief reason explaining each change — this reason is shown to the reviewer when they re-evaluate the timesheet.
Re-run the compliance audit
Any edit invalidates the prior audit. Run the audit again to make sure your changes do not introduce new compliance issues.
