What should an evaluation team request in a generated set-up task pack?
A checklist of the contents worth asking for, from decision records and policies to expected end states and reset instructions.
Use this list when asking for a task pack or environment so the sample can be judged against concrete contents.
- Decision records with outcomes, conditions, approver roles and dates. - Party records including near-duplicates and variant spellings. - Target records such as accounts, services or contracts, in more than one starting status. - Document and check records with received, verified, expired and missing states. - Written policies and decision tables that govern activation and waivers. - Handover tasks and notice templates tied to named roles. - An expected end state for every case, including cases where the right outcome is to hold. - Seed and reset instructions so any case can be rerun from the same starting state.
Also ask which parts are generated from a template and which vary freely, since that affects how much variety you are really testing.
The material is generated, synthetic output and not real business records. Ask how it is grounded, and inspect it for disclosure risk before you use it.
Naming the contents up front makes a sample easier to judge and a pilot easier to scope.
- Audience:
- Evaluation teams
- Content type:
- Checklist
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- Can a simulated environment include tool errors and incomplete approvals?
- What does a generated task with a seeded fault look like for policy issue?
- What file formats, schemas and tool actions can a set-up release use?
- What records, relationships and policies can a generated set-up release contain?
- What should a buyer specify when requesting a generated set-up release?
- What should I specify about environment state before requesting a release?