Which record types should an environment builder ask for in an escalation release?

Environment teams can use this list when describing what an escalation release should contain.

- **Authority rules** by role, product, amount band and grade, with effective dates so version questions can be tested. - **Cases** with amounts, grades, parties and a full status history, including states beyond the happy path. - **Evidence items** linked to each case, with some deliberately missing or stale. - **Escalation and response records** carrying reason codes, target roles and outcomes such as approve, amend, decline and return. - **Delegation and roster records** showing who is absent and who covers. - **Audit events** with actor, role, action and timestamp, since many graders read these rather than the final case row. - **Related-case links** through shared parties or events, so splitting and aggregation can be detected. - **Task definitions** with a start state, goal, permitted tools and expected end-state checks.

Also ask for a data dictionary and a statement of which fields are generated from rules and which are free text. That makes it easier to see where a grader can rely on structure and where it must interpret prose.

Scope the domain, such as lending, claims or utilities, so field names and policies feel coherent.