Litigation and Recovery
Debt Recovery Legal Workflow Metrics
Denominator-aware debt recovery metrics for notices, service, filings, hearings, orders, settlements, promises, payments, cash, aging, cost, and forecasts.
Direct answer
A defensible debt recovery dashboard starts with an eligible account or case population, a dated event dictionary, and separate ledgers for legal outcomes, commitments, and cash. Track notice issuance and service, filings, hearings, orders, settlements, promises, payments, principal, interest, costs, aging, roll rates, cure, contact, cycle time, and forecast error with explicit denominators and exclusions. Use segmented internal baselines; no metric is a universal benchmark or a guarantee of collection.
Definitions
Eligible account or case
A unique account or legal case inside the declared cohort, snapshot, and jurisdiction that meets the metric-specific inclusion rules and is not in an identified exclusion state.
Exposure basis
The amount and components used as a financial denominator, such as principal outstanding, accrued interest, approved costs, total claim, or a declared opening balance at a reporting date.
Demand notice
A recorded notice requesting payment or another defined response, with its version, approval, issue date, delivery channel, recipient, and linked account or case.
Service outcome
The recorded result of an attempted notice delivery or legally relevant service method, such as served, refused, returned, unverified, substituted, or pending under the applicable process.
Legal outcome
A recorded procedural or adjudicative event, including filing acceptance, hearing result, order, dismissal, withdrawal, or other jurisdiction-specific disposition; it is not cash recovery.
Promise to pay
A documented commitment to pay a stated amount by a stated date or schedule, subject to validation, modification, breach, and cancellation rules.
Cash collected
A payment received, cleared, posted, and applied to the declared account or case ledger, separated into principal, interest, costs, fees, reversals, and unapplied amounts.
Cure
A defined exit from a delinquent or recovery state after qualifying payment or arrangement conditions are met and the account remains within the organization-approved cure observation rule.
Roll rate
The movement of eligible accounts or balance from one declared aging, delinquency, or legal stage to another during an observation interval.
Recovery cycle time
Elapsed duration between two declared recovery events, such as default to notice, notice to service, filing to order, or case opening to cleared payment.
Forecast error
The difference between a documented expected recovery amount and the corresponding actual cleared and applied cash for the same cohort, period, currency, and component definition.
Exclusion
A documented rule that removes a record, event, amount, or period from a specific metric because it is outside scope, invalid, duplicated, transferred, reversed, or otherwise not comparable.
Field definitions
Population and exposure
- accountOrCaseId
- Stable identifier linking the account, claim, legal case, notices, events, promises, payments, and costs.
- Type: Defined in the implementation data dictionary
- Requiredness: Required
- Validation: Use a non-reused identifier and document the relationship between a lending account, borrower, claim, suit, tribunal matter, or successor case.
- Owner: Assigned record owner
- eligibilitySnapshot
- Cohort, as-of date, reporting period, jurisdiction, status, and inclusion or exclusion decision.
- Type: Defined in the implementation data dictionary
- Requiredness: Required
- Validation: Freeze eligibility before calculating rates. Record transferred, sold, duplicate, invalid, disputed, closed, and out-of-scope records without silently dropping them.
- Owner: Assigned record owner
- exposureComponents
- Opening and closing principal, interest, approved costs, fees, total claim, currency, and balance basis.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for amount metrics
- Validation: Distinguish booked, claimed, committed, received, cleared, applied, reversed, waived, written-off, and unapplied amounts.
- Owner: Assigned record owner
- agingAndStage
- Versioned delinquency, aging, legal-stage, and cure-state classifications at each snapshot.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for aging and roll rates
- Validation: Publish bucket boundaries, precedence, source dates, transfer logic, and treatment of unknown or conflicting status.
- Owner: Assigned record owner
Workflow events
- noticeAndService
- Notice type, version, approval, issue, attempt, channel, recipient, service method, outcome, and evidence.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for notice and service metrics
- Validation: Keep sent, attempted, delivered, served, refused, returned, unverified, and pending as separate controlled outcomes.
- Owner: Assigned record owner
- legalProgression
- Filing, acceptance, hearing, adjournment, order, settlement, dismissal, withdrawal, and other forum-specific events.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for legal-stage metrics
- Validation: Record event date, forum, case reference, outcome, next action, source evidence, and whether the event is procedural or adjudicative.
- Owner: Assigned record owner
- commitment
- Settlement or promise amount, component, approval, due schedule, modification, payment linkage, breach, and cancellation.
- Type: Defined in the implementation data dictionary
- Requiredness: Required when commitments are measured
- Validation: Keep commitment face value and cleared payment separate. Record partial, late, reversed, and unapplied payment outcomes.
- Owner: Assigned record owner
- paymentApplication
- Payment source, received and cleared dates, currency, amount, allocation, reversal, refund, and ledger linkage.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for cash metrics
- Validation: Count cash only after the declared cleared and applied condition. Preserve unapplied and reversed amounts outside collected cash.
- Owner: Assigned record owner
Measurement and governance
- metricDefinition
- Metric name, unit, numerator, denominator, observation window, formula version, and segmentation.
- Type: Defined in the implementation data dictionary
- Requiredness: Required
- Validation: Store the exact query or calculation version and state whether the result is account-count, case-count, event-count, duration, or currency-weighted.
- Owner: Assigned record owner
- contactAndCure
- Attempt, channel, right-party or valid-contact result, restriction, qualifying cure event, and cure observation period.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for contact or cure metrics
- Validation: Do not count an attempt as contact or a promise as cure. Retain complaint, restriction, consent, and escalation outcomes where applicable.
- Owner: Assigned record owner
- legalCost
- Cost category, incurred or paid basis, currency, case linkage, invoice or source, allocation method, and period.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for legal-cost metrics
- Validation: Separate filing, service, counsel, agency, court, internal, recovered, waived, disputed, and unallocated costs.
- Owner: Assigned record owner
- forecastVersion
- Frozen expected amount, component, cohort, forecast date, period, currency, assumptions, and version owner.
- Type: Defined in the implementation data dictionary
- Requiredness: Required for forecast error
- Validation: Compare against the same cohort and period of cleared and applied cash. Preserve timing, reversal, pending-application, and scope-change explanations.
- Owner: Assigned record owner
Controlled vocabulary guidance
- legalStage
- Examples: Eligible, Notice due, Notice issued, Service pending, Served, Filing approved, Filed, Hearing scheduled, Order pending, Order received, Settlement discussion, Settled, Cured, Closed, Transferred, Excluded
- Governance: Define entry and exit evidence for each stage. A stage describes workflow position and must not be interpreted as a payment or legal-success guarantee.
- serviceOutcome
- Examples: Delivered, Served, Refused, Returned, Unverified, Address issue, Restricted, Pending, Not applicable
- Governance: Use the applicable legal or operational service vocabulary for the jurisdiction and preserve the source method and evidence.
- commitmentOutcome
- Examples: Proposed, Approved, Executed, Due, Kept, Partial, Late, Breached, Modified, Canceled, Expired, Not applicable
- Governance: Commitment outcomes are not cash outcomes. A kept commitment requires the guide-defined payment condition and should link to cleared and applied payment records.
- paymentOutcome
- Examples: Received, Cleared, Applied to principal, Applied to interest, Applied to cost, Unapplied, Reversed, Refunded, Disputed, Written off
- Governance: Use a payment allocation rule and retain each component. Do not count received, promised, or booked amounts as collected cash unless the declared cleared-and-applied condition is met.
- exclusionReason
- Examples: Duplicate, Test record, Out of scope, Transferred or sold, Closed before window, Invalid identifier, Invalid amount, Missing required event, Unmatched payment, Reversed or refunded, Disputed, Policy-restricted, Unknown
- Governance: Report exclusion counts by reason and metric. Exclusion is not success, failure, cure, or non-contact.
Practical workflow
Declare the measurement unit and snapshot
Choose account, facility, borrower, claim, legal case, notice, hearing, promise, payment, or currency amount as the unit for each metric. Publish the as-of date, reporting period, currency, time zone, jurisdiction, portfolio segment, and whether results are account-count or balance-weighted.
Build the eligible population
Create a stable population of unique accounts or cases with the required identifier, exposure basis, status, jurisdiction, and event dates. State whether eligibility is measured at opening, event, or period end, and freeze the population before calculating rates.
Publish the event dictionary
Define default, delinquency, demand approval, notice issue, delivery attempt, service outcome, filing submission and acceptance, hearing scheduled and held, order received, settlement approval and execution, promise made and due, payment received and cleared, application, reversal, cure, closure, and transfer events.
Reconcile the exposure ledger
Reconcile opening principal, interest, approved costs, payments, reversals, adjustments, waivers, write-offs, settlements, and closing balances to the source ledger. Keep booked, claimed, committed, received, cleared, and applied amounts distinct.
Measure demand and service
Report the population requiring a demand notice, notices approved and issued, delivery attempts, valid service outcomes, returned or refused notices, and unresolved service exceptions. Separate a notice sent from a notice legally or operationally treated as served.
Measure filings, hearings, and orders
Track cases eligible for filing, filings submitted and accepted, hearings scheduled, hearings held or adjourned, orders expected, orders received, and each procedural disposition. Use the applicable forum and process definitions; do not treat filing, attendance, or an order as proof of payment.
Track settlements and commitments
Record settlement offers, approvals, executed agreements, waived components, promised amounts, due dates, modifications, breaches, and cancellations. Report settlement or promise outcomes separately from cleared cash and from a court order or judgment.
Post and classify payments
Use cleared payment records and an allocation rule to classify cash to principal, interest, costs, fees, unapplied cash, reversals, and refunds. Preserve currency, value date, posting date, application date, source, and account or case linkage.
Calculate aging and roll movement
Assign each eligible account or case to a versioned aging or legal-stage bucket at the declared snapshot. Compare opening and closing buckets using account counts and balance amounts, and explain transfers, cures, closures, settlements, write-offs, and missing status events.
Measure contact and cure
Define a contact attempt, valid contact, right-party contact, and contact channel. Measure contactability and outcomes against the population due for contact. Define cure using actual qualifying payment or arrangement conditions and a stated observation period; a promise alone is not cure.
Measure cycle time and legal cost
Calculate event-to-event durations with calendar or business units, pause rules, time zones, reopened work, and missing timestamps. Attribute filing fees, service fees, counsel fees, court costs, agency costs, and other approved legal expenses to the same case and reporting cohort.
Compare forecast with actual cash
Freeze the forecast version, expected period, expected principal and other components, and eligible cohort. Compare only with cleared and applied cash from the same cohort and period, while preserving timing differences, reversals, settlements, write-offs, and records still pending application.
Review segmentation and data quality
Segment by product, originator, delinquency or aging bucket, balance band, geography, jurisdiction, collateral, legal forum, counsel or agency, notice channel, contact outcome, settlement type, and case stage. Publish missing identifiers, invalid dates, duplicate events, unmatched cash, and unclassified amounts before interpreting movement.
Set internal decision rules
Use a documented internal baseline and qualitative decision bands for investigation, escalation, staffing, service review, data remediation, or strategy changes. Do not convert an ordinal band into arithmetic, copy a vendor or industry number as a universal target, or promise a recovery result.
Retain evidence and review changes
Retain source extracts, event definitions, cohort snapshots, ledger reconciliations, formula versions, exclusions, approvals, forecast versions, and report outputs. Revalidate after a system, policy, legal process, servicing channel, portfolio mix, currency, or accounting treatment changes.
Comparison
| Metric family | What it answers | Separation or denominator guardrail |
|---|---|---|
| Legal progression | How far eligible matters moved through notice, service, filing, hearing, order, settlement, or closure stages. | Use the stage-specific eligible population and record procedural outcomes separately from payment or recovery amounts. |
| Commitment performance | Whether settlements or promises were approved, due, modified, kept, breached, or canceled. | A commitment is not cash. Measure due commitments and cleared payments separately, with partial payments and reversals classified. |
| Cash recovery | How much cleared and applied principal, interest, cost, or fee cash was collected. | Use a declared exposure amount and allocation rule. Do not count a judgment, order, settlement face value, or promise as collected cash. |
| Pipeline movement | Where accounts or cases are aging, curing, rolling forward, closing, or remaining unresolved. | Publish opening population and balance, transfers, exits, additions, exclusions, and unknown status rather than inferring movement from a single ending snapshot. |
| Cost and forecast | What legal work cost and how expected cash compared with actual applied cash. | Keep fees and costs in the stated currency and cohort. Forecast error must identify timing, reversals, pending application, and denominator-zero treatment. |
Limitations and exceptions
- A filing, hearing, order, or settlement can be a legal or procedural outcome without producing cleared cash. Never report legal progression as collection performance.
- A promise or settlement face value is a commitment, not principal, interest, cost, or fee cash. Report kept, breached, partial, modified, and canceled commitments separately.
- A portfolio mix change, transfer, write-off, sale, restructure, or accounting reclassification can move balances without a change in operating performance.
- Small cohorts, sparse events, missing timestamps, and unclassified payments can make rates, aging, cycle times, and forecast error unstable. Show counts and data-quality exclusions.
- Jurisdiction, forum, consumer-protection, servicing, insolvency, limitation, notice, and privacy requirements vary. Official sources provide context, not a universal recovery workflow or legal advice.
- Contact attempts do not prove right-party contact, service, willingness to pay, or recovery. Define contact outcomes and preserve consent, restriction, complaint, and escalation handling.
- A lower legal cost per case can reflect fewer filings, cheaper matters, delayed work, or incomplete cost capture rather than better recovery. Pair cost with stage, outcome, quality, and cash context.
- No metric in this guide is a universal benchmark, legal deadline, collection guarantee, or prediction of an individual account outcome.
Primary sources
Methodology
Use a versioned event dictionary and a frozen eligibility snapshot for each metric. Let eligible_accounts = unique accounts meeting the declared cohort, jurisdiction, status, identifier, amount, and event-date rules at the stated as-of point; eligible_cases = unique legal cases meeting the case-specific rules. Report account-count and balance-weighted results separately. Demand_notice_rate = unique eligible accounts or cases with at least one notice issued / eligible accounts or cases requiring a notice. Service_rate = notices with the declared valid service outcome / notices issued with a service obligation. Filing_rate = unique eligible cases with at least one accepted filing / cases approved and eligible for filing. Hearing_completion_rate = hearings held or disposition-recorded / hearings scheduled and due. Order_recording_rate = unique matters with at least one order received and recorded / matters with an order expected in the window. Settlement_execution_rate = unique eligible cases with at least one executed settlement / eligible cases with an approved settlement path or opened settlement negotiation. Each completion-rate numerator is a distinct-entity subset of its denominator; if event frequency is needed, report events per eligible entity instead of a completion rate. For bounded examples, 80 unique eligible accounts with a notice issued / 100 eligible accounts requiring notice = 80%; 18 eligible cases with an accepted filing / 24 eligible cases approved for filing = 75%; 9 matters with an order recorded / 12 matters with an order expected = 75%; and 6 eligible cases with an executed settlement / 10 eligible cases with an approved settlement path = 60%. Promise_kept_rate = promises with the declared kept condition / promises due; promise_to_cash_rate = promises with cleared and applied payment by the due rule / promises due. Payment_realization_rate = cleared and applied cash / eligible exposure basis, with separate results for principal, interest, approved cost, fee, and total cash. Never count a promise, settlement face value, judgment, order, or booked receivable as cash collected. Roll_rate(A_to_B) = accounts or opening balance in bucket A at the opening snapshot that are in bucket B at the closing snapshot / eligible accounts or opening balance in bucket A; publish counts and currency separately and explain additions, exits, transfers, write-offs, and unknowns. Aging = as-of date minus the declared default, delinquency, demand, filing, or case-opening date, in calendar days or business days as stated; publish count, balance, median, and selected percentiles by bucket. Cycle_time = end event timestamp minus start event timestamp, in declared hours or days, with pause, business-calendar, time-zone, reopened-work, and missing-event rules. Cure_rate = eligible accounts entering the defined delinquent or recovery state that meet the qualifying payment or arrangement condition and remain cured for the declared observation period / eligible accounts entering that state; a promise alone does not cure. Contact_rate = accounts with the declared valid or right-party contact outcome / eligible accounts due for contact; attempt_rate and contactability should be reported separately. Legal_cost_per_case = eligible legal costs in the declared currency and period / eligible cases with the stated cost basis; separately report unallocated, disputed, waived, recovered, and internal costs. Forecast_error_pct = absolute(actual cleared and applied cash - frozen forecast cash) / frozen forecast cash when the forecast denominator is greater than zero; also publish signed_error_currency = actual cash - forecast cash and forecast error by principal, interest, cost, and total. Exclude and count duplicates, test records, out-of-scope or transferred accounts, closed-before-window records, invalid identifiers or amounts, missing required events, unmatched or reversed payments, disputed or policy-restricted records, and unknown classifications according to each metric rule. Do not turn exclusions into successes or failures. Segment by product, balance band, age, jurisdiction, forum, collateral, counsel or agency, notice channel, contact outcome, settlement type, and stage. Compare only like-for-like cohorts and use internal baselines; official sources inform conduct, procedure, lending oversight, and measurement discipline but do not prescribe universal benchmarks, legal deadlines, collection guarantees, or individual outcomes.
Make recovery workflow performance measurable
Reach out and learn more about our offerings and how CaseDocker can help you
Built for legal operations teams
Share your use case and we will connect you with the right team for product guidance, pricing, and rollout planning.
Clear next steps
Expect a response from our team with the most relevant next step for your inquiry.
Get in Touch
Get in Touch
FAQs
Related CaseDocker capabilities
Credit WorkDesk
Coordinate loan, borrower, account, notice, recovery, payment, and portfolio workflows in a structured credit operations workspace.
ExploreLoan recovery legal workflow
Connect recovery intake, demand notices, legal escalation, settlements, and progress reporting across recovery and legal teams.
ExploreRecovery suit management
Track recovery suits, hearings, orders, settlements, documents, and recovery outcomes in one case workflow.
ExploreNBFC legal recovery
Give NBFC teams structured recovery cases, notice timelines, litigation coordination, and recovery-progress visibility.
ExploreTurn this guide into an operating plan
Share your current legal workflow and CaseDocker can map the right modules, integrations, controls, and rollout sequence.