Authority / NOC Coordinator

NOC Coordinator Jobs in Dubai – Job Overview

Applicants exploring NOC Coordinator Jobs in Dubai can consider the Authority / NOC Coordinator vacancy at Tarrad Development. The role relates to ongoing and upcoming high-rise building projects in Dubai, UAE. The notice lists Suite 28, U Bora Tower, Business Bay, Dubai as the address. This position concerns authority approvals and no-objection certificates, commonly called NOCs, within construction project coordination.

Job description

The following workflow explains general authority coordination practice, rather than employer-specific duties. Work usually starts by linking planned construction activities to the approvals they need. The coordinator reviews the project scope, design stage, and available approval records. Next, they identify which submissions depend on earlier permissions or technical information. This helps prevent a submission from reaching an authority before the supporting details exist. For a high-rise project, several design disciplines may affect the same approval. So the coordinator checks dependencies with the responsible consultant or project lead. The result is a clear sequence of submissions, with owners for missing information.

Before submission, the coordinator gathers the documents relevant to that particular approval. These may include drawings, technical statements, and forms, depending on the authority's requirements. They compare drawing numbers and revision dates across the package. However, document collection alone does not establish that the design meets technical rules. The responsible technical specialist must resolve design questions before the package moves forward. The coordinator also checks that supporting records refer to the correct project and scope. If a required item is missing, they identify its owner and request it. This gives the reviewer a consistent package rather than several conflicting versions.

Checks and exception handling

Once the package is ready, submission creates a record that needs active follow-up. The coordinator keeps the submission reference, date, document revision, and any receipt together. Then they track whether the authority has accepted the package for review. Acceptance for review does not necessarily mean approval to start the related work. That difference matters when the site team asks whether an activity can proceed. The coordinator reports the actual status and refers permission questions to the responsible lead. Meanwhile, they follow up on outstanding responses using the relevant authority's process. Clear records help the project team distinguish waiting time from an unresolved action.

For example, an authority might return a high-rise access drawing with a clearance question. The coordinator first checks which drawing revision the reviewer used. If the comment refers to an older layout, they confirm the current version with the designer. However, they do not assume that a newer drawing automatically answers the concern. The designer must explain how the current layout addresses the stated clearance. Next, the coordinator links that response to the comment and checks the replacement documents. They tell the project lead which approval remains pending and what response is ready. This keeps a document correction separate from a technical decision.

Coordination and completion

During review, the coordinator turns changing approval information into useful project updates. An update should explain the current stage, next action, responsible person, and known dependency. Instead of promising an approval date, they distinguish confirmed dates from estimates. If a response affects planned construction, the project lead needs that information early. The coordinator can also bring related questions together before a technical meeting. Afterward, they record the decisions and check who will answer each open point. Where different disciplines give conflicting answers, they request one agreed technical response. This reduces separate submissions that solve one issue but create another.

When an approval arrives, the coordinator checks more than the document heading. They read its scope, conditions, validity, and references to drawings or earlier approvals. A no-objection certificate may cover only a defined activity, not the whole project. Therefore, the relevant technical and site leads need the conditions before using it. The coordinator keeps the approved version separate from superseded records to prevent confusion. If the design later changes, they ask the responsible specialist whether further approval is necessary. Finally, they close completed tracking entries while keeping any remaining conditions visible. A clear handover shows what the approval permits and what still needs action.

Typical Duties & Responsibilities

• Maintain an approval register that shows each application reference, responsible person, current status, and next action.
• Check authority contact details and submission routes before sending documents, so queries reach the correct recipient.
• Prepare document indexes that let reviewers locate drawings and supporting records without searching through unrelated material.
• Record requests for additional information and assign each point to the relevant technical contributor for response.
• Arrange submission-related discussions with the relevant parties and capture agreed actions in a clear meeting record.
• Track authority fee requests against the related application and pass them to the responsible person for handling.
• Flag approaching certificate validity dates so project leads can decide whether renewal or another submission is needed.
• Organise final approval records by project scope, giving authorised colleagues a clear route to the correct documents.

Candidate Profile

Applicants can prepare a truthful example of organising approval records during a project handover. For instance, explain how you identified missing certificates and helped the team locate valid copies. Describe your own contribution, the records you checked, and the result without claiming others' technical decisions. Use a non-confidential summary rather than sharing protected project files. Also, ask which authorities and project stages the position covers. Clarify the reporting line, document responsibilities, work arrangement, and expected start date. These preparation suggestions are guidance, not additional employer requirements.

Qualifications & Requirements

• Experience: Other Positions: Minimum 5 years of relevant UAE experience.
• High-rise building construction experience is mandatory for ALL positions.
• Strong technical knowledge, project execution capabilities, and familiarity with UAE construction standards and regulations.
• Excellent communication, coordination, and problem-solving skills.
• Preference will be given to candidates who are available to join immediately or within a short notice period.

Employer-stated Skills & Competencies

• Strong technical knowledge
• Project execution capabilities
• Familiarity with UAE construction standards and regulations
• Excellent communication, coordination, and problem-solving skills
• Strong technical knowledge, project execution capabilities, and familiarity with UAE construction standards and regulations.
• Excellent communication, coordination, and problem-solving skills.

How to Apply

Apply Now: career@tarrad.ae Interested candidates are requested to send their updated CVs, clearly mentioning the position applied for in the email subject line.

About Tarrad Development

Tarrad Development operates in luxury real estate. Its portfolio includes Mackerel Tower and the Celesto series.