Exception inbox | FieldCamp
Review the FieldCamp timesheet entries that cannot be auto-confirmed, approve a suggested fix, edit the time yourself, or override and dismiss a flag.
The Exception inbox is the only Timesheet screen you have to work every week. The ledger confirms whatever it can from clock punches, geofences and visit activity; anything it cannot confirm lands here as an exception with the evidence attached.
Every action on this screen appends to the audit trail. Nothing is overwritten.
Before you begin
- Resolving exceptions is a manager action. Admin and Dispatcher tiers can resolve; technicians can only see their own flags on My day.
- Which checks run, how severe each one is, and when FieldCamp may resolve one on its own are configured in Timesheet settings.
Open the inbox
- Open Timesheet.
- Select the Exception inbox tab, or select Resolve exceptions on the ledger.
The header shows the open count and, when relevant, how many are blocking payroll. Filter with All, High, Medium or Low.
The inbox is not tied to the period picker. It lists every open exception, whichever week it came from.
Exception types
| Exception | What triggered it |
|---|---|
| Missed clock-out | A shift was started and never ended |
| Clocked in away from job site | The clock-in location fell outside the geofence |
| Clocked out away from job site | The clock-out location fell outside the geofence |
| Visit action outside geofence | A visit status change or work-timer action happened away from the site |
| Location needs review | A location was captured but could not be confirmed |
| Location permission off | The device did not allow location access |
| GPS stale | The last location reading was too old to trust |
| Visit started without Start Day | Work was started on a visit with no open shift |
| Overtime risk | The day or week is heading past the overtime trigger |
| Long idle on-clock | A long gap on the clock with no work evidence |
| Overlapping jobs | Two jobs claim the same minutes |
| Manual time edit | A manager changed a time by hand |
| AI-flagged anomaly | The anomaly check flagged the day as unusual |
Resolve an exception
- Select an exception in the list. The detail panel opens with Evidence we have and, where one is available, FieldCamp's suggestion.
- Choose one action:
| Action | What it does |
|---|---|
| Approve fix | Applies the suggested correction and closes the exception |
| Edit instead | Opens the technician's day so you can set the time yourself |
| Override | Closes the exception without applying a fix |
| Dismiss | Closes the exception as not actionable |
- The row is marked resolved and the payroll figures are re-audited.
Selecting Override asks you to confirm, because it clears the flag without correcting the underlying time.
Use Open day on any exception to jump straight to that technician's day view with the full timeline and evidence trail.
Suggested fixes
When a suggestion is being prepared, the panel shows FieldCamp is reviewing this flag…. If no suggestion can be produced you see No automated suggestion — review manually, and only Override and Dismiss remain.
How confident the assistant has to be before it resolves a flag on its own — instead of only suggesting — is the AI autonomy threshold on each rule in Timesheet settings. Set it to 100 to always require a human.
Exceptions and payroll
High-severity exceptions block a payroll export. On Payroll review a technician with open high-severity flags shows Resolve instead of Approve, and the export dialog lists everyone who is blocking. You can still choose Export anyway — the override is recorded.
Related articles
Review a technician's day | FieldCamp
Open a FieldCamp technician's reconstructed day, read the segment timeline and evidence trail, correct clock punches and work-timer entries, and clear flags.
Payroll review and export | FieldCamp
Review verified hours for a pay period in FieldCamp, approve each technician, and export payroll to CSV for Gusto, ADP or Paychex, or prepare a QuickBooks sync.