An evidence-organizing example
This fictional scenario shows an expected work product, not a deployed system or an auditor's conclusion. The task is to prepare a source-linked response pack for an authorized reviewer. It does not determine audit sufficiency or approve disclosure.
The request and source register
REQ-EX-03 asks for the approved procedure and evidence that the September operating review was signed off. DOC-A is the current approved procedure, accessible to the preparation team. DOC-B is September's review record, with the sign-off field blank. DOC-C is an August review record. DOC-D belongs to another entity and is outside the team's permitted access.
The expected evidence index
Approved procedure: DOC-A, available for reviewer assessment. September review: DOC-B, record located but sign-off not evidenced. August record: DOC-C, outside the requested period. No evidence from another entity should be retrieved or included.
Draft internal handoff: The approved procedure is ready for your review. The September record is present, but its sign-off field is blank. Please confirm the correct approval evidence or record the gap before responding.
Each included document should retain its identifier, version, period and permitted location. The reviewer decides whether it answers the request and whether it may be sent.
Test the uncomfortable cases
Change the period on DOC-C to resemble September: the workflow must check the actual record, not rely only on the filename. Withdraw permission to DOC-A: retrieval must fail safely. Add an unsupported assertion that the review was approved: the response must still identify the missing evidence.
Test cross-entity permissions in an isolated environment with deliberately separate synthetic records. A text instruction telling the assistant to ignore another entity is not a substitute for access enforcement.
What to measure
Record search, preparation, review and correction effort, the number of requests reopened, source mismatches and any attempted unauthorized retrieval. Preserve the evidence needed to investigate a failed test.
The useful decision is whether a bounded retrieval-and-preparation workflow deserves further assessment. This example makes no claim about audit approval, regulatory compliance or financial savings.
Save this illustrative pack
The text download contains the sample inputs, expected output and exception checks described above. It contains no client information.