Prerequisites not yet underway.
An approval whose predecessor has not been started — flagged before the submission is attempted rather than after the portal rejects it. This is the sequencing knowledge, made into a check.
Zepth Core · Document Management
Authority Approval Log
The regulatory critical path — and it slips silently, because nobody owns the chase.
Last updated
Zepth Core module
Authority Approval Log
AI agent built into the module
The approvals registerPrerequisite chainsSubmission and resubmission trackingCertificate custody with expiry alerts
Many, not one
a single Dubai tower can require NOCs from civil defence, the municipality, the roads authority, utilities, aviation and district bodies
GCC authority practice
The count varies by project, emirate and asset type — which is precisely the problem. There is no canonical list, and the scarce asset on any project is the person who knows what is prerequisite to what.
Documents, not deadlines
approval cycle time is dominated by resubmission loops — rejections for missing or inconsistent documents, days to weeks each
GCC approvals practice
We deliberately quote no authority processing times. They are volatile, they vary by emirate, and a number published here would be wrong within a year. What does not change is that a complete first submission is the whole game.
Overview
Authority approvals — no-objection certificates, permits, inspections and completion certificates — are the government’s clock running alongside yours. They gate mobilisation, they gate utility connections, and at the end they gate occupancy.
And they slip for a reason that is almost never technical: nobody owns them. They are treated as compliance paperwork rather than as programme activities, so they have no duration, no float, no owner, and no early-warning signal until the day somebody discovers the building cannot be occupied.
The fan-out, and the knowledge that is scarce
One project, many authorities. Civil defence for life safety. The municipality for the building. The roads authority for anything that touches the highway. Utilities for power, water and district cooling. Aviation, if you are tall enough or close enough. District bodies, free-zone authorities, and whichever body has jurisdiction over the thing nobody thought about.
Each has its own portal, its own document set, its own cadence, and its own idea of what constitutes a complete submission.
And the failure mode is not the approval you knew about and started late. It is the NOC nobody knew was a PREREQUISITE to the one they were chasing — discovered at the point of submission, when the portal rejects it and asks for a certificate from a body the team had not previously heard of. The scarce asset on any GCC project is not effort. It is sequencing knowledge, and it usually lives in one person’s head.
What an approvals discipline requires
Approvals are programme activities. Put them on the programme. With durations, owners, predecessors and float — not in a compliance drawer to be dealt with by whoever has capacity. An approval with no owner is an approval that will be chased by nobody until it is late, and by everybody once it is. And the completion-certificate chain — final inspections, conformity certification, occupancy — determines the handover date every bit as surely as the snag list does. One of those two is on the programme. The other usually is not.
Document completeness dominates cycle time. Everything else is noise. Approvals are rejected for missing documents, inconsistent drawings, a stamp from the wrong entity, a form completed against last year’s template. Each rejection is a resubmission loop measured in days or weeks, and it consumes far more calendar than any authority’s actual review. The lever is not chasing harder. It is submitting complete — which means somebody has to know, in advance, exactly what complete means for this authority, this type, this year.
Permits expire mid-project, and nobody is watching the ones that already worked. Crane permits. Road-closure permits. Working-hours exemptions. Utility connection approvals. These are granted, celebrated, filed — and they have validity windows that end while the project is still running. It is exactly the same discipline as tracking bond and insurance expiry, and it fails the same way: attention flows to what is not yet obtained, and nothing watches what has been.
The utility and third-party handshakes are what ambush fit-out. District cooling. Power energisation. Telecom. These involve a third party with its own commercial process, its own queue, and no particular investment in your programme — and they routinely surface late, because they look like connections rather than approvals. A project that has managed civil defence immaculately can still miss its handover waiting on an energisation date it never put on the programme.
How approvals go wrong
Silently, which is the whole problem. An approval slips a week, then two, and nothing happens — no alarm, no escalation, no variance report, because it was never on the programme with a duration in the first place.
A prerequisite emerges late, and a submission that was ready is now blocked behind an application that has not started. A permit that everybody remembers obtaining expires, and the crane stops.
And then the completion-certificate chain runs, at the end, in series — final inspections, conformity, occupancy — with a handover date that was fixed months ago and a set of authorities who did not agree to it.
How Zepth runs approvals
An approvals register built at mobilisation: every authority, every approval type, its prerequisites, its document set, its owner and its target dates — which is the artefact that turns one person’s sequencing knowledge into something the project owns.
Sequenced against the programme, so an approval is an activity rather than a task. Submission tracking through the resubmission loops, because the loops are where the calendar goes. And certificate custody with expiry alerts — so the permit that is quietly running out surfaces before the crane stops rather than after.
The value
Why it matters
Approvals sit on the programme with owners and durations — so a slip produces a signal rather than a surprise.
Prerequisite chains are visible before submission, not discovered at the portal.
First submissions are complete, which is the only real lever on approval cycle time.
Permits that expire mid-project surface before the crane stops.
Capabilities
What you can do
01
The approvals register
Authority, type, prerequisites, documents, owner and dates — the artefact that turns one person’s sequencing knowledge into something the project owns.
02
Prerequisite chains
What blocks what. The NOC nobody knew was prerequisite is the classic way a GCC programme loses a month.
03
Submission and resubmission tracking
Through the loops, because the loops are where the calendar actually goes.
04
Certificate custody with expiry alerts
Crane permits, road closures, working-hours exemptions — the approvals that were obtained and then stopped being watched.
05
The occupancy view
What is still blocking the completion-certificate chain, kept current, rather than assembled in a panic at the end.
The workflow
How it actually runs
- 1
Build the approvals register at mobilisation
Authority, type, prerequisites, document set, owner, target dates. This is the moment to extract the sequencing knowledge from whoever is carrying it, before they are unavailable.
- 2
Sequence it against the programme
With durations and predecessors. An approval that is not on the programme has no float, no variance, and no early warning — it simply becomes late one day.
- 3
Submit complete, and track the loops
Document completeness dominates cycle time. Every resubmission is days to weeks, and the resubmissions are where the schedule actually goes.
- 4
Schedule the inspections
They are appointments with an external party who has other appointments. Booked late, they are booked far away.
- 5
Hold the certificates — and watch them expire
Crane permits, road closures, working-hours exemptions. Attention flows to what is not yet obtained; nothing watches what already was.
AI that does the work
How AI changes Authority Approval Log management.
Submission checklists per authority type.
Drafted from what that authority actually requires, so the first submission is complete — which is the only lever that meaningfully moves approval cycle time.
The occupancy answer, kept current.
“What is still blocking handover?” answerable on any Tuesday, rather than assembled in a panic in the last fortnight by someone reading a filing cabinet.
Expiry radar.
Permits and certificates approaching the end of their validity window, surfaced while there is still time for that to be useful information rather than an incident report.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
Best practices
- Put approvals on the programme with durations and owners. An approval in a compliance drawer has no float and no variance — it is simply on time, until the day it is not.
- Extract the sequencing knowledge at mobilisation. It lives in one person’s head, and the project will discover this at the worst possible moment, which is when they are on leave.
- Optimise for a complete first submission, not for chasing. Resubmission loops consume more calendar than any authority’s review, and chasing harder does not shorten them.
- Track expiry as hard as you track approval. Attention flows to what has not been obtained; nothing watches what has, and the crane permit expires anyway.
Dashboards & reporting
The approvals register by authority, type and owner, with prerequisites and status — and, crucially, with approvals shown as programme activities rather than as compliance items. Submissions and their resubmission loops, which is where the calendar goes. Certificates held, and certificates expiring. And the occupancy view: what is still blocking the completion-certificate chain, today.
Live dashboards
Drill-down & filters
Export to Excel / PDF
FAQ
Common questions
What is an NOC?
A no-objection certificate: a formal statement from an authority or third party that it does not object to your work proceeding. It is the basic currency of GCC approvals, and the thing to understand about NOCs is that they chain. One NOC is frequently a prerequisite for another, and the project that discovers this at the submission portal has already lost the time.
Read the full answerWhich approvals does a typical GCC project need?
It varies by emirate, asset type and location, and there is no canonical list — which is itself the point. A single tower can require sign-offs from civil defence, the municipality, the roads authority, utilities, aviation and district or free-zone bodies, each with its own portal, document set and cadence. Build the register at mobilisation, from someone who has done this asset type in this jurisdiction, and treat that person’s knowledge as the scarce asset it is.
Read the full answerWhy do approval timelines slip?
Document completeness, overwhelmingly. Approvals get rejected for missing documents, inconsistent drawings, a stamp from the wrong entity, a form filled in against last year’s template — and every rejection is a resubmission loop of days or weeks. That consumes far more calendar than any authority’s actual review does. The lever is submitting complete, not chasing harder.
Who should own the approvals chase?
A named person, with the approvals on the programme as activities carrying durations and predecessors. The reason approvals slip silently is that they usually have neither — so there is no float to consume, no variance to report, and no early warning. They are simply on time until the day they are catastrophically not.
How do approvals connect to handover?
They determine it. The completion-certificate chain — final inspections, conformity certification, occupancy permission — runs at the end, in series, and it fixes the handover date every bit as firmly as the snag list does. The difference is that everybody watches the snag list.
Read the full answerWhat expires mid-project?
Crane permits, road-closure permits, working-hours exemptions, utility approvals — and, in the same family of failures, bonds and insurances. All of them were obtained, celebrated and filed, and all of them have validity windows that end while the project is still running. Attention flows to what has not been obtained yet. Nothing watches what has.
Sources
- GCC authority practice — the multi-authority fan-out, prerequisite chaining, and the completion-certificate chain to occupancy
- We deliberately quote no authority processing times. They are volatile, they differ by emirate, and a figure published here would be wrong within a year and quoted back at us. The durable claim is that document completeness dominates cycle time.
- UAE civil-defence penalties are cited on /modules/asset-inspections-audits/, and labour penalties on /modules/attendance/. We do not restate them here.
Related answers
In the guides
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
See it on your project.
A short, tailored walkthrough on your real workflow — no generic demo.