Which case variations should a generated policy-transition dataset contain?

Use this checklist to request variation across the lifecycle positions that a policy change can encounter.

- Work created after the new rule begins. - Open work awaiting its first assessment. - Work with a completed but unused approval. - Dormant work resumed after the change. - Closed work reopened for a new decision. - Records imported through an older intake channel. - Linked cases with different lifecycle positions.

Each cohort should have a reason for inclusion. Dormant work tests whether resumption triggers a fresh applicability check. Reopened work tests whether the new decision inherits the original treatment or starts a new policy obligation. An older intake channel can omit fields introduced by the revised rule, creating a data-completion task before assessment can proceed.

Ask for the cohort labels to remain separate from the agent's ordinary operational view when they would reveal the answer. Developers can use them for coverage analysis without making them shortcuts during evaluation.

MirrorFirm could generate these variations within one coherent business process. The resulting dataset can expose uneven behaviour across lifecycle states that an overall completion score would otherwise hide.