Classify a repeated parked-fluid mark as an active leak, residue, or insufficient evidence by controlling the surface, parked condition, elapsed time, and source-path evidence.
Core rule
A spot is not proof of an active leak until fresh fluid reappears or progresses under a controlled, comparable recheck.
Use this after a parked-fluid mark has been logged, after cleaning a suspected source area, after a repair, or anytime an old stain, splash, trapped fluid, or undertray residue may be mistaken for an ongoing leak.
Safety / evidence gate
Do not touch, smell closely, or road-test around an unknown hazardous fluid. Fuel, brake fluid, hot coolant, pressurized fluid, or fluid reaching tires, brakes, belts, exhaust, or electrical components requires a safety-first inspection before continued operation.
1Vehicle / Job Information
Start clean
2Repeat Check Condition Lock
Comparable or inconclusive
Lock the recheck setup before interpreting the mark. A different parking surface, vehicle position, temperature state, or parked time can create a false comparison.
3Original Mark Reference
Name what is being compared
4Repeat Spot Capture
Record before interpreting
5Active-Leak vs Residue Separation
Trace the wettest point
Evidence Supporting an Active Leak
Check only what was directly observed during this controlled recheck.
Evidence Supporting Residue / Carryover
Residue evidence can explain the mark, but it does not prove the system is sealed.
6Drift / Safety / Evidence-Quality Check
Catch the false call
Hard stop: Do not continue operating the vehicle when fluid may reach a tire, brake friction surface, steering component, belt, hot exhaust, high-current electrical connection, or when fuel, brake fluid, or a major coolant loss is suspected.
7Final Classification
Choose only what the evidence supports
Boundary: “Residue” means the controlled repeat check did not support an active release from the inspected area. It does not prove every seal, hose, fitting, vent, drain, or system is leak-free. “Active leak” identifies ongoing release evidence; it does not identify the failed component unless the source point and failure path were directly proven.
8Release / Routing Check
Do not close it weak
Stay in the loop
Get new drops in your inbox
New QTS builds, tools, and garage stories — straight to your inbox. No spam. Unsubscribe anytime.