A decision point is a preplanned time or location at which a chase team commits to a clear field choice, such as holding the current position, repositioning, switching cells, or ending operations. It converts vague intent into a specific check that the driver, navigator, and observer all recognize.
How they are set
Decision points are chosen while there is still time to think. A common pattern is a time-based check, for example a target-arrival deadline after which the team commits or aborts, and a location-based check, for example a specific intersection past which no further eastward pursuit is allowed.
The Skywarn safety guidance built around Awareness, Communication, Escape Routes, and Safe Zones assumes exactly this kind of planning. Knowing where you are willing to be and where you are not before the storm arrives is how those principles actually get enforced.
How they are used in the field
A navigator calls decision points out loud as they approach. At each one, the team names the current storm state, the current road situation, and the intended next move. If any of those has changed enough to invalidate the plan, the plan is updated on the spot.
For high-drama situations near a tornadic supercell, decision points may be spaced only a few miles apart. For a slow-moving cell on a benign day, one every fifteen minutes may be enough.
Where they fail
The most common failure is emotional. A cell looks better than expected, and the team drives past the abort trigger because reversing feels like giving up. Another is ambiguity, where the trigger was set in words no one can now agree on.
A third failure is stacking too many decision points without honoring any of them. If every intersection is a check, none of them functions as a real commitment, and the team slides toward whatever position looks most exciting in the moment.
Good decision points are specific, honored, and reviewed. If a plan quietly slid past a trigger without anyone calling it, that is worth talking about at the end of the day so the next chase does not repeat it.