Most organisations can show you a sanctions screening report. Far fewer can show you which contract it belongs to, which list version it was run against, or whether anyone looked again after the agreement was signed. The check exists, but it exists in a screening tool, on a date, for a name that may or may not match the legal entity written into the agreement.
That gap matters because designations move and contracts do not. A supply agreement signed in March runs through the next three years, across list updates nobody connected back to the contract record. When a regulator or an internal auditor asks what you knew and when, the answer has to come from the agreement, not from a tool export that someone has to reconcile by hand.
Treating screening as a contract control rather than a compliance errand changes three things: where the check is triggered, what it writes down, and how often it repeats. None of those changes require a new screening vendor. They require the screening result to become a field on the contract record with an owner and a review date attached to it.
The five failure patterns behind most screening gaps
The gaps are rarely about list quality. They come from process placement, from counterparty data that cannot be matched reliably, and from evidence that lives somewhere the contract record cannot reach. Five patterns account for most of what audit teams find.
- Screening at the wrong moment, the check runs after a counterparty has already been created and a purchase order issued, so clearing it is a formality rather than a gate.
- Name-only matching, the screen runs against a trade name with no registration number or address, which produces either a flood of weak hits or a confident miss.
- No link to the agreement, the result sits in a screening platform with its own identifiers, so nobody can answer which contracts a given counterparty actually has.
- One screen, then silence, the relationship is monitored for the days before signature and ignored for the years after, which is the opposite of where the exposure sits.
- Unwritten dismissals, a reviewer clears a potential hit and records nothing about why, leaving a decision that cannot be defended or repeated.
Each of these is a data and placement problem rather than a judgement problem. The reviewer who cleared the hit usually had good reasons. Those reasons simply never reached a record anyone could find later, and the counterparty identity used for the screen never reconciled with the identity on the signed agreement.
Screening the trading name on an intake form while signing with a differently named subsidiary is a common and expensive mismatch. The screened identity and the contracting identity have to be the same record, with the same registration number, before the result means anything. A contract metadata model that masters counterparty identity once removes most of this class of error.
What a working screening control looks like
A control that holds up has a trigger, an identity, a result and a repeat. Those four elements turn screening from a report into something an obligation register can manage, which is the same mechanism used for any other recurring contractual duty.
- Trigger at intake, before party creation. No counterparty record is created, and no requisition or order form proceeds, until an initial screen has returned and been recorded against the proposed legal entity.
- One mastered counterparty identity. The legal name, registration number, country of incorporation, registered address and ultimate parent are held once and reused, so screening, contracting and payment all point at the same entity
- A second screen at execution. Weeks often separate intake from signature. A confirmation screen at execution closes that window and is cheap to run when identity is already structured.
- Scheduled re-screening with an owner. Re-screening is an obligation with a frequency, a named owner and an escalation path, sitting on the contract record alongside insurance certificates and reporting duties.
- Evidence that travels with the agreement. Result, list version, date, matched identifiers and reviewer are stored on the contract, so producing the file is a query rather than a reconstruction exercise.
A five-step roadmap for putting screening on the contract record
Step 1, map where counterparties enter
List every route a new counterparty can take into the business, including procurement intake, sales order forms, legal entity onboarding, grant and sponsorship processes, and acquired contract populations. Most organisations find at least two routes that bypass screening entirely because they were never considered contracting channels.
Step 2, fix counterparty identity first
Screening quality is capped by identity quality. Normalise legal names, attach registration numbers and addresses, resolve duplicates into a single record and capture the ultimate parent. This work pays for itself twice, once in screening precision and once in spend and risk reporting.
Step 3, define the clause set
Agree standard language for the restricted-party representation, the ongoing notification covenant, the subcontractor flow-down and the immediate suspension right. Put it in the clause library with guidance on what may be negotiated and what may not, so reviewers are not drafting it fresh each time.
Step 4, instrument the obligation
Create re-screening as a tracked obligation with a frequency that reflects risk, an owner by role rather than by person, a due date and an escalation path. Tie the schedule to the live contract population so terminations stop generating work and new agreements inherit it automatically.
Step 5, close the loop on hits
Write down the dismissal standard before you need it. Who may clear a weak match, what evidence they must record, when a hit escalates to legal or compliance, and what happens to performance and payment while a hit is open. A documented standard is what makes a cleared hit defensible a year later.
See screening as a tracked contract obligation
Aavenir holds counterparty identity, screening results and re-screening schedules on the agreement record, with owners, due dates and evidence in one place.
What changes when screening sits on the contract
The practical difference is retrieval time. Teams that hold screening results on the contract record answer regulator and auditor questions from the agreement itself, in minutes, with the list version and reviewer attached. Teams that hold results in a separate platform spend days reconciling identifiers before they can answer at all. The underlying screening is identical; the evidence architecture is not. A second difference shows up in coverage, because re-screening tied to the live contract population does not quietly drift out of date as agreements are signed and terminated.
Placing the control, point by point
The table below sets out where each screening action belongs, who should own it and what evidence it has to leave behind. The pattern is deliberately conservative: each step is cheap, and the cost of skipping one shows up only when it is too late to fix.
| Lifecycle point | Screening action | Owner | Evidence recorded |
|---|---|---|---|
| Intake, before party creation | Initial screen on proposed legal entity | Contract operations | Result, list version, date, identifiers used |
| Review and negotiation | Confirm restricted-party clause set is present | Legal reviewer | Clause variant and any approved deviation |
| Execution | Confirmation screen on the signing entity | Contract operations | Second result with signatory entity reference |
| Active term | Scheduled re-screen at risk-based frequency | Named obligation owner | Dated result per cycle, hits and dismissals |
| Designation or hit | Suspension decision and notification | Compliance with legal | Decision memo, actions taken, timestamps |
Screening is not difficult work. It becomes difficult when the result has nowhere to live, the counterparty identity cannot be matched, and the schedule depends on somebody remembering. Putting the trigger in the contract workflow and the evidence on the contract record removes all three problems at once, and it does so without changing the list sources or the reviewers already doing the judgement work. For organisations running third-party risk contract automation already, screening is one more obligation on a register that exists, and the marginal cost of adding it is small.
For related guidance, see How to build a clause library your legal team trusts, When the order form and the MSA disagree and Proving an obligation was actually met.
