Versioned rules engine
A versioned, date-effective rules engine keeps policy values such as allowances, payout rates, wage limits and required documents outside the code. Administrators add a new version with a start date, older cases keep the rules that applied to them, and nothing needs a software release.
See the PERKESO case studyWhat it does
Versions with start dates
Each policy change is a new version that takes effect on its own date.
History preserved
Past cases are always judged by the rules that applied at the time.
No release needed
Administrators change values without waiting for developers.
Common questions
What is a date-effective rules engine?
It stores policy values as versions with start dates, so the system always applies the version that was in force for each case.
Why do policy changes need effective dates?
Because cases are judged by the rules in force when they happened. Effective dates keep old and new cases correct at the same time.
Who can change the rules?
Authorised administrators, with every change recorded.
Have a process you want to automate?
Tell us how the work runs today. We will reply with the next step and a quote in RM.