What is Policy versioning?
Technology
Policy versioning is the practice of storing every change to a credit policy as an identifiable version — with author, date and reason — and being able to tell which one was live at any point in time. It makes policies comparable, revertible and auditable without ambiguity.
Why saving is not enough
Editing a policy in place destroys its history. With versioning, any past decision can be reconstructed with the policy that actually produced it — essential for audit and for controlling change between test and production environments.
Related terms
Batch processing
Batch processing evaluates many cases at once against a policy, instead of answering application by application. It is used to re-score a portfolio, build pre-approved campaigns and test a new policy on historical volume.
Decision engine
A decision engine is software that automates credit application assessment by applying business rules, scoring models and external data to return a decision — approve, decline or refer — in milliseconds. Unlike custom-built code, it lets the risk team configure and change policies without engineering involvement.
Decision tree
A decision tree is the visual representation of a credit policy as a sequence of conditions (if/then) leading to an outcome. In a no-code engine it is built by dragging blocks, which lets business and risk teams design and read the logic without writing code.
Back to the full glossary.
Want to see it in your operation?
We review how you decide today and show you how it would work in the engine, with your own sources and policies.