What evidence artefacts should accompany a generated change request?

Use this checklist to specify the evidence surrounding a request, rather than supplying an isolated instruction with no basis for interpretation.

- Include the original request text and channel metadata. - Link attachments to the request they support. - Mark documents that a later submission supersedes. - Record which claims each document supports. - Represent missing or unreadable evidence explicitly. - Include case notes with their authoring roles. - Link the final decision to the evidence used.

For a logistics customer changing site access arrangements, the bundle can contain an updated loading instruction, a site diagram and a note that an earlier entrance is closed. A missing diagram page can leave vehicle clearance unresolved even when the delivery address is complete.

The generated package can preserve this gap instead of silently supplying an answer. That gives the agent a reason to request the specific missing evidence and allows a reviewer to understand why the change remains incomplete. Buyers can also inspect whether generated supporting documents agree with the structured records and whether their grounding introduces disclosure risk.