Guide
Preparing a client recap with an AI agent without sharing internal notes
Separate internal notes from the client recap: shareable content, a separate draft, attachments, and human review before distribution.
By AIKUB ยท
An agent allowed to read internal notes should not, by default, be allowed to include them in a client recap. To scope this preparation, define the intended audience, shareable information, and passages requiring a human decision. This guide proposes creating a client draft separate from working notes, then checking the text, attachments, and recipients before any authorized distribution.
What may be included in the client recap?
Start with a distribution instruction, not just a summarization instruction. Specify the client and case, who should receive the recap, and which content categories may appear. For example, the assignment may cover points discussed with the client, confirmed decisions, and questions to ask them. Internal comments and unapproved options stay outside the draft unless the owner explicitly decides otherwise.
Fictional example: after a meeting, a firm records an agreed client decision alongside an internal comment about workload allocation. The client recap should convey the decision without copying that comment. If the comment instead reveals uncertainty affecting the next step being announced, the owner must clarify the message; simply removing the sentence must not create misleading certainty. This is an illustrative scenario, not a client testimonial.
How should sources and the two outputs be separated?
Provide only the sources needed and authorized for this case. Define the expected recap sections: meeting purpose, confirmed decisions, agreed actions, and open questions. For each proposed passage, request a reference the reviewer can consult in an internal review record. That record is not part of the client document.
Plan two separate outputs: the client draft and the internal review record. The latter can explain excluded passages, ambiguities, and pending decisions within authorized access boundaries. Do not place those notes below the client text in a single message ready to forward. If a passage has no clear sharing status, keep the question in the review record and pause approval of the affected recap.
What should be checked beyond the visible text?
Review the exact deliverable intended for the client. Check the text, file name, attachments, comments, and proposed links. A draft with suitable wording should not automatically include the internal source file as an attachment. For a document link, have someone confirm that the target document and sharing access match the intended audience.
Also check recipients and copied recipients rather than deriving them from everyone named in the notes. Someone mentioned during the meeting is not necessarily a recipient of the recap. Any attachment or recipient added after review needs checking before distribution. Keep preparation separate from sending and limit the first assignment to drafts if that makes oversight easier.
How should this separation be tested before use?
Create an anonymized example containing a shareable decision, an internal comment, and a passage whose distribution still needs confirmation. Write the expected result before the test: the decision appears faithfully in the draft, the comment stays internal, and the ambiguous passage triggers a question for the owner. Also check that qualifications needed for the client to understand the situation have not disappeared.
Add a test where the client text is correct but the proposed attachment is the internal notes file. The expected result is to block that attachment, not approve the whole package based on the text. Have a responsible person review outputs and discrepancies, then repeat after correction. This review is not an automatic confidentiality guarantee; sharing and access controls also need validation in the tools used.
Where should you start with AIKUB?
Bring a client recap template, anonymized notes, and your distribution rules to a diagnostic. Identify who decides what may be shared, who reviews the final document, and which questions must block approval. The first scope can cover one meeting category, with internal preparation and no sending access.
AIKUB supports the scoping of personalized, governed agents, with support and training included. Find your first quick win in repetitive recap preparation while keeping distribution decisions under human supervision. The intended result is an audience-appropriate document with a separate internal review record, not automatic forwarding of every available note.
Frequently asked questions
Does access to the notes authorize sharing them?
No. Define readable sources separately from content that may be distributed to the intended audience. Passages without a clear rule should go to the owner before recap approval.
Should source notes be attached to the recap?
Not by default. The attachment must be part of distribution review and suitable for the recipients. A reference useful to an internal reviewer does not automatically become a shareable client attachment.
Can every qualification be removed to simplify the document?
No. Separating internal comments must not distort decisions or hide uncertainty important to the client. Have the owner clarify those passages and approve their wording before distribution.