Identify the required Civil Defence document and the stage at which the building or completion application needs it. Plan preparation, reviews and responses for each application around those dependencies.
Put both approval routes in one programme
Coordination can reduce avoidable mismatches, but it cannot guarantee identical review times. A programme should show the technical inputs, official submission stages and outstanding responses for each application.
Gather the current application status
Ask for the current service details, the drawing status and any known dependencies. Record who owns each file and who communicates design changes between the teams.
Map the dependencies and responsibilities
List the deliverables
Name the document required from each organisation.
Map dependencies
Show which application waits for another document.
Track current actions
Record the status, next action and responsible person.
Update the programme
Revise assumptions when comments or scope change.
Allow for completion-stage requirements
For example, DDA’s fit-out completion service lists a DCD completion certificate among its documents. This is a specific dependency; it does not establish a universal timeline for all fire-safety NOCs or building permits.
Support with the approval programme
Gravity can help review the project information and coordinate the agreed design and approval scope. Explore the relevant service.