Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tread.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
What this solves

Driver hours are where billing teams lose their afternoons. Every shift produces a timesheet with arrival, on-site, and departure times — and on a multi-site contractor day, one truck can generate three timesheets. Approving them one by one is how teams end up with a five-person billing department managing what should be a one-person job. This workflow lets a payroll lead approve a full day’s timesheets in one screen, with anything questionable flagged automatically.

​
Walkthrough

1

Open the timesheet queue

Go to Approvals → Timesheets. Hours are grouped by driver, by day, and by job. Use filters to narrow to a date, a foreman, or a single project.
2

Pick an approval lens

Choose how you want to approve: By Job (a foreman’s whole crew on one project), By Day (every driver’s hours for a date), or By Exception (only timesheets the agent flagged). Most teams run By Exception first to clear flagged hours, then By Day for the rest.
3

Review flagged exceptions

The agent flags timesheets with mismatched geofence times, missing breaks, overtime triggers, or hours outside the dispatched shift. Each flag has a reason and a recommended fix.
4

Edit hours inline

Click a row to adjust start, end, or break time. Tread shows the geofence-derived time next to the proposed time so you see exactly what changed. Add a note for the audit log.
5

Bulk-approve the clean timesheets

Select all, then Approve. Approved hours flow into Settlements & Driver Pay and any payroll export you’ve configured.
6

Confirm the day is closed

The job header shows green when every driver’s timesheet is approved. Re-open is one click if a correction comes in later.

​
Watch it

​
Common pitfalls

Geofence times are the source of truth — adjust them, not the timesheet. Editing a timesheet without correcting the underlying geofence event creates a mismatch that surfaces later in disputes. If a driver clocked in 20 minutes before the geofence registered arrival, fix the geofence event (or the geofence itself), then let the timesheet recalc.
One truck, one site = one timesheet — usually. A multi-jobsite day can produce three timesheets for one driver. A contractor running cross-town hauls flagged this on day one of onboarding because their old system rolled hours into one record per day. Confirm your team understands the per-job model before go-live.