After a compliance scan, every finding needs a decision: fix it, dismiss it, or tell Warrant it isn't relevant. This article explains what a finding shows, why some findings are dismissed automatically, and how your team's dismissals and relevancy feedback are used. It's for anyone who reviews scan results, and for admins who set up review settings.
New to scanning? Start with Scan an Asset for Compliance.
What a finding shows
Open a file, click Scan, and look at the findings list. Findings are grouped by regulator or policy source (for example a federal regulator, Disclosures, or Brand Guidelines). Each finding card shows:
Risk level: a High, Medium or Low badge with a matching icon.
Where it is: a page number for documents and PDFs, or a timestamp for audio and video. Click the card to jump to that spot in the file.
AI badge: every scan finding is generated by Warrant's AI. Hover over the badge to read: "This finding was generated by Warrant's AI system. A human reviewer makes the final decision."
Source: the policy or rule that was triggered, a description of the issue, and, when available, a View source regulation link, a Required Disclosure box with the copy that should appear, or a View Disclosure link.
Warrant also judges how confident it is that each finding applies to your content. Depending on your settings, findings it is less sure about can be dismissed automatically, as explained below.
How confidence and Review sensitivity work together
Your admin's Review sensitivity setting decides how confident Warrant must be before a finding is shown. See Global Sensitivity Control for Compliance Scans for how to change it. The levels run from Flexible, which shows the fewest findings, through Mild (the default), Balanced and High, to Maximum, which shows the most. Higher sensitivity shows more lower-confidence findings.
A few things to know:
Brand guideline findings can use their own level. If your admin sets Brand guidelines sensitivity to a level other than Same as compliance sensitivity (default), brand guideline findings are compared against that level instead. All other findings use Review sensitivity.
Your counts follow the same rule. The High, Medium and Low counts on the Scan tab and the Info tab only include findings that are open and meet your sensitivity level.
Relevancy Confidence Auto-Dismissal
This switch decides what happens to findings that fall below your sensitivity level. It's on by default.
On: when a scan runs, findings below your sensitivity level are dismissed automatically and marked System Dismissed. They don't count toward the compliance score and don't appear in the active list, but you can still review them (see below).
Off: no finding is dismissed because of low confidence. Every finding stays open for a person to review and counts toward the score.
The switch applies to scans run after you change it. Findings that were already System Dismissed stay dismissed until someone restores them. It doesn't affect dismissals based on reviewer feedback, described in How relevancy feedback is used below.
To change it:
Click Settings in the left sidebar.
Under Compliance, select Review settings.
In the AI compliance section, turn Relevancy Confidence Auto-Dismissal on or off. It appears when Enable AI compliance scanning is on, and changes save straight away.
Only admins can change this setting.
System Dismissed vs. Dismissed
A dismissed finding is grayed out and carries one of two labels:
System Dismissed: Warrant dismissed it automatically when the scan ran. The card reads Auto-dismissed by system with the date, and explains why, for example that its confidence was below your sensitivity level, or that reviewers previously marked its policy not relevant. Nobody has reviewed these findings.
Dismissed: a person dismissed it. The card shows who dismissed it, the date, and their reason if they gave one.
View dismissed findings
Above the findings list, click Dismissed. The number in brackets shows how many findings were dismissed in this scan. You can also click the gray Dismissed count next to the risk counts under the score.
Click Active to see only open findings, or All to go back.
Dismiss a finding
If a finding doesn't need a fix, for example because the issue is handled elsewhere, you can dismiss it.
On the finding card, click Dismiss.
Optionally, enter a Reason for dismissal. A reason isn't required, but it helps approvers and auditors understand your decision.
Click Dismiss to confirm.
The finding is removed from the compliance score, and the file's score updates straight away. Dismissing doesn't tell Warrant the policy was wrong. To do that, use relevancy feedback, described below.
Restore a dismissed finding
Dismissed findings, whether dismissed by a person or by the system, have two options:
Undismiss reopens the finding. It counts toward the compliance score again. No feedback is recorded.
Mark Relevant also reopens the finding, and records a "relevant" vote from you on it. Warrant asks you to confirm first. For a System Dismissed finding, the message reminds you that it was never reviewed and that marking it relevant records your review as an affirmative human judgement. Use this when the system was wrong to dismiss something.
Comment on a finding
Click the speech bubble icon on a finding to open its comment thread, type in Add a comment…, and send. The icon shows how many comments a finding has. You can edit or delete your own comments. Use comments to discuss a finding with your team before deciding what to do with it.
Give relevancy feedback
Relevancy feedback tells Warrant whether a finding was actually relevant to your content. It's separate from dismissing: you can give feedback on a finding whether or not you dismiss it.
On the finding card, click the thumbs up (relevant) or thumbs down (not relevant) icon.
In the Mark as Relevant or Mark as Not Relevant window, optionally add a note explaining why.
Click Relevant or Not Relevant.
A Relevant or Not Relevant tag appears next to the icons. Each person has one vote per finding. Voting again replaces your earlier vote.
If your admin turns on Show Relevancy Feedback on Flags (in Settings under Compliance, Review settings; off by default), the notes reviewers write appear on the finding itself, the way a dismissal reason does. When it's off, the notes are visible to admins only, on the Policy tasks & audit trail page.
How relevancy feedback is used
Votes are counted per policy across your whole company, not per file. They're only used for your company's scans, and they affect future scans, not findings that already exist.
Policy tasks: when a policy is repeatedly marked not relevant, Warrant creates a task on the Policy tasks & audit trail page suggesting an admin review that policy. Click Review Feedback on the task to see the votes. See Policy Tasks and the Policy Audit Trail.
Higher scrutiny: repeated not relevant votes on a policy make Warrant apply it more strictly, so it is flagged only when there is clear evidence of a violation. The Scan feedback summary shows a banner listing these policies.
Automatic dismissal: if not relevant votes keep outweighing relevant ones, new findings from that policy can be dismissed automatically and labelled System Dismissed, with a note that reviewers previously marked it not relevant. This happens even when Relevancy Confidence Auto-Dismissal is off.
Relevant votes, including those from Mark Relevant, count against not relevant votes. If a policy keeps getting dismissed but your team finds it useful, marking its findings relevant brings it back. If a policy really doesn't fit your business, an admin can edit, lower the risk level of, or disable it on the AI Policies page.
Where it's recorded
On the finding: who dismissed it, when, and the reason, or why the system dismissed it.
Policy audit trail: every thumbs up, thumbs down and Mark Relevant vote appears in the Policy audit trail with the person, the policy and any note. Filter by Feedback to see only these entries, and click Download CSV to export them.
The file's audit trail: thumbs up and thumbs down votes, and comments added, edited or deleted on findings, also appear in the file's history on the Info tab.
Who can do what
Dismiss, Undismiss and Mark Relevant need the Review permission.
Thumbs up and thumbs down need the Relevancy Feedback permission.
Commenting on findings needs the Comment permission.
Changing Review sensitivity, Relevancy Confidence Auto-Dismissal or Show Relevancy Feedback on Flags needs admin access.
If you don't see these buttons on a finding, ask your admin to check your role. See Managing Roles & Permissions.