Exception alerts are prompts, not verdicts

A flag is a question, not an answer

Exception review compares what the card says against what the truck says. When gallons look high for the miles driven, Spartan Stack flags the charge for a second look. The flag tells you where to look. It does not tell you what happened.

Common reasons a flag fires

Plenty of flags have ordinary explanations. A reefer unit took part of the fill, the truck idled through a long wait at a shipper, or mileage data came in late. Check the obvious causes before assuming anything else.

How to work a flag

• Pull up the charge, receipt, and miles side by side
• Check for reefer fuel, idle time, or late mileage
• Ask the driver in the same thread
• Close it with a note on what you found

Ask, don't accuse

How you ask matters. "Help me understand this fill" gets a straight answer. An accusation gets a driver who stops texting receipts, and then you have less data, not more. Most flags close in one message when the question is honest.

When a pattern means more

One flag is noise. The same card or truck flagging week after week is worth a closer look, and the notes left on earlier flags make that review faster. Tighten card controls if you need to, but base it on the pattern, not a single alert.