The case where paperwork should never be the reason a damaged vehicle goes back out. It's also the safest rule to start with, because a failed accident report is one you'd never want to ignore anyway.

Any of the rules below reads like this once built — trigger, conditions and actions in three blocks.

Closes the gap between a serious fault being found and a job existing for it. Because it's driven by severity rather than by form, it catches critical defects however they arose — including ones added by hand.

Check your severity definitions before switching this on. If your inspectors use critical loosely, you'll create more work orders than you want. That's a good reason to look at the severity distribution in your defects first.

Turns a written policy into a control. This one fires far more often than the accident rule, so build it after you've watched a narrower rule for a week — and brief your drivers before you switch it on.

For a vehicle that's been through the shop repeatedly and needs a tighter leash than the rest of the fleet. Easy to remove once it settles down — and because it's scoped to one asset, it can't surprise you at scale.

The defect trigger fires for faults reported by diagnostic codes as well as ones found by people, so a rule built on severity covers both without any extra setup. If your telematics integration raises defects, this catches them.

The pattern that works: build the narrowest version, leave it a week, then open the Runs tab and look at what it caught and what it skipped.

The skipped runs are the interesting ones. They show you the events that were close but didn't match, which tells you exactly what a wider version of the rule would have acted on. Widen one condition at a time, and check again.