Recall and reassignment
Purpose. Recall is often described as “pulling accounts back” from a DCA. That description is too small. In a well-run model, recall is a compliance control when the bank must stop third-party pressure, a strategy control when the bank changes course, a portfolio lever when performance or risk shifts, and a state transition that must be visible in CP systems, vendor systems, and reporting cohorts. This page ties recall to Controls framework and to technical design in CP / DCA files and R1 / R2 traceability.
Secured recoveries. Secured recoveries is a separate case-managed process with different legal, security, and asset realisation mechanics. It may eventually produce a crystallised shortfall that then enters the unsecured or contingent recoveries model described in this pack. Do not merge secured enforcement mechanics into this contingent recall narrative.
What recall is
Recall ends (or prepares to end) a specific placement episode: the DCA should stop outbound collection activity governed by that placement, subject to contract and law. It does not always mean the customer story is finished; it means this vendor chapter closes under CP authority.
Recall is therefore inseparable from suppression and contact rules. If recall only updates a database row but diallers still run, you have a broken control, not a completed recall.
Types of recall: compliance
Compliance recalls are immediate and non-negotiable in the sense that the DCA cannot treat them as a commercial negotiation. Examples include hardship holds that require stop or soften under policy, complaints that require cease collection activity, disputes that freeze pursuit while investigated, deceased or bankruptcy events, legal holds, and other protected states defined by your bank and regulator.
The DCA may still log a request for clarification or supply evidence, but it cannot override CP. If your contract implies the vendor can “defer” a compliance recall, fix the contract. That pattern is a conduct incident waiting to happen.
Types of recall: strategic
Strategic recalls happen when the bank chooses a different path: poor payment or engagement, underperformance versus cohort, change in segment strategy, move from DCA1 to DCA2, move internal, move to legal, prepare for debt sale, or close to abandon or forgiveness under governance. These recalls are still controls: they encode why the bank stopped this placement.
Strategic recall should always connect to proposed versus actual next strategy. The DCA may propose (“we think R2 will work,” “we need extension to finish arrangement paperwork”). CP decides. That decision should be stored as data, not only in meeting minutes.
Types of recall: data and control
Sometimes you recall because the placement itself was wrong: incorrect balance, duplicate assignment, wrong customer linkage, a catastrophic interface break, or fraud suspicion. These recalls are defensive: stop harm, preserve evidence, re-open only when clean.
DCA recall request, extension, and challenge
Vendors must be able to request recall, request extension of time before recall effect, propose alternative actions, and update arrangement information. This is an operating model requirement, not a nice-to-have interface. Without it, strategists get surprises and customers get incoherent treatment.
The governance rule is constant: DCA can influence; CP decides. For non-compliance recalls, CP may accept an extension when the vendor shows active engagement, a credible arrangement in progress, or data fixes underway. The extension should be logged with an end time and review trigger. “Silent extension” via email is another failure pattern.
Recall as control, not only event
A healthy model tests recall like a control: stop contact within SLA, remove from dialler, confirm vendor acknowledgement, update CP status, feed suppression to any parallel channels. COF for DCA describes how engineered gates can block actions after recall states, which reduces reliance on manual vigilance alone.
What happens after recall
Recall should terminate in a defined next state: internal queue, R2 placement, legal instruction, sale preparation, closure to abandon or forgive, or customer paid in full through another path. Ambiguity is expensive. If operations “recall to nowhere,” cohort reporting breaks and customers fall between teams.
Link explicitly to Allocation strategy and End states. The Worked example shows one path through R1, recall, and R2.
Risks when recall is weak
- Double contact: DCA and internal teams both pursue.
- Hardship breach: demand tone continues after recall should have stopped work.
- Stale balance or status: scripts use old amounts after partial payment.
- Arrangement conflict: DCA believes a plan is active; CP has broken it.
- Reporting drift: recalled accounts still counted as open at vendor in monthly packs.
Governance and reporting link
Recall volume, reason mix, SLA adherence, and failures to stop should appear in Layer 3 and issues tracking. A spike in compliance recalls may be good (better detection) or bad (systemic placement errors). A flat strategic recall rate with rising complaints may signal vendor gaming. Governance asks why, not only how many. See Governance and Reporting.
Related: Controls framework · Back to pack home