What should we specify when asking for the contents of an intake release?

Use this list when specifying which layers an intake release should contain for your buyers.

- Applications or cases with channel, timestamps, requester details and a current state that changes over the life of the case. - Submitted items, including partial, duplicate, unreadable and contradictory ones, each linked to its parent case. - Completeness checks with pass, fail and waived outcomes, tied to a rule identifier so they can be audited. - Routing decisions with queue, reason code and the role that made the decision, including supervisor overrides. - Handover notes and follow-up requests, with generated free text where your buyers need it for language tasks. - A versioned policy file that defines completeness and queue eligibility, so outcomes can be checked against stated rules. - Task definitions with starting state, tools and reference outcomes, if your customers need evaluation rather than training only. - A manifest and schema files so that you can version the release and validate it on ingest.