The recurring cost in this category is usually not the licence. It is the quotation that arrives when you want a number moved from 14 days to 21.
What it does
Thresholds. The logic of a rule, built in a form rather than written in code. What an action is called. The questions an officer must answer before completing one. Which rules run automatically and which wait for a person. Who can see which page.
Change a number and your cases re-evaluate immediately, on your data, not on our next release.
A threshold shared by several rules says which rules read it. Turning a rule over to automated email names the open cases it will pick up and asks you to confirm. Nothing about “configurable” should mean “you find out on Monday”.
Who moved which threshold, from what to what, when, and how many cases it moved. That record is what lets configuration sit with your own team rather than with one person — and it answers an auditor asking who decided.
A statutory hold, the six-year limitation clock and an unread access need are not thresholds you can set to zero. They sit under your rules rather than beside them, so a configuration mistake cannot switch off a legal duty.
Nothing prioritises a tenant by a model you cannot inspect. Where a model is used at all it drafts for a person; it does not decide. That is an increasingly awkward question to answer with a system whose weightings the vendor treats as commercially confidential.
Where this stops
The product tells you what a change will move and records who made it. It will not tell you that 21 days is the right answer for your tenants.
Housing Act 1988 Grounds 10 and 11 carry no threshold in law. Any figure you use for them is policy, not statute.
Rebuilding an incumbent's rule set in readable form is work, and it is work we do with you rather than something that happens on import.
Tell us about your organisation and what you are trying to fix. It goes straight to the team, and a person replies.