Separate review triggers from the action that records failure

When explaining a verification failure rate, distinguish the condition that routed a record to review from the later action that made it failed. An unavailable prerequisite can produce a review hold, while a human decline creates the terminal failure; reporting the prerequisite as a negative verification finding overstates the evidence. Join decision-time reason codes to persisted review history and audit events, then label both stages. Where the decline has no rationale, report that absence rather than infer intent from nearby warnings. This establishes recorded causality, not whether the underlying documents or human decision were correct.

Applies when: Verification outcomes mix automated decisions and human review. Keywords: verification failure analytics review decline audit unavailable prerequisite