Assistant Output Verification Gate (QA)

Assistant Output Verification Gate (QA)

1. 01

   Spot-check every assistant-drafted client email against the source thread before it leaves the agency

   Pull the original thread and confirm names, dates, and quoted figures match. A calendar secretary that reads scheduling threads can propose a time the client never offered, and the error only surfaces when the client replies.

2. 02

   Reconcile assistant-generated meeting notes with the recording transcript

   Assign one person per client account to compare the summary against the transcript for scope changes, budget mentions, and verbal approvals. Notes that drop a retainer increase become a billing dispute three weeks later.

3. 03

   Test recall queries against known facts before trusting the assistant's memory layer

   Ask the assistant for a specific past commitment, such as the rate quoted to a named client, and verify the answer against the CRM. On-device memory tools index screen content and inboxes, so a stale draft can be retrieved as if it were sent.

4. 04

   Flag any assistant action that touches client money, contracts, or public channels for human sign-off

   Drafting is safe to automate; sending, publishing, and invoicing are not. Route those outputs to a named approver and log who cleared them.

5. 05

   Run a weekly sample of 10 assistant outputs per active retainer and score accuracy on a three-point scale

   Correct, correctable, or wrong. Track the ratio week over week; a rising correctable share means the context layer is drifting and needs a re-index or a scope reset.

6. 06

   Log every correction in a shared error register with the assistant, the task type, and the failure mode

   Patterns emerge fast: scheduling assistants misread timezone shorthand, inbox assistants over-apply custom rules. The register becomes the input for the next context boundary review.

7. 07

   Confirm the assistant's data boundary still matches the client's contract before the next reporting cycle

   Check that no client data moved to a cloud service the client did not approve. On-device tools keep transcripts and inboxes local, which is a selling point only if the deployment actually stays local.