A guarantor who exists only as a name on a crumpled photocopy will not save your loss rate. Guarantor workflow small lenders Philippines teams need is the boring path from co-maker intent to a file you can act on — without turning every close into a three-day pilgrimage. This is commercial origination hygiene, not a capital-plan essay and not a week-one delinquency sermon.
Product-safe framing: use borrowers CRM fields, document vault habits, and clear process steps. Guarantor and co-maker data live as file fields and verified contacts. Do not claim full electronic signature tooling as live. Soft path: PesoLend features keep borrower and loan files together so officers stop hunting co-makers in group chat.
Why guarantor process dies at close speed
Officers optimize for the handshake. Guarantor KYC close rate collapses when the co-maker must appear twice, bring three IDs, and wait while the cashier invents fields. Then managers blame “lazy officers” instead of a clumsy workflow. Loss rate guarantor policy MFI shops want has to be fast enough that officers use it on ordinary ₱8,000–₱20,000 tickets, not only on scary ones.
In Quezon City and Davao desks, the winning pattern is capture co-maker identity early, verify reachability once, store consent text, and only escalate to in-person when ticket size or risk tier says so.
Minimum co-maker workflow that still books loans
- Capture at application: full name, mobile, address with barangay, relationship, primary ID type/number.
- Reachability test: call or SMS once before approval. Dead numbers fail the gate.
- Consent note: short statement that they understand they may be contacted for collection support. SMS reply “YES” with date stamp is enough for many thin ops shops.
- File link: co-maker attached to borrower and loan — not floating in a shared Drive folder named “final2.”
- Exception path: manager can waive co-maker on tiny tickets with a reason code; waivers report weekly.
That is co-maker LMS workflow as practice. It cuts loss rate without killing close speed because most of it happens before the borrower is sitting at the till expecting cash in five minutes.
Tiered rules by ticket size
Example tiers many PH small lenders recognize (tune to your appetite): small ticket gets reachable co-maker plus ID details and SMS consent; mid ticket adds co-maker ID image in the vault and a manager glance; high ticket needs in-person acknowledgment or stronger dual control with no same-day waive. Publish peso thresholds internally. Do not invent marketing prices in public posts. The point is speed matching risk.
Where loss rate actually improves
Guarantors help when they are real humans who answer the phone and care about reputation in the barangay. Measure percent of loans with co-maker phone that connects on first try, percent of DPD-15 accounts where co-maker contact was attempted within 48 hours, and charge-off rate on loans with versus without completed guarantor pack in the same ticket band. If the pack is complete but never used in collections, you bought paperwork, not loss reduction.
Exception rules that still book loans
Allow exceptions with reason code, manager name and timestamp, and a compensating control such as lower ticket, shorter tenure, or denser early reminders. Weekly exception reports keep honesty. Unlimited exceptions recreate the old chaos.
What not to invent on day twenty
Skip claiming live full electronic signature products, offline field apps, predictive scoring of guarantors, or polished borrower portals. You need CRM fields, file storage, SMS or call notes, and approvals. That is enough to cut loss without freezing the queue.
Keep learning on-site: first 90 days, second loan cross-sell, why PesoLend, features.
14-day install
- Freeze the minimum field list; remove decorative fields officers skip.
- Require reachability tests before approval on mid and high tiers.
- Turn on weekly waiver reports.
- Spot-check ten files; coach consent language; celebrate faster closes that still have complete packs.
Target: co-maker reachability above 90% on new mid-ticket loans, without adding a full day to average time-to-cash.
(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.
Scripts collectors can use with co-makers
Keep the first co-maker call calm and short: introduce the lending desk, confirm relationship, confirm they agreed to be contacted if the borrower stalls, and thank them. Log the outcome. On DPD-5, a second call can ask for help reaching the borrower — not for immediate payment theater. Harassment destroys barangay reputation and future close rates. Polite persistence with a dated note beats shouting.
Train officers in Tagalog and Cebuano variants of the same script so tone stays consistent across Quezon City and Cebu desks. Record which script version was used in the loan note when the ticket is mid or high.
File hygiene checklist for co-makers
Before disbursement on mid tickets, a second pair of eyes confirms: number rings, ID fields complete, consent note dated, relationship not “friend TBD,” and waiver reason present if any field was skipped. That two-minute glance prevents the loss-rate mystery three months later when nobody can find who the co-maker was supposed to be.
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.
Closing
Guarantor workflow that cuts loss rate without killing close speed is early capture, reachability, consent on file, tiered depth, and exceptions with names. Keep it inside borrower and loan records. Skip signature mythology until your thin ops are boringly reliable.
Run that file discipline from https://pesolend.com/app/login.