Title Verification Report Structure That Odisha Advocates Trust

A title verification report is an analytics output. It is not a legal opinion. The legal opinion on any property file in Odisha remains with the signing advocate. With that boundary clear, here is what a useful report contains and how to read it as an advocate.

The three input documents

Every Odisha title verification operates on three primary inputs:

• Record of Rights (Khatiyan) for the current Hal owner record, plus the Sabak record where present
• Encumbrance Certificate (Form 25) covering the relevant 12 to 30 year search window across sale-deed and mortgage categories
• Sale Deed Certified Copies for every transfer in the chain you intend to verify

A report that reconciles fewer than these three is incomplete. A report that ingests more (mutation orders, Bhu Naksha extracts, court records) is richer but the three above are the canonical floor.

{{EDUCATION_CTA}}

What the report must contain

Five sections, every time:

1. Document inventory. Page counts, OCR confidence per page, and any pages that failed extraction. A report that hides the inventory is hiding its limits.

2. Owner-name reconciliation. Every name appearing on every document, with exact match flagging across the chain. Khatiyan name vs Sale Deed seller vs EC chain. Variant spellings flagged separately from genuine mismatches. Maiden names, suffixes, parentage all surfaced.

3. Plot identity reconciliation. Plot number, Khata number, Mouja, Tahasil for each document. Sabak Hal correspondence read where applicable. Compound plot detection (568/896) with parent-child mapping. Boundary descriptions cross-checked when present.

4. Encumbrance status. Every entry from the EC walked in chronological order. Mortgages with discharge entries paired. Court orders flagged as separate from sale-deed events. Gaps in the EC chain (years with no recorded activity) called out explicitly.

5. Findings with severity grading. Every flag is critical, warning, or informational. Every flag cites the source document and page. The advocate decides whether each flag breaks the file or can be accepted in writing.

What the report must not do

A useful report respects the boundary of analytics versus legal advice:

• It does not certify ownership. The Khatiyan certifies ownership; the report just reads the Khatiyan against the chain.
• It does not declare a property safe to buy. The report surfaces facts; the advocate determines acceptability.
• It does not compress or summarise findings into a single yes-or-no verdict. Each finding is presented with its source citation so the advocate can verify the source independently.
• It does not synthesise documents that were not provided. A 10-year EC cannot answer questions about 1989 transfers; the report says so explicitly rather than guessing.

{{FEAR_CTA}}

Reading the severity grading

Three levels in order of seriousness:

• Critical means stop the registration. Examples: seller name does not appear on Hal Khatiyan; double registration of the same plot to different parties; subsisting mortgage with no recorded discharge.
• Warning means resolve before closing or accept in writing with the buyer's informed consent. Examples: Sabak record references a different Khatiyan from the Hal record without a Settlement-era correspondence entry; mutation order pending as of the EC search date; partition deed visible but not yet propagated to the Khatiyan.
• Informational means note in the file. Examples: plot is sub-divided into compound numbers; Kissam classification is agricultural and conversion has been ordered but receipt is pending.

Citations are the trust contract

A finding without a citation is a guess. A useful report carries:

• The document name and the SRO or IGR reference where applicable
• The page number where the finding originated
• Where relevant, the line number or paragraph reference
• A direct quote of the language that triggered the flag, when the language is the basis of the finding

Citations let the advocate check the source rapidly. They also let the buyer's counsel cross-examine the finding without re-reading the entire 200-page chain.

What an advocate still does after the report lands

The report compresses the legwork. It does not replace any of these advocate functions:

1. Confirm jurisdiction. Plot numbers are unique within a Mouja. The report's plot identity check assumes the Mouja and Tahasil are correctly stated; the advocate confirms with the seller.

2. Read the corner cases. Power of Attorney chains, probated wills, partition deeds where one heir is missing: the report flags these but cannot adjudicate the ramifications.

3. Check court records outside the SRO. Lis Pendens registered only at the District Court will not appear on the EC; advocate-led court search remains essential.

4. Sign the legal opinion. The advocate signs. The report is the workpaper.

Real Odisha case patterns where the report changed the outcome

A buyer in Cuttack received a clean buyer-side opinion from a non-specialist lawyer. The Title Verification report flagged a mortgage entry from 2019 with no registered discharge, even though the Sale Deed bore a manuscript loan-closure endorsement. The Sub-Registrar required the registered release deed before mutation; the buyer obtained it; the transaction proceeded clean.

A buyer in Khordha had three separate Sale Deed CCs covering a property that had passed through partition between siblings. The report mapped Sabak 78 to Hal 142 to compound plot 568/896 across four documents. Without the structured chain, the advocate was reconciling the same chain from memory across multiple meetings; with the report, the chain is on a single page.

What to ask of any title verification tool

If you are evaluating tools, three questions:

1. Does the report cite source pages for every finding?

2. Does the tool decline to certify safety, leaving the legal opinion with the advocate?

3. Does the tool process all three primary documents (RoR, EC, Sale Deed CCs) and reconcile across them, or does it process them in isolation?

The third question separates structured chain reconciliation from document-level OCR.

{{FINAL_CTA}}