Understanding the jurisdiction
First establish the actual plot or unit jurisdiction. A nearby project may have followed a different process.
One of the first questions is not “Which form do we fill?” It is “Who has jurisdiction over this property, and what exactly is changing?”
EMARC Engineering Consultant L.L.C. · Dubai, UAE
Two properties can be a short drive apart and fall under different approval processes. A change that one authority treats as a straightforward fit-out may be a building modification in another jurisdiction—or under the same authority if it changes the use, structure or gross floor area. Starting with last year’s checklist from another project can send the team in the wrong direction.
EMARC’s authority-approval consultancy begins by establishing the available facts: plot or unit details, existing approvals, proposed work, landlord or master-developer conditions and the discipline documents that may be required. Under the agreed appointment, the team can coordinate technical submissions, document tracking and responses to reviewers.
Approvals are made by the relevant authority, not by a consultant. Requirements can change; a complete-looking file does not guarantee acceptance or a particular processing time. The value of early coordination is understanding which decisions remain open and who is responsible for closing them.
Speak with our teamFirst establish the actual plot or unit jurisdiction. A nearby project may have followed a different process.
Some applications depend on earlier consents, drawings or NOCs. The order matters as much as the checklist.
A reviewer needs to know which revision is current. Keep superseded drawings out of the submission set.
Every open comment needs an owner and a due response; so the project team knows what is still outstanding.
There is a difference between a landlord NOC, a technical design approval, a permit to start work and a completion certificate. A sound project programme accounts for each relevant stage.
Before an application is prepared, we identify the property jurisdiction, proposed work and responsible applicants. The appointment sets out which submissions, document checks and follow-up tasks EMARC will handle.
Identify the jurisdiction, proposed works and current approval position before making any submission assumptions.
Map the likely permissions, drawing responsibilities and dependencies with the owner and appointed consultants.
Compare architectural, structural and MEP records for consistency and the correct revision before issuing files.
Organise the appointed application material and help the authorised applicant meet the relevant portal or document requirements.
Keep comments and responses tied to specific drawings so the team can see what has changed and why.
Report what is submitted, what is under review and which decisions or documents are still needed from others.
A useful coordination record shows what is ready, what is missing and who must act next. The final document list is specific to the project and its reviewing bodies.
An initial route map explaining the identified authority stages and where additional confirmation is required.
A project-specific list of available and missing documents—not a recycled generic submission checklist.
Named responsibility for key drawings, signatures, owner consents and required follow-up activities.
A record of reviewer observations and the technical team’s responses or revisions.
A live status summary distinguishing received, pending, resubmitted and formally accepted items.
Confirm the jurisdiction and application stages before assembling the file. Keep each submission, comment and revision tied to the relevant drawing issue.
Locate the property in the correct authority framework and define what is actually being proposed.
Identify the stages, prerequisites, responsible parties and relevant document sets.
Check completeness and revision consistency with the consultants preparing the technical material.
Coordinate authorised filing and responses to review observations within the appointment scope.
Record each authority outcome and clarify the conditions or next steps before the project moves forward.
The same property can require a different application when its use or structure changes. The examples below explain why the scope needs to be checked before selecting a submission route.
New developments may involve design stages, NOCs and construction permits that need to be planned together.
Commercial premises require checks on approved use, landlord conditions and the works proposed within the existing unit.
Extra floor area, process changes or warehouse alterations can affect which technical application is appropriate.
A proposed extension or internal alteration should be checked against prior approvals and community conditions.
Suppose a tenant plans new partitions, extra electrical equipment and a small kitchen. The project team needs to identify whether the existing use permits that operation, whether ventilation and drainage can be accommodated and whether the works fall under a fit-out or modification process in that specific jurisdiction.
With those answers, the team can assemble a realistic list of drawings, consents and responsibilities instead of promising an approval before the design is understood.
These questions help separate consultant coordination from decisions made by authorities, utilities and property stakeholders.
It depends on where the property is located and what work is proposed. Dubai Municipality and Dubai Development Authority publish different building and design services, and some projects involve other zones, master developers or utilities.
Application eligibility depends on the authority, professional licence, appointment and project scope. EMARC can review the project and confirm its proposed consultancy role, including where an authorised specialist or applicant is needed.
Requirements vary according to the work, use, fire-safety impacts, existing building permissions and relevant landlord or jurisdiction rules. Confirm applicable permits before construction or occupancy changes.
No. A No Objection Certificate from a utility or other stakeholder may be one prerequisite within a wider approval sequence. The necessary set of NOCs varies by project.
In many workflows reviewers request amended documents or additional details. The team should understand each observation, check its impact on connected drawings, and submit a consistent revised set using the correct channel.
No. Processing time is influenced by statutory review, external comments, document readiness, scope changes and third-party requirements. Published service estimates should not be represented as guaranteed outcomes for a particular project.
Provide the location, existing approval information and a short list of proposed changes. We can help identify the questions that must be settled first.
Confirm requirements on the official service page for the property’s jurisdiction. A published checklist or time estimate is not a guarantee for an individual application.
Use these guides to prepare the initial project information and recognise changes that may need additional technical review.
For the first conversation, read our guide to preparing an authority submission.
Tell us what you’re planning and where you need clarity. Our Dubai team is ready to discuss your engineering and authority-submission requirements.