Wintertrace On GitHub →

Feature · Shift management

Hours captured by the work, not by hand

Drivers do not enter timesheets. They start their shift, run their operations, and end their shift — the system records exactly when. Payroll exports follow directly from the captured data.

Shift workflow

  1. 1

    Start shift

    The driver opens the app and starts their shift. Timestamp is captured automatically.

  2. 2

    Run operations

    During the shift, any number of operations can be started, paused, and ended. Each one ties back to the active shift.

  3. 3

    End shift

    The driver ends the shift. Duration and totals are computed automatically.

Wintertrace admin shift list with a week view of four drivers, status colours, and start and end timestamps for each shift.
Weekly shift overview in the admin area. Status colours flag missing or overlapping shifts.

CSV export for payroll

Operation data — including shift links — exports to a single CSV file that drops cleanly into Excel, Google Sheets, or payroll systems. Filterable by time range, driver, and customer.

  • · Operation date
  • · Driver
  • · Customer
  • · Service location
  • · Operation type
  • · Start and end time
  • · Duration
  • · Shift ID
  • · Source (manual / automatic)

The source column distinguishes automatic operations (captured live via GPS) from manual operations (back-entered after a tech failure or for early-morning runs before the app was started).

Manual operations

Real life: phones die, the app crashes, someone forgets to start recording. Manual entry covers all of that.

Operations can be entered manually in the admin area or in the driver app — date, time, customer, service location, operation type, and vehicle. Weather data is fetched retroactively for the chosen time. Manual operations are flagged as such on the PDF service proof so the documentation chain remains honest.

Topic page: Snow service time tracking