1,847 findings reviewed.
Prove it.
Your auditor wants evidence that your team reviewed every ARM finding this period. Who reviewed it, when, and why it was marked expected. Without Sentry, the answer lives in Slack threads and someone's memory. With triage, it's one CSV.
Fix everything, or ignore things and hope.
A plan sits past its end date with $241K remaining balance. The controller knows the customer renewed and the backdated plan is processing. But the finding still shows in the population. So they either spend time fixing a record that will resolve itself, or they skip it and lose the audit trail.
During audit, the question is always the same: “Did you review this population?” The controller says yes. The auditor asks for evidence. The controller searches Slack for a message from three months ago.
A reason, a comment, and a fingerprint.
Click a record. Pick one of five structured reasons your auditor already recognizes. Optionally add a comment. Sentry snapshots the record's key fields so it knows if the data moves later.
The row greys out. The count moves. The log records it.
Status chips on the findings table track progress in real time: Active drops, Acknowledged rises. The dismissed row stays visible at half opacity with an undo link. An entry appears in the Activity Log with your name, the reason, and the timestamp.
Dismissed doesn't mean forgotten.
You dismissed RP-4412 on April 3rd. Two weeks later the balance grew from $241K to $248K. The fingerprint no longer matches. Sentry re-queues the record, highlights the row in amber, and shows you what changed: old value vs. new, with the original dismissal context preserved.
Three options. Keep dismissed. Update the reason. Or bring it back to active so it counts against the close gate again.
Exception: “Intentional” suppresses permanently. The record stays dismissed regardless of future data changes.
Every decision, timestamped, with the user's name on it.
The Activity Log records every dismiss, restore, and resurface. The progress bar shows where you are: 238 of 1,847 reviewed. Filter by action type, user, or time range. Export the full trail as CSV for the close binder. Your auditor doesn't need Sentry access. They need the file.