Which record types should I request in an escalation sample?

Use this list to decide what a first sample should contain, and drop items that do not suit your training or evaluation purpose.

- Request or application records with amount, type and status history - Authority matrix with roles, limits and effective dates - Policy text with exception categories linked to reason codes - Referral events with from-role, to-role and trigger - Handover notes of varying quality, including thin and thorough ones - Decisions with outcome, conditions and the decider's role - Follow-up tasks created by conditions or returns - Linked-party or facility groupings that change combined exposure

Ask that every record carries a stable identifier and that foreign keys resolve inside the sample. A sample where a referral points to an application that is not present limits what you can test.

Also ask for a short data dictionary describing each field, so your team can map the fields to your own schema before deciding on scope. Because the material is generated, request a note on how cases were constructed, so you can judge grounding and spot patterns that look too regular.

If the sample is for evaluation rather than training, add gold end states per case so a grader has something to compare against.