What records and relationships can a sufficiency dataset contain?

A generated release for this workflow can include the following record families, informed by how real businesses structure the work.

**Cases** carry a type, an opening point, a current status and a history of status changes. Statuses such as `assessment`, `awaiting-documents`, `ready-to-proceed` and `withdrawn` give the workflow its shape.

**Documents** carry a type, an issue date, a stated period, a quality flag and content. The flags can mark a document as expired, unsigned, partial or mismatched to the applicant.

**Policy rules** state which document types a case type needs, how recent they must be, and which alternatives are acceptable. Rules can be versioned so that a case is judged against the version in force at the time.

**Assessments** record the verdict per document and overall, with a rationale that cites rule identifiers.

**Requests** record the items asked for, the wording, the response-by point and what happens at lapse.

The relationships matter more than the individual tables. An assessment points to rules and documents. A request points to the assessment gaps that caused it. A resubmission points to the request it answers.

For a reseller, those links are what you can describe to customers as inspectable. Ask for them to be present in a sample, and check them before listing.