Every unit assignment is scored across crew fatigue, vehicle condition, weather, call acuity, and system tempo — automatically, in the seconds between dispatch and rolling. Your supervisor sees the number, and the reasons behind it, while there's still time to act.
Each dimension is scored 0–100 on its own, then weighted into a composite. Every sub-score returns its drivers — the specific factors that moved it — so a supervisor sees why the number is what it is, not just that it's high.
Risk doesn't add up — it compounds. When two or more dimensions cross the line together, an interaction multiplier lifts the composite above the plain weighted average. Weights, thresholds and multipliers are all yours to tune, with Conservative, Standard and Aggressive presets to start from.
Most fatigue policies rely on someone speaking up at shift change. This reads the schedule you already keep, and asks the crew directly when it matters.
Hours on task, rolling 24/72/168-hour totals, and consecutive shifts come straight from your existing clock-in records. Nothing new to maintain.
Crews check in with the Karolinska Sleepiness Scale and Samn-Perelli — the same instruments used in aviation fatigue research — plus hours slept.
A check-in appears at clock-in and scheduled reminders reach on-duty crews, so the data is fresh when a call actually drops.
Four levels of response. Set the one that matches your service's culture and medical direction — nothing fires that you haven't chosen.
The score and its drivers are logged and shown on the call. No interruption to the dispatch.
All plansA high-risk dispatch notifies supervisors immediately, with the contributing factors attached.
Pro and aboveThe call is flagged for acknowledgment. Crew or supervisor confirms they've seen the risk, and that confirmation is recorded.
Pro and aboveThe dispatch cannot advance until a supervisor overrides it with a written reason — creating a documented decision every time risk is accepted.
EnterpriseAcknowledgements, overrides and mitigations are all recorded against the assessment — so the record of what you knew, and what you decided, is there when someone asks.
Environmental data is pulled at assessment time and sampled along the actual route — every ten miles, not just at the origin and destination.
Current conditions and active alerts for the response area.
Real-time traffic and routing along the path the unit will actually drive.
Live road status where the state publishes it, starting with Ohio.
Dawn and dusk glare windows, calculated locally for the exact call location.
AQI for respiratory-driven call volume and crew exposure.
Scheduling, fleet maintenance and dispatch history already in RescueLink — no integration work.
| Capability | Basic | Pro | Enterprise |
|---|---|---|---|
| Risk scoring, logging & objective fatigue | ✓ | ✓ | ✓ |
| Crew fatigue check-in | — | ✓ | ✓ |
| Air quality data | — | ✓ | ✓ |
| Supervisor alerts | — | ✓ | ✓ |
| Soft stop | — | ✓ | ✓ |
| Custom thresholds & weights | — | ✓ | ✓ |
| Hard stop with documented override | — | — | ✓ |
| Historical backtesting | — | — | ✓ |
| Per-state DOT road data | — | — | ✓ |
| Assessments per month | 5,000 | 50,000 | Unlimited |
| History retention | 90 days | 365 days | Unlimited |
We'll score them against your own schedule, fleet and weather history, and show you which runs would have raised a flag. Then you decide whether the number was right.
Request a demo