Lending · Example
Consumer credit decisioning
Cadre name · Spark
Returns approve, decline, counteroffer, or refer within the illustrated credit policy.
Operating dossier
The job, permitted decisions, and owner
Mandate
Applies the supplied credit policy to credit-relevant application data, returning approve, decline, counteroffer, or refer with direct protected-basis fields withheld.
- Case arrives with
- Applicant · Product · Requested amount · Term
- Allowed outcomes
- Approve · Decline · Counteroffer · Refer
- Where it fits
- Application to Decision · Agent Assurance
Operating logic
- 01Makes the credit decision (approve, decline, counteroffer, or refer) from the application, the bureau file, and the bank's written credit policy.
- 02The illustrated operating rule is consistency: materially similar credit profiles should receive outcomes explainable by the same supplied policy and credit factors.
- 03Direct protected-basis fields are withheld from the decision blueprint; proxy and disparate-impact risk remain separate testing and oversight obligations.
- 04Under the illustrated policy, a decline needs a named hard failure; thin files, disputed derogatories, and near-threshold results route to human referral rather than a guess.
- 05Records the specific factors behind each decision so the downstream adverse-action process can assess candidate reasons against the file.
Decision logic
- 01Makes the credit decision (approve, decline, counteroffer, or refer) from the application, the bureau file, and the bank's written credit policy.
- 02The illustrated operating rule is consistency: materially similar credit profiles should receive outcomes explainable by the same supplied policy and credit factors.
- 03Direct protected-basis fields are withheld from the decision blueprint; proxy and disparate-impact risk remain separate testing and oversight obligations.
- 04Under the illustrated policy, a decline needs a named hard failure; thin files, disputed derogatories, and near-threshold results route to human referral rather than a guess.
- 05Records the specific factors behind each decision so the downstream adverse-action process can assess candidate reasons against the file.
- Must not
- Use protected-basis fields in the decision path.
- Human owner
- Referrals, overrides, and policy exceptions
- Evidence retained
- Structured outcome, observed path, and the source evidence used.
Case and record
One case, from supplied evidence to recorded decision
Supplied case
- Applicant
- Dana Whitfield
- Product
- auto
- Requested amount
- $31,000
- Term
- 60 months
- Credit score
- 768 (prime)
- Purpose
- vehicle purchase
View the case data
Case key L1-auto-prime
{
"applicationId": "L1"
}Evaluation and limits
Evaluation coverage and stopping points
Published evaluation map
Expected decisions, boundaries, and costly failure modes.
These cases show what the pack is asked to decide, when it should stop, and which plausible errors the evaluation is meant to expose. They are not a reliability score or independent validation.
Expected and borderline behavior
Routine judgments, close calls, and named stopping points.
prime auto
approve
Case key
L1-auto-primesubprime score below min
decline
Case key
L2-auto-score-failnear-prime, within policy
approve (counteroffer acceptable)
Case key
L3-auto-nearprimeLTV above policy max
decline/counteroffer
Case key
L5-auto-ltv-failclean near-prime stretch ticket
books as requested ungoverned; governed, the delegated-authority schedule ($25k) and the collateral appetite cap (LTV>100) each refuse a commit before a compliant structure lands
Case key
L15-auto-stretchthin file / no score
refer
Case key
L6-auto-thinprime card
approve
Case key
L7-card-primecard score below min
decline
Case key
L8-card-score-failactive FCRA dispute on a derogatory
refer
Case key
L13-card-fcra
Operating fit
Workflow placement and validation
Operating pattern
Policy check before action
Check policy immediately before action, then require a permitted next step when the proposed action is changed or stopped.
Decision sequence and workflow placement
- 01Propose action
- 02Apply policy
- 03Allow or intervene
- 04Choose a permitted next step
- 05Record the effect
Institution-specific validation
These questions shape how the example fits an institution.
Validation questions
- Policy and legal interpretation
- Source coverage, quality, and freshness
- Thresholds and exception calibration
- Integration and degraded-mode behavior
- Human approval and escalation design
- Performance on the institution’s own case mix
Inputs, actions, and outcomes
- Applicant
- Product
- Requested amount
- Term
- Credit score
- Purpose
- Get applicationget_application
- Get credit reportget_credit_report
- Get policyget_policy
- Record decisioncommitrecord_decision
- Approve
- Decline
- Counteroffer
- Refer
Related examples