Research updates

New research and corrections dated 18–20 October 2026. These pages retain source dates and limitations; they do not recover missing historical originals.

• Ambala: Do not treat a proposed collector-rate publication as a final assessment
• Delhi agricultural land: establish the village’s legal and planning status
• Faridabad: Read the plan legend and boundary before valuing road-side land
• Ghaziabad: a draft land-use map is not a parcel permission
• Greater Noida: identify the project as well as the village
• Gurugram: Choose the planning area before assessing agricultural use
• Jhajjar: Use the local schedule rather than one district-wide land rate
• Jind: A zone-specific permission cannot be generalised to surrounding farmland
• Karnal: Separate enduring record-office functions from undated acquisition anecdotes
• Noida agricultural land: follow the village-specific acquisition record
• Nuh: Read the correct tehsil schedule and distinguish it from a draft
• Palwal: Match the revenue locality before using a valuation or corridor claim
• Panipat: Read the status of the plan, not just the proposed use label
• Rewari: Keep proposed valuation schedules separate from confirmed transaction costs
• Rohtak: Use the record office to connect ownership entries with the map
• Ropar/Rupnagar: connect the land record to the acquisition stage
• Sonipat: Check both the planning area and any boundary-record issue
• Auction cash planning: read the notice before committing
• Commercial property in Gurugram: evidence before a shortlist
• Industrial property in Gurugram: separate the record from the parcel
• NRI home loans: what a lender's file actually contains
• A development agreement needs a dated tax analysis
• NRI property: separate acquisition, tax and remittance decisions
• Gurugram plot records answer different questions
• Compare the actual letting, not an undated rent range
• An SCO label does not establish tenure or return
• Land-record research: four jurisdictions, different entry points