Can a task pack include out-of-date or conflicting policy documents?
A release can include superseded versions, conflicting references, temporary delegations and missing fields, each paired with an expected outcome that follows from the documents supplied.
Yes, a task pack could include them, and teams testing agent robustness often want them.
Typical variants a release can include:
- **Superseded policy versions**, where the older clause gives a different limit and the case date decides which applies. - **Conflicting references**, such as a procedure note that names one tier and an authority matrix that names another, with a stated precedence rule. - **Temporary delegations**, where a reviewer's limit is raised for a period and the case date falls inside or outside it. - **Missing fields**, such as an exposure link that is absent and must be requested before a routing decision.
Each variant needs an expected outcome that follows from the documents provided. If the conflict cannot be resolved, the expected outcome should be a request for clarification or a referral, not a forced decision.
This is deliberately generated content, so a buyer should inspect whether the conflicts resemble the ones their own teams face and whether the precedence rules are coherent. Incoherent conflicts produce noisy scores, because the agent is penalised for a contradiction the data creator introduced.
Ask for a sample with a stated mix of clean and conflicted cases, plus the rule that decides each conflicted case, so you can judge the design before committing to a larger pack.
Conflicted policies test robustness, but only if each conflict has a coherent precedence rule; ask to see the rule behind every conflicted case.
- Audience:
- Evaluation teams
- Content type:
- FAQ
- Buyer question:
- What can be generated
Content release: r-a220eb6e099b243b
Related questions
- Can a task pack include conflicting or outdated policy documents?
- What formats and schema do escalation datasets and task packs use?
- Which record types should I request for an escalation task pack?
- Which records and relationships can a generated escalation dataset contain?
- What would a generated utilities write-off escalation contain from start to finish?
- What linked state would a utilities hardship escalation scenario generate?