What business context makes an evidence task useful for agent development?

Use this checklist to decide whether a generated evidence task represents the business context an agent must understand before assembling records into a reviewable package.

- Include batch activity where one reconciliation supports several cases, requiring the agent to identify the relevant portion without claiming exclusive ownership. - Represent shared resources, such as a shift register, whose entries acquire meaning only when connected to the affected service or transaction. - Distinguish routine processing from exception handling so the agent can explain why different cases require different supporting material. - Preserve operational abbreviations alongside defined meanings, allowing the agent to interpret local terminology without inventing a new process requirement. - Include cancelled work that leaves records behind, so an agent does not mistake every recorded action for a completed business outcome. - Show the reviewer's intended decision, such as accepting a control explanation, so evidence selection serves a concrete question rather than general summarisation. - Retain workload context when it explains record structure, such as consolidated daily logs, without treating workload as permission to ignore obligations.