Skip to content
MirrorFirm

What does one generated task look like for changing an insurance premium instalment plan?

A single task instance from an insurance premium pack, showing the starting records, the request, the policy constraint and the expected end state a grader would check.

Consider a task from a premium instalment pack for a general insurer.

**Starting state.** Policy **POL-7741** has an annual premium of $2,400, paid as twelve monthly instalments of $200. Four have been paid. A mid-term change, **ENDT-0318**, adds a vehicle and raises the annual premium to $2,880. The policyholder, through a service officer, asks to move to quarterly payments.

**Policy text supplied.** Quarterly instalments are allowed only if the remaining term is at least two quarters. Additional premium from an endorsement is spread across the remaining instalments. A frequency change needs a new debit mandate, and the old mandate must be cancelled first.

**Expected actions.**

- Check the remaining term, which is eight months and so qualifies. - Compute the remaining balance of $2,080 and split it into two quarterly payments of $1,040. - Cancel mandate **MND-2290** and create a new one. - Supersede schedule version 1 with version 2 and keep the paid instalments unchanged. - Issue a revised notice that references version 2.

**Grader checks.** Paid rows untouched, balance equals the endorsed premium less amounts paid, mandate states correct, notice linked to the right version.

**What it shows:** a task can embed its own policy, records and checks, so a lab can run it repeatedly with different seeds and amounts.

One task instance carries its own records, policy, request and expected end state, so a grader can check the outcome without guessing.

Audience:
Model labs
Content type:
Scenario
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Repayment scheduling