Sabak Hal Correspondence Reading: Odisha Advocates' Guide

The Sabak Hal correspondence column on the Odisha Khatiyan is the single most useful artefact in chain-of-title work. It maps pre-Settlement (Sabak) Khata and plot numbers to their post-Settlement (Hal) equivalents. When the column is filled correctly, an advocate can trace ownership across decades in minutes. When the column is partial or missing, the advocate must reconstruct the correspondence from the underlying Settlement record. This guide is for the second case.

What the correspondence column is

Each row of the Hal Khatiyan typically carries:

• The Hal Khata number and the Sabak Khata number
• The Hal plot numbers and the Sabak plot numbers (or the Sabak parent plot for sub-divisions)
• The Sabak owner name where it differs from the Hal owner

The column exists because Settlement operations renumber plots, occasionally renumber Khatas, and adjust boundaries. A property that existed before Settlement has a Sabak identity; the same property after Settlement has a Hal identity. Both are valid; the chain runs through both.

{{EDUCATION_CTA}}

When the column is filled correctly

A typical clean entry reads: Sabak Khata 78, Hal Khata 142, Sabak plot 142, Hal plot 568. The reading: a property previously held under Khata 78 with plot 142 is now held under Khata 142 with plot 568. Same land, two numbering schemes. The owner column will indicate whether the Hal owner is the Sabak owner or a successor.

When the column is partial

Three common partial states:

1. Hal entry only, no Sabak. Means the property came into existence after the most recent Settlement. Look at the original allotment or partition deed; there is no Sabak record because there was no pre-Settlement state.

2. Sabak entry only, no Hal. Means the property was acquired during Settlement, partitioned and recorded only under successor plots, or the Hal record has not yet been digitised. Pull the Tahasildar paper Khatiyan; the Hal entry usually exists offline even when the online portal is silent.

3. Both columns filled but the names differ without an intervening transfer. This is a chain break that requires reconstruction. Either a transfer document is missing from the chain, or a Settlement-era correction order changed the recorded owner. Pull the Settlement record and the Tahasildar's correction file.

When the column is wrong

Sabak Hal correspondence rows are entered manually during Settlement. Errors happen. Three error patterns to watch:

Plot mis-mapping. The Hal record claims to map to Sabak plot 142, but the boundary description matches Sabak plot 156. The error usually shows up because adjacent properties carry overlapping or mismatched correspondence entries. Cross-check by pulling the Sabak Khatiyan for both plots and comparing the boundary descriptions.

Khata mis-mapping. Sabak Khata 78 maps to Hal Khata 142 in one row but to Hal Khata 168 in another row. The error means a Sabak Khata holder's properties were split during Settlement but the correspondence was inconsistently entered. The property's actual current owner depends on which Hal Khata holds the specific plot you are tracing, not on the Khata-level correspondence.

Compound plot ambiguity. Sabak plot 142 maps to Hal plot 568/896. The 896 fragment could be the seller's portion, or it could be a sibling's portion held under a different Khatiyan. Pull both Hal Khatiyans (568/896 and 568/anything-else) before trusting any single row.

{{FEAR_CTA}}

Reading boundary descriptions to confirm correspondence

When the correspondence column itself is doubtful, boundary descriptions are the next-most-reliable artefact. Khatiyan rows include north-south-east-west neighbour identification (typically by neighbouring plot number or by named landmark like "abuts road" or "abuts Khata 78"). A property's boundaries do not change during Settlement; only its administrative identifiers change.

If the Sabak boundaries match the Hal boundaries, the correspondence is the same property regardless of what the correspondence column says. If the boundaries materially differ, the correspondence is wrong and the advocate cannot rely on it.

Compound plots: the trap that catches buyers

Compound plot numbers (parent/child, e.g., 568/896, or letter-suffixed like 142/A/2) almost always indicate Settlement-era partition. The parent plot exists in Sabak; the child plots come into being post-Settlement.

Three rules for compound plots:

1. Each child plot has its own Khatiyan entry. Always pull the specific child Khatiyan, not the parent.

2. The child Khatiyan owner may differ from the parent Sabak owner. Partition reorganises ownership.

3. The child plot's area is a fraction of the parent's; check the area on the Hal Khatiyan against the buyer's intended area before relying on the deed's parent reference.

When to escalate to the Tahasildar's paper file

Three triggers for escalating to the Tahasildar's paper Settlement record:

1. The Hal Khatiyan is silent on Sabak correspondence and the chain you are verifying spans more than 25 years

2. The boundary descriptions disagree with the correspondence column

3. The correspondence column references a Sabak Khata or plot that does not appear on bhulekh.ori.nic.in

The paper Settlement record is the source of truth. The online portal is a digitisation; gaps and errors do exist. Tahasildar offices retrieve paper records on application; turnaround is typically 7 to 21 days.

Real Odisha case where Sabak Hal saved the file

A buyer in Khordha was offered a property with a Sale Deed from 1989 referencing Plot 142 under Khata 78. The current Bhulekh search returned no record for Plot 142 in the Mouja. The buyer suspected fraud. The Title Verification report mapped Sabak 78 → Hal 142 (Khata) and Sabak plot 142 → Hal plot 568 via the correspondence column. Same property, two numbering schemes. The transaction proceeded once the chain was reconciled.

A buyer in Cuttack assumed a similar mismatch was administrative but missed that the Hal record showed plot 142 had been subdivided into 142/A (seller's share) and 142/B (sibling's share). The Sale Deed described the parent plot 142 in full. The legally transferable area was only 142/A. Without the compound plot detection, the buyer would have paid for property the seller could not legally convey.

What to ask of any tool that automates Sabak Hal reading

Three questions an advocate asks:

1. Does the tool surface the Sabak entry, the Hal entry, and the correspondence row, side by side?

2. Does the tool flag compound plot numbers and require the matching child Khatiyan?

3. Does the tool flag boundary description mismatches between Sabak and Hal as a separate finding?

Tools that compress the read into a single "ownership verified" verdict miss the cases above.

{{FINAL_CTA}}