Turnaround Benchmarks for Property Verification at Indian Banks

Put the same question to ten heads of mortgage operations in India, and you will hear ten answers about their property verification SLA. One gives the vendor TAT. Another gives the file TAT. A few cite the contractual SLA that nobody tracks. What banks publish and what borrowers experience are far apart, and that gap is where many NPAs caused by legal defects quietly sit.

Realistic benchmarks for PSU banks, private banks, NBFCs and HFCs in India are given below. Clean-file TAT is kept apart from messy-file TAT, the bottlenecks that recur in audit after audit are named, and a best-in-class SLA is described with the noise removed.

Meaning of a property verification SLA

By contract, the turnaround time (TAT) of a property verification SLA is the period within which the bank's empanelled legal vendor, internal team or technology partner has to return a title search report (TSR) or legal scrutiny report (LSR) on property offered as mortgage security. Counting starts when loan operations hands over a full set of documents and ends when the signed-off report sits in the loan origination system (LOS).

What a panel agreement states and what happens on the ground are seldom the same. Measurement differs from bank to bank, and few separate the 'vendor clock' from the 'file clock', a distinction behind most of the friction between credit operations and legal vendors.

Where SLAs stand today, by type of lender

Our view of mortgage operations in AP, Telangana, Karnataka, Tamil Nadu and Maharashtra in 2025-26 produced these benchmarks. Treat them as typical and not exact, because branches differ widely.

• PSU banks · Promised: 7-10 working days · Clean files take 8-15 days in practice · Messy files take 18-30+ days · Typical choke point: collecting the EC, and rounds of scrutiny review
• Mid-size private banks · Promised: 5-7 working days · Clean files take 6-10 days in practice · Messy files take 12-20 days · Typical choke point: how many files a panel advocate can take
• Large private banks (top 3) · Promised: 3-5 working days · Clean files take 4-7 days in practice · Messy files take 10-15 days · Typical choke point: waiting in the internal credit committee queue
• Top-tier NBFCs · Promised: 3-5 working days · Clean files take 4-8 days in practice · Messy files take 10-18 days · Typical choke point: heavy load on few vendors, and cases that age
• HFCs (large) · Promised: 5-7 working days · Clean files take 6-12 days in practice · Messy files take 15-25 days · Typical choke point: re-scrutiny driven by NHB
• HFCs (mid/small) · Promised: 7-10 working days · Clean files take 10-15 days in practice · Messy files take 20-30+ days · Typical choke point: reliance on a single vendor
• Cooperative banks · Promised: 7-14 working days · Clean files take 12-20 days in practice · Messy files take 25-40+ days · Typical choke point: every step done by hand

Two patterns hold for every kind of lender. First, there is a wide spread between clean-file and messy-file TAT, usually 2x to 3x. Second, the SLA in the panel agreement was set years ago and nobody has compared it with real throughput since.

What causes the spread

The spread in TAT has causes, and operational audits find the same few in almost every case.

• Manual collection of the encumbrance certificate (EC): A panel clerk goes to the Sub-Registrar's Office in person, or works the state portal. EC retrieval online is decent in AP and TS and workable on Maharashtra's IGR portal, but many other states still need physical pickup or a hybrid. This step alone adds 1-4 working days.
• Checks on eCourts and lis pendens: These are left to the panel advocate's discretion, so they are often skipped or run only at district level. When a junior clerk does them, coverage is patchy. Done properly, they should run in parallel and automatically, not one after another by hand.
• Rounds of scrutiny review: The advocate sends a draft, the bank's internal legal officer returns queries, the advocate replies, and another round starts. Each round costs 2-3 working days. Most files see 1-2 rounds, and bad files see 4-5.
• Queue at the internal credit committee: Reports wait for a legal officer's review or credit committee sign-off. The delay is on the bank's side, but MIS attributes it to the vendor.
• Gaps in documents: The mother deed is missing, the parent document cannot be read, mutation is pending, or a partition deed is mentioned but not produced. A vendor cannot give a clean opinion on an incomplete file.
• Dependence on one vendor: Many HFCs and cooperative banks send 60-80% of files through a single panel advocate, and every month-end spike in workload breaks the SLA.

For more on what banks need in a verification report, see our property verification guide for banks and NBFCs and the wider property due diligence checklist for India.

What best-in-class looks like

A vendor brochure is not the source of the best-in-class number. It comes from running the workflow in a structurally different way, and the teams that reach it today share four traits.

• Clean files in under 24-48 hours: When the title chain is complete, all government portal data is available and there are no court flags, a verified opinion should return in 24-48 hours. Parallel automated checks across EC portals, eCourts, RERA, mutation records and the 15-20 government sources that matter mean retrieval of data stops being the bottleneck. Legal review of clean data becomes the only step that takes time.
• A predictable 5-7 days for messy files: Files with litigation flags, a partial chain or encumbrance disputes should still close in 5-7 working days, because the exception is found within hours, not days. The clock runs from resolution and not from discovery.
• Measuring on the file clock, not the vendor clock: The best teams measure from 'file received in operations' to 'signed report in LOS'. They allow no carve-outs for 'waiting on customer', 'waiting on legal officer' or 'waiting on advocate response', since those are what the SLA is meant to expose.
• Tiered SLAs published to the panel: Not one figure for everything, but separate SLAs by file type, geography and ticket size. Vendors and operations alike know what they commit to.

The home loan property due diligence workflow at a bank should follow these tiers directly. Without tiers every file is treated alike, and the worst case sets the average.

Measuring SLA properly: file clock against vendor clock

Vendor-clock TAT is what most banks report, since that is what the panel agreement penalises, and it leaves 40-60% of the real delay out of sight.

• File-clock TAT · Measures: the time between first touch in operations and the signed report in LOS · Importance: borrowers and front-line RMs feel this one
• Vendor-clock TAT · Measures: the time from file handover to the vendor until the draft comes back to the bank · Importance: the panel agreement imposes penalties on this one
• Net active TAT · Measures: the total of touch time with every 'waiting on' period removed · Importance: it shows whether the workflow is fast by design
• Cycle count · Measures: how many review iterations the file goes through between bank and vendor · Importance: it is the leading indicator of how mature the process is
• Exception ratio · Measures: the percentage of files sent to an exception queue · Importance: it is the leading indicator of how good the source of truth is

Mortgage operations rarely report the difference between file clock and vendor clock. A private bank that is well run shows a difference of 20-30%, while in a badly run cooperative bank it can be 100-200%. Customers there live through something 2-3x worse than panel MIS suggests.

SLA tiers that banks should publish to vendors

A panel agreement should publish four or five separate SLAs and not just one. A useful tier structure runs like this.

• Tier 1 — Ordinary residential, clean papers, project registered under RERA: 2-3 working days. Expect the bulk of your volume here, and the simplest automation.
• Tier 2 — Ordinary residential resale that needs a 13/30-year title chain: 4-5 working days. Human review earns its keep in this tier. (The reasoning is in our piece on 13-year vs 30-year title chain.)
• Tier 3 — Plots and land, agricultural conversion, or mutation still pending: 7-10 working days. Complexity is real, chains run longer and more papers are in local languages.
• Tier 4 — Commercial, industrial or large-ticket cases above ₹5 crore: 10-15 working days. Several vendors review, two legal opinions are sometimes taken, and the internal credit committee must sit.
• Tier 5 — The exception queue, covering litigation, lis pendens and SARFAESI auction property: 15-25 working days with named milestone checkpoints. (Background reading: pending court cases via eCourts, and the SARFAESI Act property guide.)

When the tier structure is published to the panel, SLA changes from a single contract number into an operating language, and both sides know their commitments.

Triggers for internal escalation

A working SLA framework needs triggers for escalation as well as deadlines. These catch problems early.

• +50% of the tier SLA gone, with no draft received: Escalate automatically to the vendor's partner level, because most slippage can still be recovered here.
• First review cycle runs past 48 hours: Flag automatically to the legal officer's manager, since slow first cycles compound quickly.
• 3+ review cycles on one file: Flag automatically to the head of operations. It signals either a poor file or a gap in vendor capability, and both need attention.
• Vendor concentration above 25% of monthly volume: A capacity warning. Set up a second vendor for that geography or product before the next quarter.
• Re-opens after disbursal: A legal defect that appears after disbursal goes straight to audit. This is the most expensive kind of failure and is nearly always a bypassed check and not a missed risk.

Banks of middle size with a legacy LOS usually produce these triggers as weekly Excel reports. The best banks show them on real-time dashboards, with operations, credit and legal heads all looking at one screen.

How automation alters the SLA discussion

Most bottlenecks in the list above come from retrieving documents, not from legal judgment. Judgment means deciding whether a title chain holds, whether a lis pendens is material and whether an encumbrance is discharged, and there the panel advocate adds real value. All the work that comes before is mechanical and can run in parallel over 15-20 government portals.

The SLA discussion looks different now that AI leads verification. LegiScore, for example, checks eCourts (28 states, 600+ districts), state EC portals, RERA registrations, mutation records and lis pendens databases in parallel, in under 15 minutes, and delivers a structured 29-section report that the panel advocate reviews and signs. Judgment takes the advocate's time and data entry does not. A fuller comparison of both approaches is in AI property verification vs manual due diligence.

No one is trying to remove the lawyer. The aim is to stop paying lawyer rates for clerical work, and to stop clerical work from setting the SLA.

First fixes if your SLA is slipping

• For one quarter, measure the file clock and not the vendor clock. Most banks find the gap far bigger than they assumed.
• Build the tier structure even before you change vendors. Tiering alone cuts 15-20% off effective TAT, as messy files no longer drag clean ones down.
• Automate the retrieval layer (EC, eCourts, RERA, mutation) in the geographies that count most. AP, TS, KA, TN and MH are the easiest to automate in India today.
• Cap vendor concentration at 25% per geography, and build redundancy before a month-end wrecks your SLA MIS.
• Publish escalation triggers to operations, legal and credit together. SLA is not just a problem for vendors.