Educational ops playbook only — not labor-law, holiday-pay, or regulatory advice. Align rota rules with your employment contracts, DOLE guidance, and branch policy.
When a Philippine money-lender branch closes for Sunday or a long weekend, borrowers still call. Some want a payment receipt posted before Monday. Some dispute a reminder. Some ask where to drop cash because the market day shifted. If nobody owns those missed calls, dues slip, PAR creeps, and the first open morning becomes a firefight. A clear Sunday collections coverage Philippines playbook — a named desk rota plus a missed-call escalation ladder — stops that drift without inventing a holiday-coverage product module.
This guide is for owners, branch managers, and ops leads at multi-desk and multi-branch small lenders who need weekend and holiday coverage that stays claim-safe and auditable. You will get a 7-slot Holiday Desk Rota, a four-rung Missed-Call Escalation Ladder (Hour 0 / +4h / +24h / next open day), and a worked Quezon City / Caloocan branch example with illustrative ₱ ops math. Soft note: an LMS like PesoLend already keeps borrower CRM, loan-officer assignment, repayments and receipts, branch roles and permissions, reminder stubs, and basic PAR/arrears reports in one place — use those as the system of record while you run the rota. This is an ops playbook, not a shipped “holiday desk” feature.
Why Sunday and holiday silence costs more than one late installment
Closed-door days are not zero-risk days. Typical failure modes for PH small lenders:
- Borrowers SMS the officer’s personal number; the officer is off-duty and replies late — or not at all.
- A payment is received via e-wallet or cash drop, but no receipt is posted until Tuesday; the LMS arrears view still shows DPD.
- A reminder stub fires Friday night; the borrower’s callback lands Sunday morning with nobody on the rota.
- Monday opening stack: unreturned calls, unposted receipts, and a PAR snapshot that looks worse than Friday’s even though cash moved over the weekend.
You do not need a collections BI suite or a special holiday module to fix this. You need (a) a published rota that assigns one on-call desk per closed day, (b) role-scoped LMS access so that desk can look up borrowers and post repayments under maker-checker where your policy requires it, and (c) a ladder that says how long a missed call may sit before it escalates. Related habits: staff roles and branch permissions, calendar dues and reminder hooks, and receipt discipline after collections.
Original element: 7-slot Holiday Desk Rota
Print this table or pin it as a branch note one week before every long weekend and every month that includes a Sunday-heavy due calendar. A slot is “closed” only when the named on-call person and the backup both acknowledge the assignment in writing (LMS note, shared sheet, or signed rota form).
| Slot | Window (Asia/Manila) | Primary owner | Backup | Must be able to do | Evidence |
|---|---|---|---|---|---|
| S1 · Pre-close brief | Last open day, 15:00–16:00 | Branch manager | Ops lead | Publish rota, freeze non-urgent disbursements for closed days, export dues list for S2–S4 windows | Signed rota + dues export |
| S2 · Sunday AM desk | Sunday 08:00–12:00 | On-call officer A | On-call cashier | Answer hotline / shared SIM; look up borrower; log call notes; take payment info for later posting | Call log + LMS notes |
| S3 · Sunday PM desk | Sunday 12:00–17:00 | On-call officer B | Manager | Same as S2; hand off open tickets to S4 if unresolved | Handoff note |
| S4 · Holiday mid-day | Public holiday 09:00–15:00 | Rotating officer | Manager | Same as S2–S3; prioritize arrears callbacks from Friday reminder stubs | Arrears callback sheet |
| S5 · Cash / receipt gate | Any closed-day payment received | On-call cashier (or manager if cashier off) | Maker-checker pair | Record cash/e-wallet proof; queue repayment for maker-checker post on next open day or post same day if policy allows remote dual control | Receipt stub + LMS queue |
| S6 · Escalation watch | Continuous while S2–S4 live | Branch manager | Owner / ops | Enforce Missed-Call Ladder; unlock role if on-call lacks needed permission | Escalation timestamps |
| S7 · Next-open recon | First open morning, first 90 min | Manager + cashier | On-call from prior slot | Post queued repayments; clear call log; PAR/arrears snapshot vs Friday close | Posted batch + PAR print |
Seven slots sound heavy for a one-desk shop. Collapse S2 and S3 into one Sunday window, keep S5 and S7 mandatory, and still name a backup. Two- and three-branch lenders should publish one rota per branch with a shared S6 manager watch so a single missed-call ladder does not bounce between barangays.
Missed-Call Escalation Ladder (Hour 0 / +4h / +24h / next open day)
A missed call is any inbound attempt on the published coverage channel (shared SIM, branch landline forward, or LMS-linked reminder reply) that is not logged with an outcome within the ladder’s first rung. Use these four rungs as policy — adjust times only if you write the change on the rota.
| Rung | Clock | Who acts | Required action | Done when |
|---|---|---|---|---|
| R0 · Capture | Hour 0 (missed call lands) | On-call desk (S2/S3/S4) | Log caller number, borrower ID if known, channel, and reason code (pay / dispute / location / other) | LMS note or call-log row exists |
| R1 · First reply | +4 hours still inside coverage window; else next live slot start | On-call desk | Return call or SMS once; offer payment drop options; if payment received, open S5 queue | Reply timestamp + outcome code |
| R2 · Manager pull | +24 hours from Hour 0 if still open | S6 manager | Reassign ticket; check arrears view; decide waive-reminder vs keep penalty per written policy | Manager note on loan file |
| R3 · Next-open close | First open morning (S7) | Manager + cashier + prior on-call | Post or void queued receipts; update borrower notice; include in PAR/arrears recon | Zero open Sunday/holiday tickets |
Do not let R1 sit on a personal chat thread with no LMS note. If the on-call officer cannot find the borrower file, that is an S6 permissions problem — fix role scope, do not invent a parallel spreadsheet of “Sunday special” accounts.
Worked example: QC–Caloocan two-desk weekend (illustrative ₱ math)
Illustrative only — not a pricing quote, yield promise, or product claim. Assume a two-desk money lender with books split Quezon City (Desk A) and Caloocan (Desk B). Friday close shows:
- Desk A: 180 live loans; ₱1.2M outstanding principal (illustrative).
- Desk B: 140 live loans; ₱900k outstanding principal (illustrative).
- Combined dues due Sunday–Monday window: 42 installments totaling about ₱168k face (illustrative average ₱4k each).
- Friday reminder stubs already sent for 28 of those 42.
Without a rota, a plausible weekend looks like this: 11 missed calls on personal lines, 4 e-wallet payments totaling ₱16k with screenshots only in chat, and Monday morning shows those 4 still in arrears on the LMS while cash already moved — classic receipt gap. Cost to the book is not only the ₱16k timing noise; it is the extra officer hours chasing “already paid” disputes and the PAR print that wrongly flags clean payers.
With the 7-slot rota applied:
- S1 Friday 15:30: Manager publishes Sunday rota — Officer A owns S2 (08:00–12:00), Officer B owns S3 (12:00–17:00), cashier on S5 remote queue, manager on S6.
- S2 Sunday 09:10: Three callbacks from Friday reminders; two borrowers confirm Monday cash drop; one pays ₱4,000 via e-wallet. On-call logs R0, opens S5 queue with proof photo, posts LMS note on the loan.
- S3 Sunday 14:40: Two new missed calls captured at R0; one returned within +4h (R1) with a location for Monday; one no-answer → stays open for R2.
- S6 Sunday 18:00: Manager pulls the open no-answer (+24h will land Monday); flags arrears view; no fee waiver without written policy.
- S7 Monday 08:15: Cashier + manager post the ₱4,000 repayment under maker-checker, clear call log (zero open weekend tickets), take PAR/arrears snapshot vs Friday. Illustrative result: one posted receipt, two scheduled Monday drops, one manager-owned callback — not eleven orphan chat threads.
Scale the same ladder to a three-branch holiday: keep S5 and S7 centralized if only one cashier can post, but keep S2–S4 local so barangay callers hear a familiar desk.
Who this is for — and who should skip
Use this playbook if you run one or more PH desks with Sunday dues, market-day borrowers, or public-holiday calendars that still generate reminders and callbacks. Especially useful when officers already share a branch hotline or SIM and you only need discipline, not new software.
Skip or adapt heavily if you are a single owner-operator with no staff (collapse to a personal “Sunday hour” plus Monday recon), or if your regulator / investor pack already mandates a different after-hours protocol — follow the stricter written rule and map it onto S5/S7 evidence so LMS receipts still match cash.
Decision framework: personal phone vs shared coverage channel
| Signal | Prefer shared hotline + LMS notes | Personal phone only is high risk |
|---|---|---|
| Staff count | 2+ people who can rotate S2–S4 | One person holds every borrower chat |
| Receipt posting | Cashier or maker-checker can post from proof queue | Payments live only in screenshots |
| Role scope | On-call has branch-scoped borrower + repayment view | On-call cannot open LMS off-site |
| Escalation | Manager can see open R0–R2 tickets Monday | Manager learns problems from angry walk-ins |
If you must keep personal phones for relationship work, still require R0 capture into the LMS within the coverage window. The borrower relationship can stay warm; the audit trail cannot stay private.
Common traps that break Sunday coverage
- Rota published in a group chat with no S1 export. When the SIM dies, nobody has the dues list.
- On-call without repayment or borrower permission. They take promises they cannot verify — fix roles before the weekend.
- Posting repayments without maker-checker when your weekday policy requires it. Weekend shortcuts that violate dual control create bigger Monday problems. See maker-checker for disburse and repay.
- Treating reminder stubs as optional. If Friday stubs fire, Sunday must own the callbacks or you train borrowers to ignore reminders.
- Skipping S7 PAR/arrears recon. You will not see silent DPD from unposted weekend cash until the weekly review — too late for a clean narrative.
- Inventing a parallel “holiday spreadsheet.” Keep borrower files, dues, and role-scoped access in the LMS; use the rota as a people schedule, not a second books system.
FAQ
Do we need to disburse on Sundays?
Usually no. Most PH small lenders freeze non-urgent disbursements on closed days (S1) and keep coverage for collections, receipts, and dispute callbacks. If you must disburse in an emergency, require the same maker-checker path you use on weekdays.
Can the on-call officer waive late fees over the phone?
Only if your written policy allows it and the waiver is logged on the loan file with manager visibility (R2). Verbal waivers that never reach the LMS are how holiday goodwill becomes Monday arguments.
What if nobody wants Sunday duty?
Rotate fairly, publish the calendar a month ahead, and keep shifts short (S2/S3 split). Comp time and holiday-pay rules are employment matters — settle them in contracts, not in the LMS. The LMS job is to make the chosen on-call person effective with borrower files and receipts.
How does timezone settings matter?
Due dates and reminder stubs should respect your tenant timezone (Asia/Manila for domestic books). Mis-set timezones create “Sunday” dues that were meant for Monday — fix settings before you blame the rota. See timezone-aware due dates.
Is this a substitute for a collections command center?
No. This is a closed-day ownership ladder using borrowers CRM, assignments, repayments/receipts, roles, reminder stubs, and basic PAR/arrears reports. It does not replace weekday route planning or a full collections analytics suite.
What to do next
This week: run S1 once — export next Sunday’s dues, name S2/S3/S5 owners, and paste the Missed-Call Ladder into your branch handbook. On the following Monday, close S7 with a posted-receipt count and a PAR snapshot versus Friday. If you want borrower files, dues, role-scoped access, and repayment receipts in one login instead of chat threads, start at PesoLend login and map your rota to the staff you already have.