Skip to main content
A revision is required when an approver returns your timesheet because one or more entries need to be corrected. FieldTime’s revision process is designed to be transparent: every change you make after the first submission is tracked with a required reason, and approvers see a before/after diff of each change so they have full context when re-approving. The revision count increments each time you resubmit, and the complete history is preserved in the audit trail.

​
When a revision is needed

Your timesheet enters revision status in two situations:
  • Revision Requested — an approver has asked for specific changes and provided comments. The timesheet is returned to you at step zero (your editable draft state) so you can make corrections.
  • Rejected — an approver has outright rejected the timesheet. The effect is the same: the timesheet is unlocked and returned to you for correction.
In both cases, the approval workflow resets completely. Prior Project Manager line approvals, Supervisor approval, and any partial Payroll approval are all cleared. After you resubmit, the full approval chain restarts from step one.
Timesheets with Locked status (after final Payroll/Admin approval) cannot be revised through the normal revision flow. A Locked timesheet requires an Administrator to explicitly reopen it before any changes can be made. Reopening creates an audit entry and triggers a full re-approval cycle. Contact your payroll administrator if a locked timesheet needs to be corrected.

​
Revision workflow

1

Receive the rejection notice

When an approver rejects your timesheet or requests a revision, you will see a notification. The timesheet status badge on the Timesheet page changes to Rejected or Revision Requested and an amber banner appears at the top of the page.Click View History in the banner to see the approver’s comments in the full audit trail. The most recent action shows the reason the timesheet was returned and what the approver expects you to change.
2

Review the rejection comments

Read the approver’s comments carefully before making any changes. Common reasons for revision include:
  • Incorrect project, phase, or task assignment on one or more entries.
  • Missing or inaccurate meal break records.
  • Clock times that do not match field records or sign-in sheets.
  • Labor classification discrepancies (for prevailing wage projects).
  • Hours recorded on the wrong day or against the wrong project.
If the comments are unclear, contact your approver directly before editing — each edit you make requires a reason, and a well-informed reason helps the PM approve faster on the next cycle.
3

Update your time entries

With the timesheet unlocked, edit the entries that need correction. Click any entry in the weekly grid to open the Time Entry Detail panel.Because this timesheet has been submitted before, every change triggers the Change Reason prompt. Enter a brief explanation of what you changed and why — for example, “Corrected clock-out time; I left at 17:00, not 18:00” or “Moved entry to correct project code per PM’s comment.”The following changes are tracked and shown to the PM as diffs:
FieldExempt employeesNon-exempt employees
Project / Phase / Task✅ Editable with reason✅ Editable with reason
Labor classification✅ Editable with reason✅ Editable with reason
Manual hours✅ Editable with reason❌ Non-exempt employees use punch times
Clock-in / Clock-outN/A (exempt use manual hours)✅ Editable with reason
Meal breaksN/A✅ Editable with reason
Notes✅ Editable with reason✅ Editable with reason
Adding a new entry: Click + Add in the daily column where the entry is needed. New entries added during a revision are flagged NEW in the PM’s approval view.Deleting an entry: Previously submitted entries cannot be hard-deleted. Clicking Request deletion marks the entry for deletion pending PM approval. The entry remains visible (struck through) until the PM approves the deletion.
4

Re-run the compliance audit

After making all corrections, scroll to the Compliance Audit panel and click Run Audit. Resolve any errors or new findings that appear. The audit gate must be fresh — any edit after the last audit run resets the gate, so always audit as your final step before resubmitting.
5

Resubmit for approval

Once the audit is fresh and all errors are resolved, the Resubmit for Approval button appears. Click it, review the Employee Certification statement, and click I Certify & Resubmit.FieldTime increments the revision count on the timesheet, takes a new snapshot of all entry states as the updated baseline, and routes the timesheet back through the full approval workflow from step one.The status banner updates to show Submitted — Revision #N so approvers can see this is a revised submission.

​
Revision count tracking

Every time you resubmit a timesheet after a rejection or revision request, the revision count increases by one. You can see the current revision count in the Resubmit for Approval button label, which displays “Revision #N”. The full revision history — including every submission, every approval or rejection, and every change reason — is available in the View History audit trail for the timesheet.
There is no limit on the number of revisions. However, repeated revisions delay payroll processing. Resolve all comments thoroughly on each cycle to keep the approval chain moving.