Appearance
Running checks
Entity checks
The Checks section on the entity page has a dropdown of what can be run and a Run check button. Needs entity.review.refresh.
Running a check creates one EntityCheck and one ProviderFetchRun. It does not start or modify a review.
The dropdown is filtered by what the entity can support: IBAN verification appears only with an IBAN on file, domain intelligence only with a website.
Most checks run synchronously and the flash reports the outcome by name — Commercial registration refresh ran successfully or … ran but failed. See the check row for details. IBAN verification is asynchronous and reports has been queued.
Party checks
Run from a person's card under Relationships: Screen, Identity, Address, Digital ID, Employment, Other registrations. Needs entity.review.create.
Each button reflects the state of that check for that person:
| Shows | Means |
|---|---|
| The check name | Not run — click to run it |
| Retry … | The last run failed |
| A past-tense label | Completed |
| In progress | Running |
| Needs date of birth | Blocked — links to the person page |
Retrying
A failed check leaves a Retry failed checks item in Next steps with a Re-run button that carries the failed check's type.
A retry creates a new check record; the failed one stays as history. Intake posture reads only the most recent run of each type, so a successful retry clears the failure — the entity is not locked out by a transient provider error.
When a check cannot run
Verity refuses rather than sending a request it knows will fail:
| Situation | What you see |
|---|---|
| No date of birth in the calendar the service matches on | Needs date of birth, linking to the person |
| Passport-only person, other-registrations check | Refused — Wathq needs a nationality code Verity does not hold |
| No IBAN | IBAN verification not offered |
| No website | Domain intelligence and website scan not offered |
| Person party required | Organization checks run at entity level; the card says so |
After a check
- Verification coverage may move, if the check satisfied a scoring rule
- Gates may become evaluable — a gate that could not be read may now be clear or triggered
- Risk does not change on its own. Run Assess risk for that.
That last point is deliberate: the band carries a timestamp, so it should reflect a moment somebody chose, not drift silently as evidence arrives.