FieldCampTimesheet settings | FieldCamp
Configure FieldCamp Timesheet: geofence radius, overtime trigger, paid travel and breaks, clock-in methods, exception rules, evidence weights and site overrides.
Timesheet settings control how the verified ledger is built: how close to the job site a technician has to be, when overtime starts, what counts as paid, which checks run, and how much each piece of evidence is trusted.
Before you begin
- Every setting on this page is admin tier only — workspace owner, Super Admin or Admin. A dispatcher who opens it sees “You don't have access to this page”.
- Changes apply workspace-wide and affect how future days are reconstructed.
- Site geofence overrides need the client site to exist first. See How to create a client.
Open Timesheet settings
- Open Timesheet.
- Select the settings control on the right of the tab bar.
- Use Back to ledger to return.
Each section saves on its own, so you can change one card without touching the others.
Company defaults
| Setting | What it does |
|---|---|
| Geofence radius (meters) | How close to the job site an action must be to count as on-site |
| Overtime trigger | Weekly (over 40h), Daily (over 8h), or Double-time after 12h/day |
| Holiday multiplier | The rate multiplier applied to holiday hours |
| Verified threshold (%) | The confidence score at or above which a block is marked Verified |
| Partial threshold (%) | The score at or above which a block is marked Partial; below it, Low |
| Pay first & last drive | Counts the first and last drive of the day as paid travel |
| Paid breaks | Counts recorded breaks as paid time |
The geofence radius does not block anyone. Working outside the radius, or with GPS unavailable, is allowed and then flagged for admin review.
Site geofence overrides
Use an override when one client site needs a different radius from the company default — a large yard, a rooftop, or an address that geocodes slightly off.
- Select the client site.
- Enter the Geofence radius, Site latitude and Site longitude.
- Select Save site geofence.
All three fields must be valid numbers. FieldCamp shows Enter valid numbers for the geofence fields if any of them is not.
Clock-in methods
Turn on the ways your technicians are allowed to go on the clock:
- Geofence auto — entering the job site starts the clock
- Manual tap — the Start day button on My day
- Job-status auto — moving a visit forward starts the clock
- NFC / QR tag — scanning a tag at the site
Exception rules
Each check has its own row with three controls:
| Control | What it does |
|---|---|
| Enabled | Turns the check on or off |
| Severity | High, Medium or Low. High-severity flags block a payroll export |
| AI autonomy threshold | The confidence FieldCamp needs before it resolves the flag itself |
Below the threshold the assistant only suggests a fix; at or above it, the fix is applied automatically. Set the threshold to 100 to always require a person.
Out of the box, most checks ship at 100 — suggest only. The exceptions are Manual time edit and GPS stale, which can auto-resolve at high confidence. Severity ships as high for missed clock-outs, off-site clock-in and clock-out, off-site visit actions, work started without Start Day, and overlapping jobs.
Each row is saved as soon as you change it.
Evidence weights
Every travel, work, pause or idle block gets a verified percentage — how sure FieldCamp is that it really happened. Evidence weights set how much each kind of signal inside a block contributes to that score.
Set a weight from 0 (ignored) to 100 (trusted most) for each combination of Segment kind and Event kind:
| Signal | What it is |
|---|---|
| GPS location ping | A periodic location reading from the technician's phone |
| Clock in / out | The technician tapped clock-in, clock-out or break |
| Visit status change | The visit moved forward — On my way, Arrived, Started, Completed |
| Job-site entry / exit | The phone crossed the job-site boundary |
| Break | A break started or ended |
| Manager edit | A manager corrected the block by hand |
| AI correction applied | An AI-proposed fix that was approved |
Weights are summed per block and capped at 100. Raising a signal you trust — geofence transitions, for example — pushes more days into Verified and leaves fewer for manual review.
Setting every weight low means almost nothing reaches the verified threshold, and the exception inbox fills up. Change one weight at a time and watch the next week's verified percentage before adjusting further.
Related articles
Labor profitability | FieldCamp
See what your labor hours earned in FieldCamp — overall margin, total labor cost against revenue, and a per-job list that flags the jobs running over.
Creating Estimates | FieldCamp
Create professional estimates (quotes) in FieldCamp with multi-option pricing, line items from your price book, deposits, customer approvals, and one-click job conversion.