Fifty Officers, Twelve Branches, One Standard: Ending Uneven Legal Scrutiny

Last year a credit policy head at a mid-size housing finance company ran a small test. From three branches in one state she collected three legal scrutiny reports on the same kind of property, a self-occupied flat financed by a housing loan. The product, the sanction band and the regulator were identical.

Nobody would have guessed the reports were related.

The first advocate had traced title for 30 years and noted a missing link deed. The second had gone back only 13 years, called the title clear, and said nothing of the link deed gap, since his format had no place for it. The third wrote a two-page note, attached a scanned encumbrance certificate and added one line: "Title found in order." Three branches gave three depths, three formats and three opinions that a credit committee cannot set side by side.

Many multi-branch lenders have this problem and few measure it. The legal work is not bad. It is inconsistent.

What makes legal opinions differ from one bank branch to another?

The causes are an absent template, wide discretion for panel advocates, and regional habits in title search that people take for personal style and not for gaps. Each branch tends to empanel its own advocates, and each advocate applies what he learned locally. Nobody higher up says what "scrutiny" must include, so the minimum is whatever each advocate thinks is enough.

Named, the mechanics are simple. No shared report structure exists, so two advocates may both be "thorough" and still write documents with almost no fields in common. No search period is defined, so one goes back 30 years and another 12, each sure he is right. State differences are real, since title in Telangana works unlike title in Maharashtra, yet without a standard they conceal true inconsistency. Risk ends up recorded in dozens of private dialects that the bank cannot read as one language.

Across our work standardising legal verification for lenders at LegiScore, the commonest finding is not error but that two correct opinions on near-identical properties cannot be compared structurally.

The True Cost of Inconsistency

The cost lands in four places, and the legal fee is not among them.

Audit findings are the first. When an internal auditor or RBI inspection samples files across branches, formats that drift look like a weak process, because a repeatable scrutiny standard cannot be shown if each advocate used a personal one. Our guide to audit readiness for bank legal verification explains the exposure in detail.

The second cost is risk that cannot be compared. A portfolio review needs like-for-like data. If Branch A's reports flag link-deed gaps and Branch C's never look for them, the overall risk picture is fiction. You are measuring which advocates happened to look, and not the portfolio.

Training overhead is the quiet third. Each new branch credit officer learns to read whatever the local advocates produce. With no institutional standard to onboard against, tribal knowledge multiplies and does not build up.

Slow turnaround is the fourth. Where formats differ, every report needs a person to interpret it before a credit decision, and sanction timelines stretch. Our piece on property verification SLAs for Indian banks benchmarks realistic targets.

The Usual Cure Is a Circular, and It Does Not Last

The standard institutional response is a circular: issue a master format, require a 30-year search, attach a sample template and tell all panel advocates to comply.

It holds for about a quarter.

A circular is a document and not a control. It relies on each advocate reading it, remembering it and applying it across hundreds of files under deadline pressure. Nothing enforces it at the point of work, exceptions go through "call the branch manager," and no audit trail shows the standard was followed and not merely circulated. When the format must change, another circular goes out and the bank waits for an adoption that never fully comes.

The alternative is to build the standard into the tool that produces the report, so that compliance is structural and not voluntary. That is the gap between a standard you announce and one you enforce.

• How it's enforced · Circular-based standardization: Left to each advocate to read and recall · Configuration-based standardization: Built in, since no report can be produced outside the defined standard
• Handling exceptions · Circular-based standardization: Unrecorded phone calls as and when · Configuration-based standardization: An override on one report, logged against the org default
• How fast it changes · Circular-based standardization: Another circular and months of patchy adoption · Configuration-based standardization: Edit the org default once and it applies to the next report
• Proof for auditors · Circular-based standardization: "We sent the memo" · Configuration-based standardization: Each report names the scenario and rulebook behind it
• Regional differences · Circular-based standardization: Hidden within advocate discretion · Configuration-based standardization: Written into named scenarios for each state and product
• New branches · Circular-based standardization: The local format must be taught again · Configuration-based standardization: The org standard applies from the first day

Defining a Verification Scenario

A verification scenario works like a stored recipe for one kind of report: depth of title search, mandatory checks, expected documents and report layout. Take a housing loan title search in Telangana, a farm plot check in Karnataka and a litigation check on a Mumbai commercial property. These are three separate tasks, and the scenario captures the difference once so nobody decides it afresh for every file.

This unit removes inconsistency at its root. A bank need not rely on each advocate recalling that agricultural land in Karnataka needs PTCL and Land Reforms Act checks and a city flat does not, since the scenario already holds that logic. Pick it, and the report knows the depth and checks to apply. What used to be discretion in 50 separate heads becomes a definition the institution owns.

On the LegiScore platform every report runs against a scenario. When a new report starts, the system picks the likely scenario from the property and loan type, and the officer may change it. Our legal scrutiny SOP checklist for mortgage approval explains why checks are defined per report type.

Organisation Defaults: A Single Standard With Room to Flex

Scenarios hold the logic, and organisation defaults decide which logic is used by default in the whole institution. At that level consistency turns automatic and stops being a hope.

At the organisation level, a default fixes both the custom-field setup and the scenario that is picked automatically. Any officer in any branch who opens a new report therefore starts from the same point. Fifty officers across twelve branches who open a new housing loan report receive the same scenario, mandatory fields and search depth, and none of them has to choose. The standard is how every report begins, not something a person opts into.

The override is where flexibility lives. A particular file might need a custom field that the org default lacks, a section turned off, or a different scenario because the property is unusual. Per-report overrides on the custom-field section let that one report differ with no change to the organisation-wide setting. The difference is logged against the default, so an exception remains visible as one and does not dissolve into advocate discretion. That gives you a single standard for the 95% and a deliberate, recorded route for the 5%.

Here is the change-management point to dwell on. A standard enforced through configuration needs no circular and no retraining, and it does not wear away. You edit the default once, and the next report in every branch reflects it.

Custom Fields: The Data Your Credit Committee Really Wants

The standard set of 150-plus data points in a thorough title search forms the legal core: chain of title, encumbrances, search period, litigation and statutory clearances. They answer whether the property is legally safe to lend against.

They do not answer the further questions your own credit committee asks. These include internal loan reference numbers, originating branch codes, the relationship manager who sourced the file, and a flag for whether the property lies in a panel-approved project. Such data belongs to the institution, and a generic report format has nowhere to put it.

Custom fields collect these additional points next to the standard set. They are set once at org level and can be overridden on a single report. Instead of a standalone PDF that somebody re-keys into the loan origination system, the legal opinion becomes a structured record already carrying your internal references. Lenders running LOS-integrated verification workflows can then pass the legal report into the credit file without manual stitching.

The Knowledge Base: Writing Each Opinion to Your Own Rulebook

Here standardisation passes from format to substance, because a consistent format with inconsistent reasoning is still inconsistent.

A knowledge base stores your institution's own rules inside the platform. That means internal credit policy, the land laws of the states where you lend, and precedents your legal team has settled. Opinions are then drafted against that rulebook and not against whatever each advocate knows or remembers.

Statute supplies the legal basis. Karnataka's agricultural land transfers come under the Karnataka Land Reforms Act, 1961 and the PTCL Act, 1978, and an opinion that skips them is wrong, not just thin. The Registration Act, 1908 and state registration records establish encumbrance, while the Transfer of Property Act, 1882 sets what a valid transfer requires. Encode them in the knowledge base and every branch's report stands on the same legal floor, topped by your internal credit policy as the institution's overlay.

That settles the opening problem. The scenario sets the depth, the org default applies it, and the knowledge base provides the legal reasoning, so three branches that gave three depths give one. In in-house legal teams versus outsourced due diligence we compare this approach with the alternative.

How the Configuration Stack Fits Together

The four parts stack in order, and each solves one layer of the inconsistency.

Think of it in order. A scenario sets how one type of report is built. The org default picks the scenario and fields used across every branch unless a real exception calls for a per-report override. Custom fields hold the data your credit committee wants beyond the legal standard. And the knowledge base is the rulebook behind each opinion, which makes the reasoning as uniform as the layout.

A completed report on the LegiScore platform runs to 29 sections, takes under 15 minutes, and notes the scenario and rulebook that produced it, evidence a circular cannot provide. The same configuration serves one file or hundreds, as covered in bulk property verification at 500 files a day, and reducing mortgage loan turnaround with automated legal scrutiny describes the effect on sanction speed.