Gargi
AtlasWalkthroughChainApp
Atlas›Stage 2 · Planning›M04 · Approvals
M04build

Approvals

State-by-state approval inventory, dependency tree, and structured tracking from submission to receipt.

What it is

Approvals are state-specific, ULB-specific, and project-type-specific. The approval strategy module owns the inventory — what approvals are needed for a given project — and the dependency tree showing how they sequence (S1 before IoD CC, RERA timing relative to GTM, EC parallel to S1). Status is tracked from submission to receipt with cycle-time predictions based on past projects in the same micro-market.

Inputs
Triggers
  • ·New project registered in M03
  • ·Approval submission package ready from Design
  • ·Authority correspondence received
  • ·IoD conditions issued by MCGM (or equivalent authority)
  • ·RERA filing deadline approaching per state policy
Data reads
  • ·Project record with location, type, segment, scope
  • ·Approval inventory per state, ULB, and project typology
  • ·Cycle-time history for each approval class from past projects in same micro-market
  • ·Design drawings and supporting documents from M07
  • ·MEP and structural calculations from M08
Artefacts consumed
  • ·Application drawings and supporting documents
  • ·Title and ownership documents
  • ·Statutory compliance certificates from various departments
  • ·Authority queries and clarification requests
Tools & Techniques
Methods
  • ·State-specific approval inventory and dependency tree
  • ·Parallel-track submission planning (where regulations allow)
  • ·IoD condition tracking with item-by-item closure workflow
  • ·Cycle-time prediction based on historical authority behaviour
  • ·Authority correspondence logging with response SLA tracking
Policies
  • ·approval strategy policy per state
  • ·IoD condition closure SOPs
  • ·RERA filing policy with timing rules
  • ·EC submission policy for projects above threshold size
Decision rules
  • ·Approval submission requires Design + Legal + Liaison joint readiness
  • ·IoD conditions all closed before CC application
  • ·RERA filing scheduled based on CC receipt forecast, not optimism
  • ·Parallel-tracking approvals requires explicit risk acceptance for cross-impacts
Outputs
Artefacts produced
  • ·Approval inventory and submission plan per project
  • ·Submission documents and authority correspondence file
  • ·Approval receipt records (IoD, CC, EC, RERA, etc.)
  • ·Cycle-time history fed back to authority intelligence
Data writes
  • ·Milestone register updated with submission and expected receipt dates
  • ·Approval status updated through lifecycle
  • ·CycleTime database updated on each approval receipt
Downstream triggers
  • ·Stage 1 approvals unlock RERA filing and pre-launch readiness
  • ·CC receipt unlocks site mobilisation in M16
  • ·EC receipt unlocks environmental compliance reporting workflows
  • ·Approval delays surface in PMC for schedule re-baselining
Stakeholders
  • LiaisonOwns approval inventory, strategy, submissions, tracking
  • DesignProvides drawings, calculations, and supporting documents
  • LegalRERA registration, regulatory documentation
  • PMOAnchors approval milestones into the project master schedule
The flow
  1. 01Identify all approvals required — based on state, ULB, project typology, stage
  2. 02Finalise approval strategy — sequencing and dependency tree
  3. 03Plan submissions — S1, parallel filings
  4. 04IoD compliance and CC — satisfy IoD conditions, secure Commencement Certificate
  5. 05EC documents and details — environmental clearance package
  6. 06RERA registration as per state timelines
  7. 07Receipt of Stage 1 approvals package required to commence pre-construction
State change
Before

Approval timelines are hopeful estimates; status is in heads, not on a record.

After

Every approval is a tracked item with submission date, expected cycle time, actual cycle time, dependency links.

Real-world example

Andheri project — 23 approvals identified across MCGM, MMRDA, and MoEFCC. IoD submission targets 16 May; expected cycle 6.2 weeks based on Borivali project history. RERA filing planned for week after IoD receipt. EC pack submitted today, tracked 8–10 week cycle.

Artefacts
  • ·Approval inventory by jurisdiction × project type
  • ·Submission documents
  • ·Authority correspondence
  • ·Approval receipt records
  • ·Cycle time history
Pain today

Approval knowledge lives in two or three Liaison heads. When that head is on leave, status questions go unanswered. Dependency tracking is manual — slippages cascade silently.

Integrations

No external system integrations — module operates on internal records.