Construction approval submissions are built from coordinated project information. Even when the design is technically sound, missing documents, inconsistent plot references, unclear drawing revisions or incomplete supporting details can slow the review process. A document-control system helps owners, consultants and contractors prepare clearer submissions and respond to authority comments efficiently.
Create a project approvals matrix
Start with a matrix listing every required permit, NOC, consent and technical review that may apply to the project. For each item, record the responsible authority, service name, submission channel, applicant eligibility, required input, dependency, target date and current status.
Keep confirmed requirements separate from items that are still being checked. This prevents assumptions from becoming project instructions and makes it easier to identify decisions that need confirmation from the authority or appointed consultant.
Build a controlled document register
Use a consistent naming convention for drawings and documents. A useful register records document number, title, discipline, revision, issue date, status, author and submission reference. Distinguish clearly between draft, for review, submitted, returned, approved and superseded documents.
Make sure the project name, plot number, location, owner and consultant details are consistent. Where a document is revised, record what changed and which related drawings or reports may also need updating.
Coordinate the main technical disciplines
Architectural, structural and MEP information should describe the same design. Check floor levels, dimensions, openings, equipment spaces, service routes, plant areas, external works and project areas across the disciplines. If one discipline changes an element, assess whether the change affects the others.
Specialist inputs may include fire and life-safety, access, traffic, utilities, geotechnical or environmental information depending on the project. Include only the reports and drawings required for the actual scope and authority checklist.
Prepare for electronic submission
Before uploading, check file names, formats, readability, page orientation, drawing scales, signatures or stamps where required, and the correct revision. Confirm that the portal fields match the supporting documents and that the application is being submitted by an eligible party.
Save the final upload set exactly as submitted, together with the portal acknowledgement and application reference. This provides a reliable baseline for tracking comments and preparing any resubmission.
Respond to comments and maintain an audit trail
Copy each authority comment into a response log, assign an owner and set a due date. The response should identify the action taken and the revised document. Where a comment affects multiple disciplines, coordinate the response before uploading a partial fix.
Keep the original submission, comment letter, response matrix and revised package together. This audit trail supports project coordination and helps the team understand which version is current and which approval conditions apply.
Practical preparation checklist
- Prepare an approvals matrix for the project and plot jurisdiction.
- Use consistent project identifiers and document naming.
- Maintain a revision-controlled drawing register.
- Coordinate architecture, structure, MEP and specialist inputs.
- Check the authority's latest file format and submission rules.
- Archive the exact upload package and acknowledgement.
- Track comments, owners, due dates and revised documents.
Frequently asked questions
Why do authority submissions get returned?
Possible reasons include missing information, inconsistent documents, unclear drawings or a mismatch with the applicable checklist. The actual reason is stated by the reviewing authority for each application.
Should every discipline use the same drawing revision?
Related documents should be coordinated so they represent the same design status. Keep a register to identify current revisions and superseded files.
Who should maintain the approvals tracker?
The project should assign a responsible coordinator, with each consultant or specialist accountable for their own technical inputs and responses.
Can a previous project's document checklist be reused?
Use it only as a planning reference. Verify the current authority checklist and project-specific requirements before submission.
Official resources and further reading
- Dubai Municipality – Building Permit Procedures
- DDA – Construction Permits and NOCs
- DEWA – Building No Objection Certificate
- DEWA – Infrastructure Projects NOC
How Keynes Group can support your project
Planning an approval submission is easier when the project team understands the applicable authority, required drawings, supporting documents and review sequence before filing. Keynes Group UAE provides approval-related coordination and project support in Dubai. Discuss your project scope, plot or community, proposed work and current drawing status with the team so that the appropriate route can be reviewed. Service scope and authority requirements depend on the project and the competent authority; approval decisions remain with the relevant authority. Visit Regulatory Approvals & Permits or Keynes Group UAE to make an enquiry.
Editorial note: Authority procedures, forms, fees, submission channels and technical requirements can change. Confirm the latest requirements directly with the competent authority before preparing or submitting an application. This article is general information, not legal or engineering advice.
