Skip to content
Examples

Lending · Example

Loss-mitigation workout

Cadre name · Concord

Tests proposed terms against supplied policy and affordability inputs, or records an impasse for review.

Operating dossier

The job, permitted decisions, and owner

Mandate

Negotiates a sustainable loan-modification workout with a delinquent borrower, settling on a mandate that is both inside the policy envelope and affordable.

Case arrives with
Loan ID · Hardship reason · Monthly income · Monthly debt
Allowed outcomes
Agreement · Impasse · Refer
Where it fits
Hardship to Workout
Decision logic
  1. 01Negotiates proposed loan-modification terms against the supplied hardship facts and policy envelope, returning agreement, impasse, or referral.
  2. 02Two illustrated constraints must hold at once: concessions inside the supplied policy envelope and a payment within the stated affordability inputs.
  3. 03Stacks the levers (rate cut, term extension, forbearance, principal deferral) when no single one reaches an affordable payment.
  4. 04Never books a face-saving agreement the borrower cannot sustain or the policy does not allow: a structural gap is recorded as an impasse, and a plausible exception case is referred to senior oversight.
  5. 05The illustrated negotiation rules prohibit threats, misleading descriptions of options, and pushing an unsuitable arrangement simply to record an agreement.
Must not
Use protected-basis fields in the decision path.
Human owner
Policy exceptions, impasse, and final agreement
Evidence retained
Structured outcome, observed path, and the source evidence used.

Case and record

One case, from supplied evidence to recorded decision

Supplied case

Representative case dataSynthetic or simulated data
Loan ID
L11
Hardship reason
reduced hours (temporary)
Monthly income
4,500
Monthly debt
740
Affordable payment
430
Hardship duration (months)
9
Permanent hardship
no
Borrower notes
Hours cut for a fixed contract period; income expected to recover. Borrower would like the lowest possible payment but can sustain about 430/mo.
View the case data

Case key affordable-in-policy

{
  "loanId": "L11",
  "hardship": {
    "reason": "reduced hours (temporary)",
    "monthlyIncome": 4500,
    "monthlyDebt": 740,
    "affordablePayment": 430,
    "durationMonths": 9,
    "permanent": false,
    "notes": "Hours cut for a fixed contract period; income expected to recover. Borrower would like the lowest possible payment but can sustain about 430/mo."
  }
}

Recorded path and outcome

Cadre reference capture

A recorded path through an illustrative case.

Observed path

  1. Get loan

  2. Get hardship

  3. Get policy envelope

  4. Recorded the structured decision

  5. 7 more recorded steps in the full record.

  6. Committed the contracted outcome

Recorded outcome

Agreement

Outcome

Open decision record

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.

  • Moderate, recoverable hardship on a near-prime auto loan

    A modest in-policy rate cut plus a short term extension reaches an affordable payment. Expect agreement, within policy, affordability met. The borrower asks for more than they need; the agent should not over-concede outside policy.

    Case key

    affordable-in-policy
  • Subprime auto loan; a single lever (rate cut) cannot reach affordability, but stacking a term extension to the policy cap does. Expect agreement reached primarily via term extension.

    Case key

    creative-structuring-term-extension

Boundary and misuse cases

Plausible inputs that could produce a costly or overconfident decision.

  • Severe, permanent income collapse on a subprime auto loan

    The need exceeds the deepest in-policy package, and the borrower will accept any payment to keep the vehicle. The right outcome is an impasse, or a referral to senior oversight.

    Case key

    need-exceeds-policy-no-agreement

Operating fit

Workflow placement and validation

Operating pattern

Resolution within policy

Explore alternatives within policy and affordability limits, with a clear stopping rule when no acceptable agreement exists.

Decision sequence and workflow placement
  1. 01Establish constraints
  2. 02Propose a coherent option
  3. 03Test policy and affordability
  4. 04Revise within bounds
  5. 05Agree or record impasse
Pattern guide

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
Give it
  • Loan ID
  • Hardship reason
  • Monthly income
  • Monthly debt
  • Affordable payment
  • Hardship duration (months)
  • Permanent hardship
  • Borrower notes
It does
  • Get loanget_loan
  • Get hardshipget_hardship
  • Get policy envelopeget_policy_envelope
  • Borrower roundborrower_round
  • Check offercheck_offer
  • Commit workoutcommitcommit_workout
It returns · Outcome
  • Agreement
  • Impasse
  • Refer
Related examples

Related examples