For Mumbai projects, municipal approvals form a critical part of the construction record. IOD, CC, OC and related correspondence should be easy to retrieve for sales, legal, finance and completion work.
Why this matters
Approval documents often contain conditions and linked plans. Keeping the certificate without the conditions, drawings or follow-up correspondence creates an incomplete record.
What to organize
- IOD, commencement certificate, occupation certificate and completion-related records
- Approved plans, amendments and drawing revision history
- Conditions, NOCs and linked departmental approvals
- Inspection reports, compliance submissions and acknowledgements
- Authority correspondence, deficiency memos and replies
- Internal responsibility matrix for each approval condition
A practical workflow
- Keep approval certificates and their conditions in the same project file.
- Track every condition as an action with an owner and due date.
- Link revised drawings to the approval they respond to.
- Record submission and acknowledgement dates for authority follow-ups.
- Review open approval conditions before sales, disbursement or handover milestones.
How DigiProVault helps
DigiProVault can organize MCGM records under the project with related tasks and version history. Teams can see which approval conditions are closed and which still need action.
What do IOD, CC and OC mean in Mumbai projects?
IOD generally refers to the Intimation of Disapproval, CC to the Commencement Certificate and OC to the Occupation Certificate. Each should be stored with its conditions, plans and correspondence.
Why should approval conditions be tracked as tasks?
A certificate may depend on conditions that need later action. Task tracking assigns each condition an owner and due date instead of leaving it inside a PDF.
What should be linked to each MCGM approval?
Link approved plans, amendments, NOCs, inspection records, deficiency replies and internal responsibility notes to the approval record.