Wintertrace On GitHub →

Feature · Analytics

Built for review, not surveillance

The dashboard exists to help operators see what happened — what was done, when, by whom, for which customer. There is no scoring, no leaderboard, and no gamification.

Four views

Same data, four useful slices.

Day view

All operations of one day on a map and in a list, filterable by driver and by customer.

Month view

Summary of every operation in a month, grouped by date.

Per-driver view

Operation count, working hours, customers served, and operation-type distribution per driver.

Per-customer view

Operation frequency, total duration, and operation-type distribution per customer.

Wintertrace analytics dashboard showing operations-per-day chart, top customers list and driver statistics for Northwind Snow Services.
The analytics dashboard. Operations by day, top customers, driver activity — no scoring, no leaderboards.

Alerts that matter

The system flags three things automatically. Each alert can be acknowledged with an optional comment.

Missing GPS data

Non-manual operations with no GPS points.

Missing weather data

Operations whose weather fetch failed at start or end.

Overlong operations

Operations that ran longer than a configured threshold (default: 4 hours).

The dashboard also shows the cron heartbeat — whether the scheduled background tasks have been running. A silent cron is one of the most common operational issues; surfacing it makes it visible.

What the analytics deliberately do not do

Some software in this category tries to score employees — operations per hour, on-time percentage, peer rankings. Wintertrace does not. Drivers work in storms at four in the morning; turning that into a score is the wrong frame.

  • No leaderboards.
  • No "efficiency" or "performance" composite scores.
  • No streaks, badges, or peer comparisons.
Topic page: De-icing report software