Understanding the Hierarchy of Agreements: A, B, and MOU

The most common pitfall for agents is treating all pre-sale documents with equal legal weight. Understand this fundamental distinction: an MOU is merely an intent; an Agreement to Sell creates a contractual promise; and the Builder Agreement establishes the primary construction contract. Legally, only the Agreement to Sell and the Builder Agreement, when properly stamped and registered, confer immediate, actionable rights upon the buyer. Relying on an MOU when the developer promises possession within a defined timeline (mandated by MahaRERA guidelines) exposes both the buyer and you to significant litigation risk.

The Builder Agreement (or Agreement for Sale by Builder) is the foundational document. It mandates that the builder/promoter commits to construct the property according to specific plans registered with the local municipal body and, crucially, registered under MahaRERA. It must clearly delineate the structure of payment, the construction schedule, and the penalty clause for delays. Agents must confirm that the agreement references the specific MahaRERA Registration Number (e.g., MH/Pune/12345/2023) of the project in its preamble. If this number is missing or if the document relates to a project not yet registered, the agreement is void for compliance purposes.

The Agreement to Sell is generally issued by the seller (or promoter, acting as the seller) to the buyer, detailing the transfer of title or unit rights. While it is an essential commitment, its enforceability hinges on the completeness of the builder’s underlying documentation. Similarly, a simple Memorandum of Understanding (MOU) typically lacks the mandatory provisions regarding penalty clauses for delay (a core consumer protection right under RERA) and the detailed payment milestone structure required by law. Never permit a client to sign an MOU and treat it as a binding substitute for a legally reviewed Agreement to Sell.

Executing Document Due Diligence: A Step-by-Step Protocol

Before introducing any property, your role mandates a minimum of three stages of documentary due diligence. This process protects you from recommending properties based on ambiguous or outdated paperwork, and it must be completed before any earnest money or initial commitment fee is paid. Stage one involves verifying the promoter’s legal standing. You must confirm that the Promoter has a clean, verifiable corporate identity (Certificate of Incorporation, PAN, TAN, and valid KYC documents) and that the property title documents provided are current and free of encumbrances. Failure to verify title deeds (Sale Deeds, Conveyance Deeds, etc.) is a direct path to agent negligence complaints.

Stage two focuses on RERA compliance alignment. You must independently verify the project status on the official MahaRERA portal. The Promoter must present a valid, registered Builder Agreement and the Project Registration Certificate (under Section 3 of RERA). Crucially, cross-reference the details: Does the project name, area, and allotted unit description in the physical documents match the details listed in the MahaRERA registration record? If the documentation reflects a change in the developer or the project scope that is not updated on the MahaRERA portal, you must flag this discrepancy immediately to the client and the promoter.

Stage three is verifying the documentation chain of custody. The developer must provide the original draft agreements, which must show clear references to the specific legal sections they comply with (e.g., stating adherence to the payment schedule outlined in RERA guidelines). Always insist on reviewing the stamped and notarized versions of the legal documents. If the developer attempts to use a boilerplate agreement that doesn't reference the specific project registration number, treat it as a significant red flag requiring escalation to the consumer grievance cell.

Actionable Warning: If the developer is asking for payments based on an agreement not publicly available or not listed on the MahaRERA website, you must advise the client to pause transactions until the documentation is verified against the portal records.

Key Safety Check: Every document must include the specific project registration number issued by the relevant state authority. This number is the single most important piece of data for client safety.

Client Mandate: Never sign any document that does not clearly state the full legal addresses and legal names of all involved parties, the builder, and the developer.

The Responsibility: Your responsibility is to ensure that the documentation matches the official, public records. Do not accept vague promises; demand verifiable paperwork linked to the official registry.