Agentic AI
An adverse-media item lands on your desk. What happens next in cmpliance?
An adverse-media item needs more than a headline. Follow the officer in cmpliance from the source record to an information request and an escalation, with the reasoning kept on the case.
The item cannot be resolved today. The officer still needs to decide what to request and who should review the concern next. This walkthrough follows those actions through to the saved case state.
youtubeAn officer reviews an adverse-media item, requests missing evidence and saves an escalation with an open request blocking sign-off.https://www.youtube.com/watch?v=ljIzcVDaM8cWatch: Reviewing an adverse-media item in cmpliance
Start with the case
The officer begins with the case, its subject and the decision being requested. At 0:08, the officer opens the subject view, then opens the adverse-media item at 0:14 in the counterparty evidence file.
Inspect the source before relying on the finding
At 0:19, the source record shows the item's URL, retrieval time and record hash. The officer can inspect those details alongside the item under review.
The officer needs to assess identity, source reliability, what is alleged, how the subject is connected and why it matters to the case. Collecting a result and judging its significance are different tasks; the judgment belongs to the officer.
Ask for the evidence that could change the assessment
At 0:25, the officer returns to the case and requests information, recording a rationale that cites the source.
The point of a request for information is to address a defined uncertainty. A broad request for more documents may produce a larger file without resolving the concern. A useful request makes clear which part of the assessment cannot yet be supported and what evidence could resolve it.
Depending on the item, that might mean distinguishing the subject from a similarly named company, establishing whether a reported relationship existed at the relevant time, or obtaining a document that corroborates or challenges the reported facts. The question determines which evidence the officer needs next.
The rationale connects the request to the work. Another reviewer should be able to understand why the information was needed and later determine whether the response answered the question. Receiving an attachment is not the same as closing the uncertainty that prompted it.
Our article on KYC evidence review beyond name screening explains the broader principle: evidence should support the claims an institution needs to rely on, and any accepted gap requires an accountable rationale. Here, the officer records the gap and requests the evidence needed to address it.
Escalation records a need for judgment
At 1:06, the officer escalates the case. Adverse media remains unresolved, and the case requires a decision from the MLRO, the money laundering reporting officer.
An escalation should carry the uncertainty forward accurately. It should not convert an unresolved allegation into a verified fact, and it should not imply that referral itself resolves the concern. The next reviewer needs to know what is available, what remains missing and why the current officer cannot complete the disposition.
That is the human judgment visible here: the officer inspects the recorded material, requests evidence and determines that the case needs further review.
Read the saved state as carefully as the action
At 1:25, the saved result shows the escalated state, a trail entry with actor and time, and an open request blocking sign-off. The MLRO route remains pending.
The next officer can pick up the reviewed item, see why more evidence was requested and read the recorded escalation. The open request remains visible alongside that work.
Why it matters for your team
Agents prepare the material for review; officers decide what evidence to request and when to escalate. cmpliance keeps those steps on the case, with the source record and request rationale available together. The next reviewer gets a defined question and the record behind it.
If your team needs a clearer handoff between an analyst's concern and the person authorised to decide, examine what the next reviewer receives: the source, the missing evidence and the reason sign-off cannot yet proceed.
Read our adverse-media screening approach, see how cmpliance works, or talk to us about the handoff your team needs.
Agents do the work. Humans make the call.
The officer can follow an adverse-media item to its source record from the case.
A reasoned information request connects the missing evidence to the concern being reviewed.
The saved escalation keeps the officer's action, its timing and the open request together for the next reviewer.
Frequently asked questions
→What can the officer inspect behind an adverse-media item?
The item opens to its source record, including the URL, retrieval time and record hash. The officer can use that context when deciding what further evidence to request.
→What happens when the officer needs more evidence?
The officer records an information request with a rationale and can escalate the case for MLRO review. In this case, the saved state keeps the open request visible and blocks sign-off.
→What does the saved trail contain?
It records the officer's action with actor and time alongside the escalated case state and the open information request.
