Smart Care Safety Overview
| Area | Curr 12 | Rank | Prev 12 | Rank | Miles Since |
|---|
| Area | Curr 12 | Rank | Prev 12 | Rank | Hours Since |
|---|
| Area | Curr 12 | Rank | Prev 12 | Rank | Hours Since |
|---|
Incidents
District Headcount
Historical Data
Year-over-Year Trend
Planning & Standown Advisor
Safety Winners
Definitions
The Three Metrics
Total Vehicle Accident Rate
Vehicle accidents normalized per million miles driven. Counts every Preventable and Non Preventable collision regardless of fault.
A lower number is better. An area driving a million miles a year with one accident has a TVAR of 1.0.
Total Recordable Incident Rate
OSHA-recordable workplace injuries normalized per 200,000 work hours (the equivalent of 100 full-time employees working one year). Drives all federally reportable safety performance.
Lower is better. OSHA's national average across industries hovers around 2.7. Below 1.0 is considered excellent.
Lost Time Incident Rate
The subset of recordables severe enough to keep an employee from working their next scheduled shift. Same denominator as TRIR.
Lower is better. LTIR is typically 30-40% of TRIR for a healthy operation.
How Tech-Months & Miles Get Computed
Every district has a monthly headcount (from the Headcount tab) and a miles-per-tech-per-month rate (4,200 Climate / 5,200 FES / 5,500 Cafe Solutions by default). For any 12-month window, the dashboard:
- Walks each district month by month across the window. For each district-month, it pulls the tech count and the district's miles/month.
- For TVAR denominator: sum of (tech_count × miles_per_month) across every district-month in the window.
- For TRIR / LTIR denominator: sum of (tech_count × tech_hpm + tech_count × BO_per_tech) where tech_hpm comes from the Admin TRIR/LTIR card and BO_per_tech is the Climate or FES back-office hours allocation.
- Numerators come from the safety_incidents_monthly table. Each injury entry routes to the right bucket: Preventable / Non Preventable → TVAR; Recordable → TRIR; lost-time recordables → LTIR.
Tech vs Non-Tech Hours
The Excel model accounts for office staff (non-tech employees) in the rate denominator by spreading their hours across each technician. The flow:
- Tech monthly hours = (annual hours − vacation) × (1 + tech bump%) / 12. Defaults: (2,080 − 80) × 1.15 / 12 = 191.67 hrs/tech/month.
- Office headcount: 252 Climate + 488 FES + 77 "other" (split proportionally by tech ratio). Climate gets 252 + 28.4 = 280.4; FES gets 488 + 48.6 = 536.6.
- Non-tech annual hours per person = (annual − vacation) × (1 + non-tech bump%) = 2,000 × 1.10 = 2,200.
- BO hours/tech/month = (office_count × 2,200) / tech_count_ref / 12. Climate: (280.4 × 2,200) / 549 / 12 = 93.65. FES: (536.6 × 2,200) / 938 / 12 = 104.88.
- Full denominator/tech/month: 191.67 + 93.65 = 285.32 Climate; 191.67 + 104.88 = 296.55 FES.
All of these are editable in the Admin tab. The dashboard recomputes on save.
Severity Score (Planning & Standdown)
Used to rank areas for stand-down prioritization. It's a weighted sum of the three current-12-month rates:
The weights reflect injury severity. A vehicle accident is the baseline (1×). A recordable injury is weighted 5× because it almost always involves lost productivity, medical attention, and follow-up. A lost-time incident is 10× because the employee couldn't work the next shift — the most serious outcome short of a fatality. Areas with the top-3 severity scores get flagged for focused review on the Planning tab.
Curr 12 vs Prev 12 (Rolling Window)
"Curr 12" is the 12 months ending in the displayed reporting month. "Prev 12" is the 12 months immediately before that — so the two windows don't overlap.
With the reporting month set to March 2026:
- Curr 12 = April 2025 through March 2026
- Prev 12 = April 2024 through March 2025
This rolling window is why 2024 and 2025 historical tech counts and incident counts have to be accurate — they're the denominator for "Prev 12" and partially for "Curr 12" until December rolls over.
Miles Since / Days Since
TVAR — Miles Since: total miles driven across the area's vehicle fleet since the most recent Preventable or Non Preventable accident. Walks backwards month by month accumulating (tech_count × miles/month) until a month with a TVAR incident is found. A long number here means a long clean streak.
TRIR — Days Since: calendar days since the most recent Recordable injury logged for any district in the area. Pulled from the injury date on each safety_injuries row.
LTIR — Days Since: calendar days since the most recent month containing a lost-time incident for any district in the area. Resolved to the last day of that month.
Incident Type Routing
When you log an entry on the Incidents tab, the Incident Type field decides which metric the event contributes to:
| Type | Goes Toward | Notes |
|---|---|---|
| Preventable | TVAR | Vehicle accident where the driver could have avoided it. Counts toward TVAR for the district-month. |
| Non Preventable | TVAR | Vehicle accident where another party was at fault. Still counts toward TVAR. |
| Recordable | TRIR | OSHA-recordable workplace injury. Lost-time recordables additionally count toward LTIR. |
Admin
Branding
TRIR Calculation
TRIR = (recordables × constant) / (techs × hrs/mo × months)
Tech vs Non-tech are separate. Tech bump applies to technicians, non-tech bump applies to office staff.
LTIR Calculation
LTIR = (lost time × constant) / (techs × hrs/mo × months)
Same calculation structure as TRIR. Tech bump applies to technicians, non-tech bump applies to office staff.
TVAR Calculation
TVAR = (accidents × constant) / (techs × miles/mo × months)
Default miles per tech per month set separately for Climate and FES. Each district inherits its division's default unless explicitly overridden.
Non-Tech (Back Office) Allocation
Office staff hours get added to each technician's monthly hours in the TRIR / LTIR denominator. From the New TRIR/LTIR sheet, rows 29-45.
Climate office total (252 + 28.4 split) = 280.4
FES office total (488 + 48.6 split) = 536.6
Incident Constants
Standard OSHA constants: 1,000,000 miles for TVAR; 200,000 work hours for TRIR and LTIR.
Regions & Areas
Hierarchy: Region → Area → District. Each District has a Division attribute (Climate or FES).
Supabase Setup
Connected to eodlrvyvgqweouhxdpjr.supabase.co. Run this SQL once in the Supabase SQL editor, then click Seed Default Data. Also create a public Storage bucket named safety-files in Supabase Storage so injury photos and reports can be uploaded.