Your credit policy becomes the decision flow that runs

Your credit policy lives in a PDF or spreadsheet. Decisimo's assistant proposes its decision flow, and your risk team accepts each part before applying it. The team can then change the policy that runs in the portal.

Book a demo Build from your policy

Build the decision flow from your policy document

Upload your credit policy as a PDF or spreadsheet. The assistant proposes the decision flow, and your risk team accepts or rejects each step. Nothing is applied until the team applies the plan.

Proposed plan lists Application Knock-Out Rules and Product Interest Rate Pricing with accept or reject controls
The plan shows the decision flow the assistant made from an uploaded credit policy. Your risk team keeps or drops each step on its own before anything is built.

Keep the policy document as the reference

The policy document stays in the portal, with each requirement citing its place in the document. Select a requirement to highlight the passage in the PDF. A release check returns a verdict for each requirement, and a requirement counts as met only when it was judged. See what regulators ask lenders to evidence.

Change the policy, compare its effect, then deploy

Edits in the portal create revisions you can compare side by side or revert. The impact analyzer reports which past decisions would change, and saved test cases run again as regression tests. Nothing runs until a release is deployed to an endpoint. When the endpoint has an approval sequence, that sequence must be signed first.

Decision table revision comparison shows original #2 and modified #3, with added and changed rows highlighted
The screen compares two revisions of the Leasing terms decision table. The risk team can see exactly which rows the change touched before it runs.

Read why a test decision came out as it did

A test run shows the scorecard bin and contribution for each value, then the decision table row that fired and the reason it wrote. The fired row also shows the values used for the decision, including the debt-to-income ratio and score.

Execution details show a 660 score and credit_policy row 2 declining at 0.541 DTI above the 0.5 limit
The test run shows a scorecard breakdown ending at 660 and the fired credit_policy row. Its debt-to-income ratio is 0.54, above the row's 0.5 limit.

Questions we get asked

Can the assistant change my credit policy on its own?

The assistant proposes a decision flow for your team to review. Each step is accepted or rejected separately, and only accepted steps are built when you apply the plan.

Which file formats can I use for my credit policy?

Upload the policy as a PDF or spreadsheet. The assistant uses it to propose the decision flow.

How do I test a policy change before it runs?

Compare the revised policy with the earlier revision and run saved test cases again as regression tests. The impact analyzer also reports which past decisions would change. The release runs through an endpoint only after deployment.

How do I get started with credit policy management?

Start with your prepared policy document and review the proposed decision flow with your team. Follow the introduction guide.

Can I compare two policy revisions?

The portal compares two revisions of an artifact side by side, and a revision can be reverted. Two releases can also be compared.

Put your credit policy into practice

Book a demo to review how your policy can become a decision flow.

Book a demo