Which records and relationships can a generated set-up dataset contain?

A generated dataset for this workflow can contain the records an operations team would touch between approval and activation, linked by stable identifiers.

**Core records**

- **Decisions or approvals**, with outcome, conditions, approver role and effective date. - **Parties**, such as customers, organisations and authorised contacts, including near-duplicates. - **Accounts, services or contracts**, with product code, terms, status and history. - **Documents and checks**, with received, verified and expired states. - **Tasks and handovers**, assigned to roles with due dates and outcomes. - **Notices**, such as welcome messages or internal alerts.

**Relationships**

A decision links to the party it concerns, the account it authorises and the conditions it imposes. Conditions link to the documents or checks that satisfy them. Tasks link back to whichever record triggered them.

**Policies**

Set-up rules can be written as structured text or decision tables: which products need which checks, who may waive a condition, and what must happen before activation.

Because the material is generated, the relationships are consistent by construction, but a buyer should inspect whether the mix of cases, exceptions and policy wording is grounded well enough for their purpose, and check for any disclosure risk.