Skip to content
MirrorFirm

Can a release include policy rules and exceptions, not just records?

Yes, a release can carry versioned policy records, edge-case exceptions and tasks where the right answer is to refuse or escalate, though the policies are generated rather than copied from any real firm.

**Can a release include policy rules and exceptions, not just records?**

Yes. A buyer can ask for policy to be part of the state, so that the correct action depends on it.

Types of rule a release can contain:

- **Limits:** the number of deferrals allowed, the longest permitted extension, the smallest instalment. - **Thresholds:** amounts or plan lengths above which an approval is needed, and by which role. - **Timing rules:** cut-off times, grace periods and blackout dates. - **Versioning:** rules with effective dates, so a plan created under an older version is judged by that version.

Exceptions can be modelled too. Examples include a hardship flag that relaxes a limit, a dispute marker that freezes a plan, or a customer who has already used their one free change.

Task packs can then include cases where the best outcome is to decline, ask for approval or hand over to another role, with the expected action stated in the grading rule.

Two limits apply. The policies are generated, so they reflect plausible practice and not the rulebook of any particular organisation. And rules that conflict with each other need to be scoped deliberately, because ambiguity helps testing only when the expected answer is defined.

Policies and exceptions turn a data dump into a testable environment, because the correct action depends on which rule applies.

Audience:
Environment builders
Content type:
FAQ
Buyer question:
What can be generated

Content release: r-a220eb6e099b243b

More on Repayment scheduling