Agentic AI
Four-eyes review: what happens when the checker challenges the recommendation?
A second reviewer should be able to question a recommendation, see the answer and decide whether it is sufficient. This cmpliance walkthrough follows that exchange into the evidence pack.
Two names beside an approval tell you who reviewed it. Can your record also show what the second person questioned and how the first person answered?
youtubeThe maker answers a checker's challenge through a new recommendation. The checker approves the case, then an administrator seals the evidence pack.https://www.youtube.com/watch?v=uN25qbw7BFUWatch: Four eyes, one accountable decision
A customer is ready for a decision. One officer has reviewed the case and recommends approval. A second officer reads the recommendation and asks a question that must be answered before proceeding.
The recorded sequence includes the recommendation, the checker's challenge, the answer in a new recommendation and the checker's eventual approval. The people responsible remain attached to their actions, giving a later reviewer more to examine than the final status.
A recommendation gives the checker something to examine
At 0:19, the maker records a recommendation. Here, the maker is the officer proposing how the case should be decided; the checker is the second officer reviewing that proposal.
A recommendation is a position that another person can examine. It should explain why the evidence supports the proposed outcome, including any limits that matter to that judgment. An approval button alone cannot convey that reasoning.
Preparing findings for review does not give an agent authority to approve the customer. Nor does the maker's recommendation stand in for the checker's decision. In the sequence shown, those are separate human actions.
Our article on KYC evidence review beyond name screening explains the wider evidence questions behind a review. This video takes one narrower question: what happens when the next officer is not yet satisfied?
The challenge needs to survive the answer
The checker challenges the recommendation at 1:00. The case returns to the officer, who answers in a new recommendation from 1:53.
Preserving both versions matters. If the first recommendation disappears, the file loses the starting point. If the challenge disappears, the revised rationale can look like something the maker had concluded all along. A later reader cannot tell what the second review contributed. In this case, the original recommendation and return remain in the history alongside the new recommendation.
The checker still needs to assess the answer. Receiving a response does not, by itself, resolve the question.
Not every second review needs disagreement. A checker may agree with a well-supported recommendation. But when a material question is raised, the question and its treatment belong in the decision record. They should not depend on the participants remembering a call or finding an old message.
Approval and sealing are different actions
At 2:38, the checker reaches the decision. A customer administrator subsequently seals the evidence pack, shown from 3:22. The checker then downloads it and opens the decision trail.
Keep those roles distinct when reading the recording. The maker recommends. The checker challenges and later approves. The administrator seals the pack. Sealing the record is not another person's substitute for the compliance decision.
The decision-trail section near the end brings the exchange into the exported record. That is what makes the hand-off useful beyond the immediate team: the question that delayed approval remains part of the explanation for the eventual outcome.
This is the practical connection to an audit-ready evidence pack. The pack needs more than the final disposition. It needs the relevant review history that explains how the people involved reached it.
Test a challenged case in your own process
Choose a completed case in which a checker returned the recommendation. Ask a colleague who was not involved to identify what the maker originally proposed, what the checker questioned, what changed in the new recommendation and who accepted the answer.
Then check whether the exported record tells the same story as the live case. If the reader needs an oral explanation, identify the missing part rather than adding a vague statement that a second review occurred.
Why it matters for your team
Agents prepare a case for the officer's judgment. cmpliance preserves what happens when that judgment is challenged: who questioned what, who answered and who decided. The original recommendation, return and revised recommendation let another reviewer see what changed before approval.
See how cmpliance works and what makes an evidence pack audit-ready. Talk to us about keeping a challenged recommendation, its answer and the final decision together.
Agents do the work. Humans make the call.
Keep the maker's recommendation separate from the checker's decision.
Preserve a material challenge and the answer alongside the original and revised recommendations.
Record approval and evidence-pack sealing as distinct actions by the people who performed them.
Frequently asked questions
→Does four-eyes review require the checker to disagree?
No. A checker can agree with a supported recommendation. When a material challenge occurs, the record should preserve what was questioned and how the answer was assessed.
→Who approves the customer in this walkthrough?
The checker approves after the maker responds through a new recommendation. A customer administrator later seals the evidence pack. The recording does not treat sealing as the approval decision.
→Where is the review exchange preserved?
The downloaded evidence pack includes the decision trail: the recommendation, the checker's challenge, the answer and the approval, attributed to the people who made them.
