Loan File Tracker: Know Where Every File Is Stuck and Why

A loan file is a relay. It passes between the applicant, the desk, the lender's sales contact, credit, technical and legal, and back again. Each handoff is a place where a file can sit for a week with nobody accountable. The tracker exists to make that waiting visible while it is still recoverable.

How it is done today

The common setup is one Excel sheet per month, a WhatsApp group per lender, and an executive who knows the files by applicant name. It works at low volume because one person is holding the state in their head, and it fails on the first day that person is unavailable.

The characteristic symptom is the status call. An applicant rings to ask where their file stands; the executive says they will check and calls the lender contact. That round trip is entirely avoidable, and it is the clearest sign that the file record is not being updated as events happen.

File header

• File ID, applicant and co-applicant, with mobile and city.
• Product — home loan, loan against property, business loan, personal loan, balance transfer.
• Lender and lender relationship manager for this file.
• Amount requested and, later, amount sanctioned.
• Rate offered and tenure, with processing charges noted.
• Source — reference, builder, existing client, campaign — recorded once.
• Owner on the desk, and the referrer if any.

Process fields

• Stage and stage-entered date, plus days in stage calculated.
• Login date — the clock most turnaround measures start from.
• Document checklist per item, with status and format.
• Query log — raised by, date, description, closed date.
• Technical and legal status, tracked separately for secured products.
• Sanction date, disbursal date and tranche where disbursal is staged.
• Expected payout percentage and amount, and payout received.
• Outcome — disbursed, rejected, withdrawn, moved to another lender, with reason.

An illustrative example for a small desk running eight live files, not benchmark data. The board is sorted by days in stage, descending, which is the order the morning review should follow.

The last column is the one that makes this board useful, because it names the party that owes the next action. Two of these files are waiting on the applicant, three on the lender, and one on the desk itself. Those are three different conversations, and without that column a manager treats all eight as the same kind of delay.

Files stop belonging to individuals

With a shared pipeline, any executive can pick up a case with the full stage history, open queries and document status visible. Leave and attrition stop being events that freeze half the book.

Applicant updates become automatic

Stage-triggered WhatsApp messages at login, sanction and disbursal remove most status calls. The applicant is better informed and the desk gets its afternoon back.

Payout stops relying on trust

Expected payout calculated on disbursal, compared with receipts, produces a short list of cases where the amount is short or missing. That reconciliation is difficult to do from memory and trivial to do from records.

A single status column

Overwriting the stage removes the ageing data that tells you where files die.

No named party for the pending item

Pending is not a status. Pending with whom is a status.

Queries handled verbally

An unlogged query is answered twice or forgotten, and either way the turnaround number becomes indefensible.

Ignoring rejected files

Rejections carry the most useful information on the desk: which profile fails with which lender. Record the reason, not just the outcome.

Continue with lead management software, CRM with a built-in dialer, WhatsApp CRM, CRM vs Excel, best CRM in India, and the tools library.