DPD-7 is late to the party. Early warning signals before DPD7 lending teams ignore usually whispered for days: broken promises-to-pay, shrinking partials, and phones that ring out. This is not another week-one delinquency playbook. It is pre-delinquency LMS flags small lenders can watch with basic PAR, arrears reports, and reminder hooks — without claiming a predictive early-warning product.
Use reports and reminder stubs you actually have. The craft is noticing, coding, and acting before the account ages into a bucket that costs field time.
Signals that quietly predict loss
- Broken PTP: borrower promised Friday, silence on Friday, new story on Monday.
- Partial pay decay: shrinking partials on a steady due amount.
- Contact decay: primary number fails; only relatives answer.
- Due-date shopping: repeated requests to move dues without a restructure gate.
- Visit avoidance: neighbors say they hide when the collector’s motorcycle is heard.
Small lender early warning PH practice codes these in the loan note the same day — not in an officer’s memory.
Pre-delinquency flags you can run thin
Configure or manually tag: missed PTP count of at least one in the current cycle; two consecutive partials below a percentage of due; failed SMS or call outcomes logged twice; reminder delivered but no payment within a day on previously clean accounts. Missed promise-to-pay signals are human. Your job is to make them visible on a queue officers open before lunch.
Playbook in the 72 hours before DPD-7
When a flag trips on a previously clean borrower in Pasig or Iloilo: call once, SMS once, note outcomes; offer a same-week partial that still shows intent without casually waiving policy fees; alert guarantor if mid or high ticket; if contact fails, schedule a visit before the weekend; if the story is a real mid-term shock, open the restructure gate — do not freestyle. Speed matters more than eloquence.
What to measure weekly
Track flags raised versus flags actioned within 24 hours, percent of flagged loans that avoid DPD-7, percent that still hit DPD-15, and officer variance on who ignores amber tags. Managers who only stare at PAR 30 are driving with the rear camera.
Pair with collections that protect cashflow, repayment discipline, late fees done clearly, and features. Stay away from black-box scoring claims; stay close to arrears truth.
14-day install
- Define four flags and the note template.
- Require action logging within 24 hours.
- Add guarantor step for mid tickets.
- Review avoided DPD-7 counts in the Friday huddle.
Target: half of amber accounts contacted same day.
(1) Worked example from a Metro Manila desk
Imagine a cashier in Quezon City closing a busy Tuesday: the numbers on the screen and the drawer only match when every repayment was posted before the count. The same discipline applies to this topic — write the rule, name the owner, and refuse chat-only exceptions. When a new hire arrives in week three, they should inherit a ritual, not a mystery. That is how Philippine one-desk and small-branch shops keep margin without theatrical software claims.
(2) Provincial desk notes (Cebu, Iloilo, Davao)
Outside Metro Manila, courier delays and thinner staff benches make written cadence even more important. A Cebu side desk cannot assume HQ will answer a float shout at 9 p.m. An Iloilo branch cannot assume the guarantor will walk in twice. A Davao collector cannot burn a full tank chasing zero-EV accounts. Localize the clocks and buffers; keep the principles identical: visible loans, visible repayments, named approvals, coded exceptions.
(3) What “good” looks like after two weeks
You will know the habit stuck when Friday sampling finds consistent language in loan notes, when officers can recompute the same KPIs from the same reports, and when borrowers hear one policy story instead of three. If group chat still hosts the real policy, you are not done. Move decisions into the LMS file and the signed one-pagers. Thin ops beat folklore.
(4) Common objections — and calm answers
“Too slow.” Faster than reconstructing a weekend of missing posts or a month of soft defaults. “Borrowers will leave.” Clear clocks and gates retain the borrowers you want. “We need AI.” You need arrears truth and human follow-up first. “We need a new module name.” You need roles, reports, and maker-checker on the Must list you already have.
(5) Worked example from a Metro Manila desk
Imagine a cashier in Quezon City closing a busy Tuesday: the numbers on the screen and the drawer only match when every repayment was posted before the count. The same discipline applies to this topic — write the rule, name the owner, and refuse chat-only exceptions. When a new hire arrives in week three, they should inherit a ritual, not a mystery. That is how Philippine one-desk and small-branch shops keep margin without theatrical software claims.
(6) Provincial desk notes (Cebu, Iloilo, Davao)
Outside Metro Manila, courier delays and thinner staff benches make written cadence even more important. A Cebu side desk cannot assume HQ will answer a float shout at 9 p.m. An Iloilo branch cannot assume the guarantor will walk in twice. A Davao collector cannot burn a full tank chasing zero-EV accounts. Localize the clocks and buffers; keep the principles identical: visible loans, visible repayments, named approvals, coded exceptions.
(7) What “good” looks like after two weeks
You will know the habit stuck when Friday sampling finds consistent language in loan notes, when officers can recompute the same KPIs from the same reports, and when borrowers hear one policy story instead of three. If group chat still hosts the real policy, you are not done. Move decisions into the LMS file and the signed one-pagers. Thin ops beat folklore.
(8) Common objections — and calm answers
“Too slow.” Faster than reconstructing a weekend of missing posts or a month of soft defaults. “Borrowers will leave.” Clear clocks and gates retain the borrowers you want. “We need AI.” You need arrears truth and human follow-up first. “We need a new module name.” You need roles, reports, and maker-checker on the Must list you already have.
Note templates officers will actually type
Keep templates short: “PTP 500 Fri 5pm — broken,” “Partial 300 of 800 — decay,” “Call failed x2 — contact rot,” “SMS delivered no pay 24h.” Officers in a hurry will not write novels. They will type four-word codes if those codes unlock a queue filter. Managers should reject empty notes like “follow up” with no date and no channel.
On Friday, sample twenty amber accounts. If half lack action timestamps, your flag system is decoration. Coaching then targets the officer’s morning routine, not another poster about collections excellence.
Guarantor timing on amber accounts
For mid and high tickets, notify the co-maker on the first broken PTP — not after DPD-15. Early polite notice preserves relationships and often surfaces the borrower’s real number. Late notice feels like blame. Document the notice in the same loan file where the flag lives.
Implementation checkpoint 1
Checkpoint 1 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 2
Checkpoint 2 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 3
Checkpoint 3 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Implementation checkpoint 4
Checkpoint 4 for this playbook: confirm the written one-pager exists, confirm one named owner in the branch, confirm last week’s sample audit happened, and confirm exceptions carried reason codes. Philippine desks in Manila, Cebu, and Davao that skip checkpoints recreate folklore inside two pay cycles. Keep the checkpoint boring and weekly.
If the checkpoint fails, pause new process complexity. Fix the broken step before adding another form field. Thin ops means fewer steps done every time — not more steps done rarely. Log the checkpoint result in a shared branch note dated in Asia/Manila local time so remote owners can see it.
Closing
Early warning before DPD-7 is broken PTPs, partial decay, and contact rot made visible on a work queue — then worked. Use PAR and reminder hooks you have. Skip the crystal ball.
Work those queues from https://pesolend.com/app/login.