One of the most expensive mistakes in real estate is confusing visibility with readiness. A project may look active, sound credible, and attract buyer confidence long before its approval position is truly clear.

That gap matters because delays rarely begin with construction alone; they often begin much earlier, in the conditions attached to approvals that most people never read closely enough.

IOD in real estate sits inside that gap. It is not just a technical document in the approval chain, but also one of the clearest early signals of whether a project is actually prepared to move forward or still depends on unresolved compliance issues.

For buyers, investors, and even seasoned market watchers, understanding IOD is less about terminology and more about reading risk, timing, and project readiness correctly.

Key Takeaways:

• IOD is not a green signal; it is a structured list of conditions that must be satisfied before a project can legally transition into execution.

• The approval journey in real estate is sequential, and without clearing IOD conditions, a project cannot move to construction or secure subsequent approvals.

• The complexity of this stage lies in its dependencies, often involving dozens of conditions across regulatory, environmental, and infrastructure authorities.

• This is also where many delays begin, not because projects fail, but because compliance remains incomplete despite visible progress.

• For serious buyers and investors, IOD is less a document and more a signal. It reveals whether a project’s readiness is real or still conditional.

• From an execution standpoint, as seen in firms like BCD Group, the difference between approval and delivery lies in how effectively these conditions are cleared and aligned with on-ground execution.

What Is IOD in Real Estate?

IOD in real estate stands for Intimation of Disapproval, a term that sounds negative but is often misunderstood in practice. It does not mean a project has been rejected. It means the project has been reviewed and can move forward, but only after meeting a defined set of conditions.

The authority is effectively saying: the plans broadly comply, but execution cannot begin until specific regulatory, technical, and infrastructure requirements are fully cleared.

In that sense, IOD is less about permission and more about preparedness. It tells you what still needs to be resolved before the project can move into execution, and where delays are most likely to originate if those conditions are not met.

Once the definition is clear, the real question becomes where this stage carries the most weight.

Why IOD Matters More in Redevelopment Projects

In redevelopment, approvals are not just procedural checkpoints. They sit inside a much tighter risk environment, where decisions already affect residents, timelines, and execution commitments before a single visible step is taken on site. That is why IOD carries more weight here than it often does in new development.

In this kind of project, the real question is not whether the approval exists. It is whether the project is truly ready to move forward without causing delays, disruption, or distrust.

• Redevelopment begins with commitments already in motion. Residents may have vacated, temporary arrangements may already be in place, and any delay at the approval stage immediately affects people, not just paperwork.

• IOD becomes a readiness test rather than a routine milestone. It is the point where the project either moves closer to execution or reveals unresolved conditions that can slow everything down.

• Delays here do not stay isolated. In redevelopment, an approval gap can quickly ripple through relocation, sequencing, stakeholder confidence, and delivery timing.

• This is why the risk equation changes. What might feel like a manageable delay in a new project can become a much more serious operational issue in redevelopment, where the margin for error is far smaller.

• Operators with deep redevelopment exposure read this stage differently. In high-stakes urban projects, BCD Group approaches IOD as part of the larger execution-readiness picture, not as a formality to be cleared and forgotten.

That higher-stakes lens only makes sense when you see IOD inside the full approval sequence.

Where IOD Fits in the Approval Process (IOD vs CC vs OC)

According to government-backed municipal processes like the Digital India Land Records Modernisation Programme (DILRMP) and urban local body frameworks, approvals are structured to ensure compliance before, during, and after construction, not just at one stage.

This staged approach is why different certificates exist for different phases of a project. To understand where IOD fits, you need to see the approval flow as a timeline, not individual documents.

How the Approval Flow Works:

• IOD → Pre-construction stage (project reviewed, conditions defined)

• CC → Construction stage (permission to begin building)

• OC → Post-construction stage (permission to occupy/use)

Each step builds on the previous one. You cannot legally move forward without completing the earlier stage.

IOD vs CC vs OC (Clear Comparison)

What This Actually Means

These approvals are not interchangeable and serve as progress checkpoints:

• IOD shows what still needs to be done

• CC confirms you can now build

• OC confirms you can now use the building

Also Read: Real Estate Regulatory Authorities Development in India

The sequence looks simple on paper, but the actual process is where the complexity begins.

IOD Approval Process in India (Step-by-Step)

The IOD process is a multi-stage workflow involving submission, scrutiny, inter-departmental clearances, and compliance cycles. Each step builds toward making the project eligible for execution.

Step 1: Submission of Development Proposal

The process begins with the developer submitting a detailed building proposal to the municipal authority. This includes architectural drawings, land ownership records, and project specifications. The submission must align with local development control regulations and zoning norms.

Step 2: Preliminary Scrutiny by Municipal Authority

Once submitted, the authority conducts an initial review to check basic completeness and regulatory alignment. At this stage, incomplete or non-compliant applications are flagged early, preventing further processing delays.

Step 3: Detailed Technical Evaluation

The proposal is then circulated across multiple departments for technical scrutiny. This includes checks related to structural design, land use compliance, and adherence to planning norms. Different departments assess different aspects of the same proposal simultaneously.

Step 4: Site Inspection and Feasibility Check

Municipal officials conduct a physical site inspection to validate whether the proposed plans match ground conditions. This includes assessing access, infrastructure readiness, and feasibility of the development on the given plot.

Step 5: Identification of Required Clearances (NOCs)

Based on the evaluation, the authority identifies all external approvals required for the project. These may include clearances from fire authorities, environmental bodies, pollution control boards, and other regulatory departments, depending on project type.

Step 6: Issuance of IOD with Conditions

After review and inspection, the authority issues the IOD along with a detailed list of conditions and pending compliances. This document effectively outlines what must be fulfilled before the project can move forward operationally.

Step 7: Compliance and Resubmission Cycle

The developer must then obtain all required NOCs and fulfil the listed conditions, which may involve multiple rounds of submission and verification. This stage often determines the timeline of the project, as delays typically occur here.

Step 8: Eligibility for Next Approval Stage

Once all conditions are satisfied and verified, the project becomes eligible to move to the next stage of approval, where construction-related permissions are considered.

Must Read: Guide on How to Get Started in Commercial Real Estate Investing

Each step depends on paperwork that turns the process from conceptual into actionable.

Documents Required for IOD

A single IOD can involve 30–40 separate conditions and clearances, each linked to a different authority, each supported by specific documentation, before the project can move forward.

That complexity translates directly into the type and depth of documentation that needs to be submitted at this stage.

Here’s what is typically required:

• Land ownership and title documents
  Property card, sale deed, 7/12 extract, or conveyance deed to establish clear development rights over the land.

• Approved building layout and architectural plans
  Detailed drawings prepared by a licensed architect, aligned with local development control regulations and zoning norms.

• Structural design and engineering plans
  Certified structural drawings to demonstrate safety, load-bearing capacity, and compliance with construction standards.

• Non-agricultural (NA) permission and land use approvals
  Required where applicable to confirm that the land is legally permitted for development.

• No Objection Certificates (NOCs) from multiple authorities
  Depending on the project, this includes approvals from:

  • Fire department

  • Pollution control board

  • Environment authorities

  • Tree authority

  • Traffic and infrastructure departments

• Infrastructure and utility clearances
  Documentation confirming alignment with water supply, drainage, sewerage, electricity, and road access systems.

• Environmental and regulatory compliance reports
  Including environmental impact assessments or specific clearances for sensitive zones (e.g., coastal or protected areas).

For buyers, the more useful question is not what sits in the file, but what it signals about progress and risk.

What Should Buyers Check in an IOD Before Investing

An IOD is not written for buyers, which is exactly why it becomes useful if you know what to look for.

Here’s what to check:

• Timeline sensitivity of pending conditions:
  Not all conditions carry the same weight. Some can be cleared quickly, while others involve external authorities and longer processing timelines. Identifying which ones are time-intensive helps assess realistic delivery expectations.

Example: If the IOD mentions a pending fire NOC, it may take weeks to obtain. But if it includes environmental clearance for a large project, approvals can stretch into months. That directly shifts your possession timeline, even if construction appears ready to begin.

• External dependencies outside the developer’s control:
  Approvals linked to government bodies or third-party infrastructure often introduce uncertainty. These are not entirely within the developer’s execution control and can affect timelines unpredictably.

Example: If road access approval depends on a municipal infrastructure upgrade, the project cannot fully progress until that external work is completed, regardless of the developer’s readiness.

• Alignment with surrounding infrastructure commitments:
  Certain conditions depend on road access, utility connections, or civic upgrades. If these are tied to external development plans, project progress may depend on factors beyond the site itself.

Example: A project may have IOD approval but still be waiting for sewerage or water line connections. This means even if construction starts, completion and usability can get delayed.

• Phasing or partial approval indicators:
  Some projects receive approvals in phases. Check whether the IOD applies to the full project or only a portion of it, which can impact how and when different parts are executed.

Example: If only Phase 1 has cleared conditions, amenities, or later towers may be delayed, affecting overall livability timelines even if your unit is in the first phase.

• References to revisions or resubmissions:
  Multiple revisions in the document can indicate back-and-forth with authorities. This may suggest complexity in approvals or challenges in aligning plans with regulations.

Example: If the same condition has been revised multiple times, it signals friction in approvals, which often translates into longer pre-construction delays.

• Authority-specific conditions that carry higher scrutiny:
  Conditions issued by certain departments (environment, fire, and planning authorities) tend to have stricter compliance requirements and longer validation cycles.

Example: Environmental conditions tied to tree clearance or coastal regulation zones can stall projects entirely until resolved, even if all other approvals are in place.

Also Read: What Is Due Diligence in Real Estate?

When those signals are not read carefully, the consequences show up later in the project cycle.

Risks of Projects Without Proper IOD

In India, authorities can halt, penalise, or even reverse non-compliant developments, making this one of the earliest points where risk compounds.

Here’s how those risks typically play out:

That is why the next step is not assumption, but verification.

How to Verify IOD Status (Step-by-Step)

In most Indian cities, this process is now partly digitised through municipal portals, making it possible to track approvals without relying only on the developer.

Step 1: Ask for the Official IOD Copy

Start by requesting the actual IOD document from the developer or seller. This is not a summary. It should be the full document issued by the municipal authority, including file number, conditions, and approval references.

Step 2: Check the Municipal Approval Portal

Most urban local bodies provide online systems to track approvals for building proposals. Use the file number, developer name, or plot details to search.

You can verify IOD status through portals such as:

• MCGM AutoDCR Portal (Mumbai)

• BDA Online Building Plan Approval System (OBPAS) (Bangalore)

• HMDA Layout Approval Portal (DPMS) (Hyderabad)

• DDA Building Plan Approval System (Delhi)

These portals allow you to check whether the IOD has been issued and whether it is still under review or compliance.

Step 3: Use “Citizen Search” or Application Tracking Tools

Government systems (often called AutoDCR or DPMS platforms) allow public access to application data. You can:

• Search by application/file number

• View proposal stages

• Access approved certificates directly

This helps confirm whether the document shown to you matches the official record.

Step 4: Verify Approval Stage and Status

Check what stage the application is in:

• Submitted

• Under review

• Approved

The status tells you whether the IOD is fully issued or still in process, which directly affects project readiness. If the project is still “under scrutiny,” the IOD has not yet been issued. If it shows “conditions pending,” the project is stuck in the compliance phase.

Step 5: Cross-Check Conditions and Remarks

Many portals also allow tracking of NOC status and authority remarks. Reviewing these helps identify:

• Pending approvals

• Queries raised by departments

• Conditions still under review

This gives a clearer picture of how far the project has progressed internally.

Step 6: Validate Through the Local Authority (If Needed)

If anything seems unclear, the final check is with the municipal office or issuing authority. This can confirm authenticity, especially in cases where documents are shared offline or partially.

Once you know how to verify the document, the deeper question is how experienced operators read beyond it.

What Ashwinder R Singh (BCD Group) Focuses on Beyond Approvals

Most buyers think approvals are the finish line. In reality, many projects with the “right approvals” still face delays, redesigns, or execution issues later. The gap is not in paperwork; it’s in how decisions are made beyond it.

Ashwinder R. Singh, Vice Chairman and CEO of BCD Group, operates at exactly this intersection. With over two decades of experience across real estate, banking, and investments, spanning leadership roles at JLL, ANAROCK, Bhartiya Urban, and global banks like Citibank and Deutsche Bank, his work is shaped by both capital discipline and on-ground execution realities.

BCD Group itself has delivered over 150 million sq. ft. of real estate over 70+ years, working across construction, development, and infrastructure, giving it visibility not just into approvals, but into how projects actually move from plan to delivery.

From that vantage point, approvals are treated as a starting condition, not a validation of success:

• Execution readiness, not approval status:
  The key question is not whether approvals exist, but whether the project is operationally ready to move once they are in place. This is across contractors, funding, and sequencing.

• Alignment between planning and delivery capability:
  A project can be technically approved but still misaligned with the developer’s ability to execute at scale, especially in complex urban environments.

• Capital flow and funding continuity:
  With a background in structured finance, the focus extends to whether funding is aligned with project timelines, because execution slows down when capital does.

• Integration of multiple systems, not isolated approvals:
  Real estate projects operate across design, infrastructure, compliance, and construction. The real risk lies in how well these systems work together, not whether each one is individually approved.

• Long-term usability and outcome, not just completion:
  The focus is on whether the project will function as intended after delivery, across livability, infrastructure, and sustainability, not just whether it reaches completion.

To explore how thirty years of experience in capital markets and real estate development shape these outcomes, you can read the full biography of Ashwinder R. Singh.

Conclusion

In real estate, the real risk is rarely in what is visible. It is in what remains conditional, unresolved, or not yet fully understood. That is why IOD matters: not as a technical formality, but as a clear signal of how far a project has actually progressed and how much uncertainty still sits beneath the surface.

For buyers and investors, the lesson is simple. Do not confuse an active site with a fully ready project. Read the approval trail, understand the dependencies, and judge readiness before confidence becomes expensive. That is the kind of discipline experienced operators, including teams with execution depth like BCD Group, learn to value early.

For those who want to keep building that sharper lens on Indian real estate, Ashwinder R. Singh’s newsletter and masterclass are a natural next step.

FAQs

1. What happens after an IOD is issued in a real estate project?

After an IOD is issued, the developer must begin fulfilling the conditions listed by the municipal authority, which often include obtaining multiple No Objection Certificates (NOCs) and regulatory clearances. Only once these requirements are satisfied can the developer apply for the next stage of approval, typically the Commencement Certificate (CC). This phase can involve multiple rounds of submissions and corrections. The speed at which these conditions are met directly influences how quickly the project progresses. It is a transition phase where compliance determines momentum.

2. Why is IOD considered critical for legal compliance in construction?

IOD ensures that the proposed development aligns with zoning laws, building codes, and safety regulations before any physical work begins. Without it, the project lacks foundational legal validation and may be treated as unauthorised construction. Authorities use this stage to verify whether the project meets statutory norms across multiple departments. It acts as a safeguard against violations that could lead to penalties or demolition later. Compliance at this stage reduces legal exposure significantly.

3. What is the difference between IOD and IOA in real estate?

IOD (Intimation of Disapproval) and IOA (Intimation of Approval) are often confused, but their usage depends on local municipal terminology. In many Indian cities, IOD is the formal document issued after plan scrutiny, even though the name suggests “disapproval.” IOA may be used in some jurisdictions to indicate approval status more directly. The key difference lies in nomenclature rather than function. Buyers should always check how the local authority defines these terms.

4. Can IOD be rejected by authorities?

Yes, IOD is not automatically granted. If the submitted plans do not comply with zoning rules, safety norms, or development regulations, authorities can raise objections or reject the proposal. In such cases, developers are required to revise and resubmit their plans. This iterative process continues until the proposal meets all regulatory requirements. Rejection is part of the scrutiny mechanism, not an exception. It ensures only compliant projects move forward.

5. Does IOD apply to both residential and commercial projects?

Yes, IOD applies to both residential and commercial developments across urban India. Any project that involves construction within municipal limits must undergo regulatory scrutiny before execution. While the scale and complexity of approvals may differ, the requirement for initial validation remains consistent. Commercial projects may involve additional clearances depending on usage. The framework is universal, but execution varies by project type.

6. What are common challenges developers face during the IOD stage?

Developers often face delays due to incomplete documentation, zoning conflicts, or pending approvals from external authorities. Coordination across departments like environment, fire, and infrastructure can slow down progress. In some cases, regulatory changes or increased scrutiny can also affect timelines. Overloaded municipal systems in large cities further add to delays. These challenges make this stage one of the most time-sensitive in the approval process.

7. Can IOD affect investor confidence in a project?

Yes, IOD plays a role in shaping investor perception, especially in early-stage projects. A project that has progressed smoothly through initial approvals is generally seen as more credible. Delays or complications at this stage can raise concerns about execution capability. Institutional investors and lenders often track approval milestones before committing funds. This makes early-stage approvals an indirect indicator of project viability.

8. Is IOD required before applying for RERA registration?

Under regulatory frameworks like MahaRERA, developers are required to obtain key approvals before registering a project. While the Commencement Certificate is typically mandatory, IOD or equivalent building plan approvals are also considered part of the compliance framework. These documents demonstrate that the project has entered the formal approval pipeline. Without them, registration may not proceed. Approval sequencing is closely tied to regulatory compliance.

9. Can construction begin immediately after IOD is received?

No, construction cannot legally begin immediately after receiving IOD. The document outlines conditions that must be fulfilled before further approvals are granted. Actual construction activity is permitted only after obtaining the Commencement Certificate (CC). Starting work without completing these steps can lead to legal consequences. IOD is a preparatory stage, not an execution clearance.

10. How does IOD impact project timelines in real estate?

IOD plays a significant role in determining how quickly a project transitions into the construction phase. Delays in obtaining or complying with IOD conditions can push timelines forward significantly. Since multiple approvals are interconnected, any delay at this stage can have a cascading effect. Developers often prioritise this phase to maintain project schedules. Timeline predictability depends heavily on how efficiently this stage is managed.

11. Is IOD validity limited or time-bound?

Yes, in many jurisdictions, IOD approvals are valid for a limited period, after which extensions or revalidation may be required. If the developer does not act within this timeframe, the approval may lapse or require updates. This ensures that projects remain aligned with current regulations. Time-bound validity also prevents indefinite holding of approvals. Developers must plan execution timelines accordingly.

12. What role does IOD play in ensuring construction safety?

IOD ensures that the proposed project meets structural, environmental, and safety standards before execution begins. Authorities review aspects such as building design, fire safety provisions, and compliance with local regulations. This reduces the risk of unsafe construction practices later. By enforcing these checks early, the process helps maintain quality and safety benchmarks. It acts as a preventive mechanism rather than a corrective one.