The 9 PM Applicant: Why Home Loan Files Sit in Queues

Picture an applicant who uploads the last paper at 9 PM. Nothing is missing, so the legal checks could begin right away. Instead the case rests until staff arrive next day, gets logged, then waits for data entry, then for an advocate, then for a reviewer. When a person finally begins, eight hours of the clock have run and none of them produced a single result.

Hardly any lender tracks this gap. They record time-to-complete, while the real drag on TAT is time-to-start.

What Makes Legal Verification Hold Up Home Loans?

Handoffs, not effort. Examining a straightforward property needs only a few hours of legal reading. Yet the case takes days or weeks, since between the applicant's upload and the signed final opinion it joins four or five separate lines. In each line, one person is finished and the next has not yet reached for the case.

Working alongside a lending operations team, we split a single case into stages and timed each. The lawyering was skilled and genuine; the idle time around it caused the trouble. Industry sources publish 3 to 10 working days for legal and technical verification of completed properties, 7 to 15 working days for home loan processing overall, and 30 to 60 days from start to finish. Pull those figures apart and the bulk is waiting, not scrutiny.

Two Kinds of Time: Touch and Queue

In loan processing, turnaround time (TAT) means the calendar span from a borrower's submission until the lender sends back a decision or report. Within it sit two kinds of time that look alike on a calendar but act differently. Touch time covers the hours when someone is actually working on the case. Queue time covers the hours when the case is ready and lying between people with no one assigned.

Counted honestly, an opinion on a clean title consists mostly of touch time: reading documents, tracing ownership, running encumbrance and litigation searches, and writing conclusions. Skilled work of that sort fills a few hours. Applicants still wait a week because their case spends most of its life in queue time. It is complete at intake yet idle before data entry. It is complete at data entry yet idle before an advocate. It is complete with the advocate yet idle before review. Trim touch time and hours come back; trim queue time and whole days come back.

One Verification Cut Into Stages

Below is the case as we logged it, hour after hour.

Stage one, intake queue. Submission arrives at 9 PM and is whole, but the desk is unmanned, so nothing moves until 9 AM. Twelve hours pass without any touch time. No other block in the case is as dead, and most dashboards hide it because their timer begins when an employee opens the case rather than when the borrower completed it.

Stage two, retyping from the LOS. A loan officer copies property and applicant particulars (address, survey number, owner name, document references) out of the bank's loan origination system into the verification form. The typing is a quarter of an hour. Afterwards comes a return trip whenever a swapped digit in the survey number sends the case back. Little time is spent, but errors and rework loom large.

Stage three, checking the papers. An associate confirms that all documents are present and readable. Half an hour of genuine effort follows, and then the case enters the advocate line.

Stage four, waiting for an advocate. The case is ripe for legal review but no advocate is free. Depending on workload, it sits for between half a day and two days, untouched.

Stage five, the legal scrutiny. An advocate studies title, ownership chain, encumbrances, litigation and approvals. Two to four hours of concentrated, useful labour produce the item the bank pays for.

Stage six, awaiting review. A draft opinion sits until a senior reviewer is available, and is then examined. Again there is waiting and a small dose of work.

Add up active effort over all six stages and it comes to the better part of one working day. Add the idle spans and you reach the week the applicant experiences.

Retyping: A Hidden Double Cost

Re-entering data hurts twice. There are the minutes spent typing, and then the mistakes: a survey number off by a digit, one applicant named two ways, an address unlike the one in the LOS. Each mismatch throws the case back into a line it had already cleared. This information already lives in the bank's loan origination system, so making someone retype it into a second one asks for lateness and errors at once.

Here waiting disguises itself as effort. Typing feels like progress, but the return trip it triggers is wasted time.

The Effect of Event-Driven Processing

More typists and more advocates will not fix idle time. What helps is removing the person who must open the case before anything starts. With event-driven processing, work begins when the system registers an event, not when an employee spots the case. Once a submission satisfies the requirements, the report starts. No morning shift, no line and no twelve-hour hole.

LegiScore offers this as Auto Start. If a borrower submits at 9 PM with every requirement satisfied, the report begins at 9 PM rather than next morning. For a case that arrives complete, the whole intake wait vanishes, which is stage one above and the largest dead block. Nights, weekends and public holidays no longer store idle cases. Time-to-start, the clock that counts, drops from hours to nothing.

It also keeps the remaining pipeline honest. If start time no longer depends on who is on shift, the leftover TAT is the actual work and internal handoffs, a far smaller and more controllable total.

Ending the Retyping Step With LOS Connectors

Data re-entry stops being a queue once both systems exchange information directly. Using LegiScore's LOS connectors, a loan officer enters a case ID and presses fetch, and property and applicant details move from the bank's loan origination system into the intake form. There is no retyping, no swapped survey digit and no return trip. Teams who want tighter integration can add REST APIs, signed webhooks and embeddable widgets, letting a newly completed case start verification with no one at a screen.

So the connector shortens TAT twice over: the typing minutes disappear, and so does the rework that typing mistakes cause. Information the bank already holds travels once and cleanly, with no second keying or recheck.

Prefill Plus Human Sign-Off: What Auditors Look For

For a regulated lender, automation that replaces human judgment is a concern. Automation that replaces typing yet keeps a person confirming is just what auditors expect to see. LegiScore's AI document prefill reads uploaded papers and populates the intake form. Before submission it displays each AI-extracted field with an "AI extracted" tag, open to edits. The loan officer reviews property description, consideration, stamp duty, registration particulars and document category as the system interpreted them, and can amend any item.

The difference is meaningful. Software does the extraction so no one retypes, and a human approves it so the file holds a defensible record of who signed off on what. Lenders gain speed without losing the control that credit and risk functions require. After the intake is confirmed, LegiScore delivers a 29-section legal opinion within 15 minutes of processing, at Rs.499 per report for bulk volumes.

Queue-Based Against Event-Driven Verification

• Time-to-start: hours or up to a day under queues, because someone must open the file; zero under event-driven flow, which starts when requirements are satisfied
• Submissions at night or on weekends: queued cases are held until the next working day, while event-driven ones start immediately, regardless of staffing
• Data entry: queue-based teams retype from the LOS; event-driven ones fetch by case ID through the LOS, an API or a webhook
• Entry mistakes: transposed digits send queued cases into rework; with event-driven flow the data travels once, untyped
• Audit trail: queued cases depend on handwritten notes; event-driven cases record each AI-extracted field, plus its edit and confirmation
• Source of TAT: mostly waiting in queue-based flow, mostly working in event-driven flow

Better Measures Than TAT-to-Complete

Operations heads looking for the days concealed in their TAT should quit reporting time-to-complete alone and add time-to-start. That figure is the span between a borrower's case becoming complete and anyone first working on it. A queue-driven shop shows a large, awkward number there, yet no dashboard displays it because the timer begins at case open. Event-driven processing shuts precisely that gap.

Four measures are enough. Time-to-start per case comes first. Next is the re-entry error rate, the proportion of cases returned for data fixes. Third is the proportion of submissions received outside office hours, a sign of how much free idle time your model creates. Fourth is touch time as a share of total TAT, revealing how much turnaround is labour and how much is waiting. When touch time is a small slice, handoffs are the problem, and extra hiring cannot repair a handoff problem.

What TAT Is Reasonable to Expect

A clean property with a full document set has no sound reason to take a week, because the legal examination is only a few hours. Once auto-start cancels the intake wait and LOS connectors cancel the retyping wait, a same-day finish is a fair target for a clean case, the rest being the advocate's real examination and a single review. Tangled titles, projects still being built and files short of documents will run longer, and rightly so, as they involve genuine work and risk. Nobody is asking for hurried scrutiny. The goal is to stop making borrowers pay in time for hours when nobody was working.

Compared with the published range of 3 to 10 working days for legal and technical verification, a pipeline that begins at submission and imports data without retyping turns the clean-case outcome from days into hours. Hard cases remain slow for honest reasons, and easy ones stop waiting on rosters.