Why log false alerts?
Too many false alerts teach drivers and reviewers to ignore the system. Too few can mean real events are missed. A log shows which alert types, vehicles and conditions cause the false ones, so you tune with facts and not with guesses.
How to use the log
- Fill in Setup. Enter the first day of week 1 and edit the lists of alert types, causes and actions.
- Log each alert you review. Date, vehicle, alert type, then the result: confirmed, false alert or unsure.
- Pick a likely cause for every false alert, and the action you took.
- Open the Weekly view. See the false-alert rate per type and per week.
- Decide and record. Use Decisions for the next step, and Setting changes for every change you make.
How the false-alert rate works
The rate counts only alerts you could judge. Unsure alerts are shown separately so they do not hide in either group.
Weeks with fewer reviewed alerts than the number in Setup are shown in gray. A rate based on a handful of alerts can swing a lot from week to week.
Fix the cause before the setting
Most false alerts have a physical cause: glare, glasses, a camera tilted down, a dirty lens, a loose mount or a passenger in view. The Causes sheet shows which cause explains the most false alerts, so you start there.
Lowering a sensitivity to cut false alerts can also hide real events. Fix the physical cause first. If you still change a setting, change one, write it in Setting changes, and compare the next week.
Reviewing video: privacy
Reviewing driver video can be regulated where you operate. Follow your company policy and local rules. This log stores references to clips, not video, and it is not legal advice. For the driver notice, see the in-cab camera notice template, which also needs legal review.
Limits of this log
It records and counts what you enter. It does not connect to a device, and it does not know which alerts your device reports. A sample of alerts can mislead if it is not typical, so write down how you chose it.