This guide shares practical operations habits for Philippine money lenders, lending companies, and small MFIs. It is educational, not legal or credit-policy advice. The borrower names, times, and peso amounts in the worked example are illustrative only.
When a borrower asks, “Bakit ang tagal ng loan ko?”, most small lenders answer with a feeling: the CI was busy, the manager was out, the documents were incomplete. A loan turnaround time tracker replaces that feeling with five timestamps per application, so you can see exactly which step ate the days. You don’t need new software to start. You need agreed stage names, one owner per stage, and the discipline to stamp the time when a file moves.
This article gives you the stage map, the columns to log, a worked example from a two-officer branch with the arithmetic shown, a copy-ready setup checklist, a 20-minute weekly review, and the traps that make turnaround numbers look better than the borrower’s actual experience.
Who this is for (and who can skip it)
This is for branches and field teams that approve more than a handful of loans a week and hear repeated “follow-up” calls from applicants. It also helps owners of multi-branch books who want to compare branches fairly instead of guessing who is slow.
If you release fewer than five loans a month and the owner personally handles every file, a tracker is overhead you probably don’t need yet. Write the dates on the folder and revisit this when volume grows.
The five stages to timestamp
Turnaround only means something if every branch splits the journey the same way. Use these five stages and write each definition on the wall of the loan desk so nobody invents their own.
| Stage | Starts when | Ends when | Owner |
|---|---|---|---|
| 1. Intake | Applicant submits the form | File is complete (all required IDs and documents received) | Loan officer |
| 2. Verification | File marked complete | KYC, credit investigation, and reference calls are done | Credit investigator |
| 3. Decision | Verification signed off | Approver records approve, decline, or counter-offer | Branch manager or credit committee |
| 4. Documentation | Decision recorded | Promissory note, disclosure statement, and schedule are signed | Loan officer |
| 5. Release | Documents signed | Cash handed over or transfer confirmed | Cashier |
The single most important rule: Intake ends when the file is complete, not when the form arrives. If you start the verification clock on an incomplete file, the investigator gets blamed for waiting on a missing barangay clearance that the applicant hasn’t brought yet.
The columns your tracker needs
Whether you keep this in a loan management system or a shared sheet, each application should carry these fields:
- Application ID and branch.
- Five stage-end timestamps (date and time, not just date).
- Stage owner names, so a stall has a person attached to it, not a department.
- Pause reason from a short fixed list: waiting on applicant, waiting on guarantor, approver unavailable, cash not available, system down, other.
- Pause start and end, so “waiting on applicant” time is separated from desk time. A file can have more than one pause; log each on its own line.
- Outcome: released, declined, withdrawn by applicant, or expired.
Two numbers come out of this. Elapsed time is what the borrower felt, from form to cash. Desk time is elapsed time minus applicant-caused pauses. You need both: desk time tells you where your process is slow, and elapsed time tells you why applicants walk to the next lender.
Calendar hours or business hours?
Decide this once, before the first entry, because it changes every number. Calendar time is simpler and matches what the borrower lives through: a file that sits from Saturday noon to Monday morning really did wait two days. Business time (only the hours your branch is open) is fairer when you compare officers, because nobody can verify a reference on Sunday.
Our suggestion for small lenders is to record calendar timestamps and report both. Raw date-and-time stamps let you compute either view later. If you only record “business days,” you lose the borrower’s view forever. Whatever you pick, write it at the top of the tracker so a new branch manager doesn’t quietly switch methods and make last quarter look slow.
Worked example: a two-officer branch
Here is an illustrative week for a ₱15,000 working-capital loan to a sari-sari store owner we’ll call Aling Rosa. She drops off her form on Saturday at 11:00 AM, but her proof of address is missing. She brings it on Monday at 2:00 PM. Times below are calendar time.
| Stage | Ended | Elapsed in stage | Pause logged |
|---|---|---|---|
| Intake | Mon 4:10 PM | about 53 hours | Waiting on applicant: proof of address, Sat 11:00 AM to Mon 2:00 PM (51 hours) |
| Verification | Tue 3:00 PM | about 23 hours | None |
| Decision | Thu 10:00 AM | 43 hours | Approver unavailable: field visits Tue–Wed |
| Documentation | Thu 2:30 PM | 4.5 hours | None |
| Release | Fri 9:15 AM | about 19 hours | Cash not available: vault below release threshold Thu PM |
Now the arithmetic, because this is where the tracker earns its keep:
- Elapsed time from Saturday 11:00 AM to Friday 9:15 AM is about 166 hours, or 6.9 days. That is what Aling Rosa felt.
- Applicant pause was 51 hours. Subtract it and desk time is about 115 hours, or 4.8 days.
- Decision plus release took 43 + 19 = about 62 hours, or 2.6 days, more than half of all desk time.
- Intake and verification together used about 25 hours of desk time once the applicant pause is removed.
Notice what that means. The officer and the investigator were not the bottleneck. The decision queue and the vault were. Without timestamps, the branch would have coached the wrong people, probably the officer who took the borrower’s angry follow-up call.
The fixes are specific. The manager can name a backup approver for files under a set amount on field-visit days, and the cashier can check the next day’s approved releases against the vault before closing, so cash is ordered in time. Our guide on building a cash position board for branch managers covers that second habit in detail.
Copy-ready setup checklist (first two weeks)
Most trackers die in week two because nobody agreed the basics. Use this list to start clean:
- Day 1: Write the five stage definitions above, plus your calendar-or-business-hours choice, on one page. The branch manager signs it.
- Day 1: Fix the pause-reason list. Six reasons is plenty; “other” must carry a one-line note.
- Day 2: Name one owner per stage per branch, plus a backup for the decision stage.
- Day 2: Decide who stamps each time. The rule is that the person handing the file off stamps the end of their stage.
- Days 3–10: Log every new application, including declines and walk-aways. Do not back-fill older files; start fresh.
- Day 7: Spot-check five files against the physical folder or the system record. Fix definitions now, not after a month of bad data.
- Day 14: Run the first weekly review below, and write down your median desk time per stage as your own baseline.
That baseline matters more than any outside number. Lenders differ too much in loan size, product, and geography for a borrowed industry “standard” to mean much. Beat your own median first.
The 20-minute weekly review
Every Monday, the branch manager pulls last week’s released and declined files and answers four questions:
- Which stage had the longest median desk time? Use the median, not the average, so one stuck file doesn’t hide the pattern.
- What were the top two pause reasons? If “approver unavailable” keeps showing up, that is a delegation problem, not an officer problem.
- How many applications were withdrawn, and at which stage? Withdrawals after Decision usually mean the borrower found money elsewhere while waiting for release.
- Which three files took longest, and why? Read them one by one. The notes will tell you more than the averages.
Write one action per week, with an owner and a date. One fix that sticks beats five that are forgotten by Wednesday.
Reading the numbers: symptom, likely cause, first fix
After a few weeks the patterns repeat. This table helps you avoid fixing the wrong thing:
| What the tracker shows | Likely cause | First fix to try |
|---|---|---|
| Long intake, mostly “waiting on applicant” | Requirements explained late or verbally | Hand over a printed requirements list at first contact |
| Verification fast on Mondays, slow by Thursday | Investigator also covers collections later in the week | Protect two fixed CI blocks per day |
| Decision delays cluster on the same days | Single approver doing field visits | Written backup approver and approval limits |
| Withdrawals spike after decision | Borrower found money elsewhere while waiting for release | Same-day or next-morning release cut-off |
| One branch is slow on every stage | Staffing gap or different stage definitions | Audit five files before blaming the team |
Mistakes that make turnaround look better than it is
- Back-filling timestamps on Friday. If officers reconstruct times from memory at the end of the week, the data turns into fiction. Stamp the time when the file moves, or let the system do it.
- Dropping declined and withdrawn files. If you only measure released loans, you never see the applicants who gave up. Withdrawals are often your clearest turnaround signal.
- Counting “waiting on applicant” as desk time, or the reverse. Both distort the picture. Log pauses honestly and report both numbers.
- Speeding up by skipping checks. A faster release that skips a guarantor callback or the amortization walkthrough just moves the problem into collections. Pair this tracker with a guarantor contact recheck before release and an amortization preview before disbursement, so speed and quality move together.
- Ranking branches on raw elapsed time. A rural branch whose applicants travel far to submit documents will always look slower. Compare desk time instead.
A simple decision framework
Once you have four weeks of data, use the slowest stage to decide what to fix first:
- Intake is slowest: give applicants a one-page requirements checklist at first contact, and don’t accept a form until it’s complete. Our field KYC checklist is a good starting point.
- Verification is slowest: batch reference calls into two fixed time blocks a day, and route field CI by barangay instead of by order received.
- Decision is slowest: set written approval limits so smaller, clean renewals don’t wait for the branch manager. A maker-checker setup keeps that safe.
- Documentation is slowest: pre-print the disclosure statement and schedule at decision time so signing is the only step left.
- Release is slowest: plan cash a day ahead from the approved queue, and agree a same-day release cut-off with the cashier. Our piece on disbursement cut-off times walks through how to set one.
Don’t speed up the documentation stage by cutting the disclosure
When Documentation looks slow, the tempting fix is to release first and sign later. Don’t. Under the Truth in Lending Act, Republic Act No. 3765, Section 4, a creditor must give the borrower a clear written statement of the credit terms before the transaction is consummated. The tracker should make that step faster, for example by preparing the statement and schedule at decision time, never make it optional. If your stage definition says Documentation ends when the disclosure statement is signed, a release timestamp that comes before it is a red flag worth checking in your weekly review.
Frequently asked questions
What is a good loan turnaround time for a small Philippine lender?
There is no single figure that fits every lender, and we don’t recommend copying one. Turnaround depends on loan size, whether a field CI visit is required, and how far applicants travel. Measure four weeks of your own median desk time per stage, then set a target that improves on it.
Should declined applications count toward turnaround?
Yes. A slow decline still costs the applicant time and costs your desk effort. Track declines through the Decision stage, and track withdrawals at whatever stage the applicant walked away.
Can we start with a spreadsheet?
Yes. A shared sheet with the columns above works for a single branch. It gets harder across branches because timestamps are typed by hand and definitions drift. That is usually the point where keeping stage dates inside the loan record pays off.
Who should own the weekly review?
The branch manager, because most fixes (approval limits, backup approvers, cash planning) are theirs to make. For multi-branch lenders, the operations head should see every branch’s desk-time medians side by side once a month.
How PesoLend helps
Keeping loan records, approvals, and disbursements in one loan management system such as PesoLend means the dates live with the loan file instead of on sticky notes and officers’ phones. Branch maker-checker approval on disbursement and an audit trail make it clear who moved a file and when, so the Monday review starts from what’s already recorded instead of a spreadsheet rebuilt from memory. Existing teams can log in to PesoLend to review their loan records.
What to do next
This week, agree on the five stage definitions with your team and start stamping times on every new application, including the ones you decline. Hold your first 20-minute review next Monday, pick the single slowest stage, and fix only that. In a month you’ll know where your days really go, and so will the borrowers who stop calling to ask.