Guide
How should an AI agent flag missing information in a summary?
Distinguish confirmed information, details not found, and sources not reviewed in an AI summary, with checkable references and human review.
By AIKUB ·
“The client has no objections” and “no objection was found in the reviewed documents” do not mean the same thing. When scoping a summary prepared by an AI agent, require confirmed facts, information not found, and sources not reviewed to remain distinct. This guide proposes a review record and tests that make those limits visible before a person uses the summary.
What does information not found mean?
Define acceptable wording before delegating preparation. “Confirmed” should point to an explicit passage in an authorized source. “Not found in the reviewed sources” describes the outcome of a limited search. “Not verified” indicates that an expected check could not be completed. None of these states should automatically become a negative answer or an approval.
Fictional example: a firm prepares a summary before a client meeting. Available notes mention no objection, but an expected attachment has not been reviewed. The summary should state that limitation rather than describe the client as satisfied or the case as approved. This is a scoping scenario, not an observed client result.
How should the reading scope be defined?
Specify the case, period, expected document types, and sources the agent may review. Separate the expected list from the list actually read. Flag a missing, inaccessible, or unreadable attachment with a useful reference, without claiming its contents were examined. Do not ask the agent to search unauthorized spaces to fill the gap.
For each important point, require a reference the reviewer can locate: document, relevant version or date, and page or section when available. A reference must support the claim it accompanies. If two sources disagree, flag a separate conflict; do not classify it as merely missing information.
What should the summary record contain?
Use a short structure: summary purpose, scope actually reviewed, facts with references, details not found, sources not reviewed, and questions requiring verification. In the meeting example, the objections field can state: “Not found in the reviewed notes; case attachment not examined.” The reader can see what remains open without guessing.
Also distinguish a reported statement from an approved decision. “The client requests a change” does not mean “the change is approved.” The responsible person decides whether the summary is sufficient to prepare the meeting or needs further checking. Preparing a summary does not authorize external distribution or a change to the client’s status.
How can the summary’s limits be tested?
Prepare anonymized cases with expected answers: an explicitly stated fact, an explicit negative answer, a subject never discussed, and an expected attachment that cannot be accessed. Add a passage reporting a request without approving it. Check that these situations produce different wording and that each confirmed fact has a relevant reference.
The reviewer should also look for important omissions, not only incorrect sentences. Compare the summary with the required points and sources actually reviewed. Record discrepancies, adjust the scope, and repeat tests before expanding use. A cautionary instruction alone is not an accuracy guarantee; retain human review appropriate to the intended use.
How can you prepare this use case with AIKUB?
Bring a type of summary your team prepares regularly, an anonymized case, and the questions its reader needs to answer to a diagnostic. Identify permitted sources, information to exclude, and the person who checks the result. The first assignment can remain limited to an internal draft accompanied by its review record.
AIKUB supports the scoping of personalized, governed agents, with support and training included. Find your first quick win in repetitive computer-based preparation while keeping the limits of available information visible. The diagnostic defines what the summary should explain, what it must not conclude, and when a human needs to complete the check.
Frequently asked questions
Does not found mean the information does not exist?
No. That wording must remain tied to the sources and scope actually reviewed. It does not establish absence across the entire case or every tool.
What should happen with an inaccessible attachment?
Flag that it was not reviewed and have the responsible person assess its importance. Do not claim to summarize it or bypass access limits.
Can a summary confirm an approval?
It can report an explicit approval with its reference, within the assignment’s scope. Silence in a source or a change request is not approval, and the summary grants no new authority to act.