What the team burnout score actually measures

A 0–100 risk score per technician, recomputed live over a rolling 7-day window — always "the last 7 days as of right now", not tied to the payroll period. It's visible on Reports, on the mobile Insights screen, and answerable by the assistant ("is anyone at risk of burnout this week?").

It's built from exactly three signals, all of which the app genuinely has:

Hours over a standard 40-hour week — 3 points per overtime hour, capped at 60 (reached at a 60-hour week). Job-stop density — average distinct visits per working day above 4/day, as a stand-in for travel and context-switching load, capped at 25. Consecutive days worked — 15 points for all 7 days, 8 for 6 of 7, otherwise 0.

Job-stop *count* is used rather than real drive time on purpose: actual mileage would need every customer address geocoded, which only happens for businesses with SerpApi connected and only for addresses saved since. A proxy that works for everyone beats a precise number that's missing for half your team.

Any score of 80+ comes with a plain-English recommendation, and every score shows the specific factors that drove it — never just a bare number.