These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Credit Scoring Engine
- Features
- Decision review
Decision review
Keep independent decisions and reason codes tied to the reviewed revision.
OverviewAuthorized applications×
Credit Scoring Engine · Decision review
New
Authorized applications
Pickup waits for the operations manager
| Record number | Applicant | Requested amount | Revision | Status | |
|---|---|---|---|---|---|
| APP-28378 | APP-4918 | 30 | 440 | Authorized | |
| APP-30774 | APP-3937 | 810 | 880 | Authorized | |
| APP-27103 | APP-3470 | 210 | 770 | Authorized | |
| APP-77043 | APP-8952 | 750 | 130 | Authorized | |
| APP-64711 | APP-4742 | 50 | 160 | Authorized |
6 of 6 records
APP-4918Applications · APP-28378
AuthorizedRequested amount30
Revision440
What you can do
Decide against a known revision
Credit Reviewer examines a submitted application and records the outcome in a separate decision record. The decision identifies the application revision, reviewer, time, reason codes and operation key. This separates the reviewer’s judgment from the preparer’s changing work. It also gives Auditor a way to answer which version was considered and who made the decision.
Suppose an Operations Manager submits an application for a requested amount, then notices a correction. The reviewer should see the updated revision before deciding. A decision tied to the earlier revision should not silently authorize the changed request. The case history should make the correction and the later decision understandable without relying on a freeform comment alone.
How the work is organized
- Submission. Applications carries the case status and revision that reaches review.
- Decision. credit decisions records approve, decline or refer with a reviewer and reasons.
- Evidence. record attachments and assessment evidence keep supporting material and provider events near the case.
What to agree during setup
Name the people permitted to prepare and review applications. Keep the independent reviewer separate from the submitter. Agree how reason codes will be written consistently enough to compare decisions across cases. Decide what happens to a referred case: who receives it, which revision changes, and how the reviewer sees the corrected material. Define a clear route for a decline and for any later new application from the same applicant.
An approval decision is still distinct from provider execution and confirmation. The team should not mark a case confirmed simply because the reviewer approves it. Establish who records provider evidence, who checks it, and how the instruction identifier is associated with the application. Use the decision time and reviewer identity during a later audit of the case.
Check the handoff on an actual case
Prepare a submitted application with a supporting attachment. Have a Credit Reviewer who did not prepare it compare the amount, purpose, applicant and revision. Record an approval with reasons, then inspect the decision history from the application. Repeat with a referred application and a changed revision. Confirm that the new reviewer decision identifies the new revision while the earlier decision remains visible.
What your team sees
- Submitted decision inbox. Review submitted applications ready for a decision.
- Decision history. Read the recorded outcome, reviewer, reasons and revision.
- Authorized applications. Find approved cases awaiting provider follow-up.
Follow the work through
What it keeps track of
Data model- Applications
- Credit applications moving through authorization, submission and confirmation.
- Credit decisions
- Independent reviewer decisions recorded against a frozen application revision.
- People
- Preparers, approvers, auditors and administrators working in the organization.
- Record attachments
- Supporting documents attached to an application.
- Assessment evidence
- Provider statements, confirmations, settlement notices and corrections for an application.
Who uses it
Permissions- Credit Reviewer
- Owns the independent decision.
- Operations Manager
- Prepares the case and responds to referrals.
- Auditor
- Inspects the decision trail; App Administrator maintains access setup.
Set up Credit Scoring Engine your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.