Derives human-readable manual test cases from a business-rule spec via a decision table: identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column (each feasible column is one coverage item per ISTQB CTFL v4.0 section 4.2.3). A deep single-technique walkthrough rather than a broad multi-lens case matrix; the output is manual step/expected cases rather than parameterized test code, and it covers how cases are derived rather than how a case record is structured. Use when a spec's outcome depends on interacting conditions (pricing, eligibility, discounts, routing rules) rather than the boundaries of a single input.
93
93%
Does it follow best practices?
Impact
94%
1.02xAverage score across 10 eval scenarios
Passed
No findings from the security scan
Motor claims arrive through the web form and are routed automatically. The ops note below is what the routing was built from. It reads as four independent statements, and the statements overlap: last week a EUR 4,000 claim on a policy opened five weeks ago went to the adjuster, and fraud review escalated it because they say it was theirs.
There is a second problem. The claim form only renders the police-report upload above a certain claim value, so some of the states this note describes cannot actually be produced by a customer. Our tester wasted an afternoon trying to set one of them up before someone told him.
I need one document for the triage review. It should say what every possible state of the inputs does, which states our tester genuinely cannot reproduce, and which ones the note fails to settle.
Produce claim-routing-analysis.md containing:
Out of scope: the adjuster's internal workflow, the fraud scoring model, and any code change. This is a review document only.
Extract the following files before beginning.
=============== FILE: docs/claim-triage-note.md ===============
A claim is approved automatically when all of these hold: the claim amount is EUR 1,000 or less, the policy has been active for six months or more, and at least one damage photo is attached.
A small claim on an established policy with no photo attached is held, and the customer is emailed to ask for a photo.
Claims above EUR 1,000 go to a human adjuster.
Claims on a policy that has been active for less than six months go to fraud review.
Photos are advisory for an adjuster - the adjuster opens the file either way, and their presence or absence changes nothing about the adjuster's handling.
The police-report upload appears on the claim form only for claims above EUR 1,000. Below that the field is not rendered at all, so a small claim never arrives carrying a report.
Where a police report is attached, the adjuster is expected to close the claim within two working days instead of the usual five.