Verdicts are possible-match, never “cleared”
Screening never returnspass, fail, or cleared. It returns one of:
| Verdict | Meaning |
|---|---|
review | A possible match was found at or above the score threshold. A human should review it. |
no_match | No match was found in the checked registers as of the checked date. |
unavailable | A register could not be read. This is never reported as a clean no_match. |
review. A DOB match
raises confidence but a missing or non-matching DOB never excludes a candidate, because
the DFAT date-of-birth field is multi-value and cannot be reliably parsed. A name hit
without a DOB match still warrants review.
Always know which register produced a hit
Every screen response breaks the verdict down by underlying register, so you can see exactly what matched:review if any source is review, unavailable if any source
is unavailable, otherwise no_match. A read failure fails safe to unavailable, so
an outage can never look like a clean result.
Screening a trust screens the trustee
For a trust, AUO screens the resolved corporate trustee, not the trust, because that is where liability sits.The disclaimer is always present
Every screen response includes a disclaimer stating that no match found is not a clearance and that possible matches require human review. It is part of the contract, not boilerplate you can ignore.Next
Screen endpoint
The request and response reference for POST /screen.
Honest boundaries
Where screening fits in the wider picture of what AUO covers.