Steinvar DecideDecision rulesCredit and risk rules your analysts can read.
Steinvar Decide holds the bank’s decision rules as staged rule sets written as sentences, not code. Analysts test a change in a sandbox, a second person approves it, and every evaluation is kept with the inputs and the version that produced it.
The HQ back office; the workplace and people’s names are blurred.
- Staged
- rule sets with one active version
- Sandbox
- evaluation before a version goes live
- Every
- evaluation recorded with its inputs and version
Rules
Rules as sentences
An outline and a rule sheet show each rule as a readable sentence; the expressions underneath are CEL.
Stages
Rules grouped into stages that run in order, ending in a verdict and reasons.
Sandbox
Any version can be evaluated against sample inputs before it is used.
Governance
Maker-checker
A version is drafted by one person and approved by another; one version is active at a time.
Evaluation records
Each decision is stored with its inputs, outcome, reasons and the version that produced it.
Where it is used
Loan affordability
The verdict on an application, named in the loan offer; staff can override with a reason.
KYC risk rating
The risk rating on a verification case.
How a rule change ships
Edit
An analyst changes a rule in the rule sheet.
Test
The draft is evaluated in the sandbox.
Approve
A second person approves; it becomes the active version.
Explain
Each later decision records the version and the reasons.
Controls built in.
One active version
There is never doubt about which rules decided.
Recommendation
Decisions inform a person where the process says so; overrides keep their reason.
Standards and formats
- CEL (Common Expression Language)
Not in this module today
- Credit-bureau data is not an input today; rules use the application, the customer’s accounts and their loans with the bank.
Questions about Steinvar Decide
Do analysts need to write code?
No. Rules are read and edited as sentences in a rule sheet.