1. Time Tracking
  2. Who it's for
  3. Hourly and field teams
Who it's for

Hourly and field teams

Field technicians, support staff and other hourly teams are paid from their timesheets. Time is often captured on a phone away from a signal, daily limits and overtime thresholds apply, and payroll depends on approved, locked hours each pay period.

How Time Tracking is set up for you

Mobile capture offline

Entries queue on the phone and sync on reconnect.

Daily and weekly limits

Policies cap daily hours and set the weekly overtime threshold, with violations recorded.

Exempt and non-exempt staff

Assign policies by classification and state of work.

Payroll by pay period

Locked entries are bundled per person at each period end.

Field technicians, support staff and other hourly teams are paid from their timesheets. Time is often captured on a phone away from a signal, daily limits and overtime thresholds apply, and payroll depends on approved, locked hours each pay period.

Start with one hourly team on one pay calendar. Assign policies, roll out mobile entry and run two pay periods through approval, lock and payroll export. Reconcile the bundles with payroll before adding teams.

[Plan the rollout](/time-tracking/implementation), [review the modules](/time-tracking#modules), and [compare the source data](/time-tracking/data-model).

Features to start with

Roles on the team

Resource
Logs time on the web, on mobile or with timers, submits weekly timesheets and requests unlocks for locked weeks.
Resource Manager
Approves timesheet steps for their direct reports and follows up on late timesheets and policy violations.
Controller
Owns time policies, approval rules, rates, pay calendars and lock exemptions, decides unlock requests and approves controller steps.
Admin
Maintains resources, users and configuration without approving time.

Set up Time Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started