Skip to content
MirrorFirm

What acceptance checks should we run on an intake sample before listing it?

Eight acceptance checks covering state transitions, rule conformance, exception coverage, leakage, template echo, split hygiene, disclosure scanning and record keeping.

Run these checks on any intake sample before you list it or pass it to a customer.

- Check that every case follows legal state transitions, with no routing before receipt and no closure without a decision. - Join each routing decision to its cited policy rule and confirm the recorded queue matches, or is flagged as an override. - Confirm that exceptions such as duplicates, reopens and escalations appear, and that each carries a reason code. - Search free text for leaked labels, such as queue names or outcomes appearing in notes or file names. - Cluster free text to find template echo, where a small set of phrasings repeats across many cases. - Verify that all events for a case sit in a single training or test split. - Scan for distinctive strings or combinations that could point to a real person or business. - Record the checks, thresholds and results against the release identifier before listing.

A fixed set of acceptance checks, recorded against the release identifier, gives you evidence of what you inspected before onward licensing.

Audience:
Licensed resellers
Content type:
Checklist
Buyer question:
How to evaluate it

Content release: r-a220eb6e099b243b

More on Application intake