Mixed-Use Residential Development in the Northern Emirates — Saved from a 14-Month Overrun

A developer eleven weeks into construction with no structured approval programme. The overrun in prospect was 14 months. The delivered overrun was six weeks.

The Outcome First

A 340-unit mixed-use development — residential towers with ground-floor retail — in Ras Al Khaimah. TrustForce was appointed as independent PM eleven weeks after construction had started, brought in by the developer's lender following a draw-down review that identified authority approval gaps as a critical programme risk.

The lender's concern was specific: civil defence and municipality approvals for the superstructure phase had not been submitted, the contractor had been given a completion date that assumed approvals would arrive within standard timelines, and no approval tracker existed. The quantity surveyor's assessment at the point of TrustForce appointment was a probable 14-month overrun against the contractual completion date. Six weeks of overrun was ultimately delivered — ten days of which related to a civil defence resubmission on the retail podium that was outside TrustForce's control at appointment.

What TrustForce Inherited

Eleven weeks of construction on a programme with no structured approval strategy is a specific kind of problem. It is not the same as a programme that has not started. Contractors are mobilised, procurement is underway, and subcontract packages are either awarded or in negotiation. Changing the sequencing of work to accommodate authority approval timelines — which should have been built into the programme before mobilisation — now has direct cost implications.

The approval gap on this project was the result of a straightforward sequence: the developer had appointed the main contractor before the design was sufficiently advanced for authority submission. The contractor had built a programme based on assumed approval dates that no one had verified with RAK Municipality or the relevant authority bodies. When TrustForce reviewed the programme at appointment, four separate approval workstreams — civil defence, municipality structural sign-off, DEWA equivalent utility connections, and Al Marjan Island Authority coordination for the coastal site — had no confirmed submission dates, no named submission owner, and no dependency mapping against construction activities.

From the field — what an unstructured approval programme looks like in practice

On this project, the contractor's site manager was fielding approval queries from four separate authority contacts, none of whom had been briefed on the programme or given a submission schedule. Two of the four had received informal enquiries from the developer's consultant but no formal submission pack. The civil defence contact had changed twice since the project started; neither successor had been notified of the project.

TrustForce's first action was not a programme revision. It was an authority contact audit — mapping who held each approval file, what had been submitted formally versus informally, and what each authority needed to move to the next stage. That audit took four days. It identified one submission that was further advanced than the programme register suggested and two that were materially behind. The programme was revised only after the audit was complete.

How the Programme Was Restructured

The restructured programme had one governing principle: no construction activity was scheduled against an assumed approval date. Every approval-dependent workstream — structural sign-off, civil defence for each phase, utility connection approvals — was scheduled against the authority's confirmed review cycle, with a resubmission buffer built in based on TrustForce's observed first-submission rejection rates on comparable RAK residential projects.

Four construction packages were resequenced as a result. The basement waterproofing contractor, originally scheduled to demobilise before the superstructure civil defence approval was expected, was retained on site for an additional three weeks at a negotiated standby rate rather than demobilised and remobilised — a saving of approximately AED 180,000 in remobilisation costs against the original programme assumption.

The lender received a revised draw-down schedule within three weeks of TrustForce appointment, tied to restructured approval milestones rather than construction progress dates. Monthly reporting against that schedule continued for the remainder of the programme.

Practical Takeaway — What Lenders and Developers Should Require Before Contractor Appointment

The gap on this project was not unusual. TrustForce has seen the same pattern — contractor appointed before approval submissions are structured — on four of the last seven Northern Emirates residential projects reviewed at programme outset or shortly after. These are the checks that should be completed before a main contractor is appointed on any UAE residential or mixed-use development:

Approval matrix completed for the specific site: authority bodies, submission types, review cycles, and named contacts confirmed — not assumed from previous projects
Design stage confirmed as sufficient for each submission type — civil defence, structural, utility, and any freezone or coastal authority requirements specific to the site
Approval dependencies mapped against the construction programme, with resubmission buffers applied at each gate
Contractor programme reviewed against approval assumptions before execution — any assumed approval date that has not been confirmed with the relevant authority must be flagged and buffered
Lender reporting obligations tied to approval milestones, not construction progress milestones, where project finance is in place

What to Do Next

If you are a developer or lender with a UAE residential or mixed-use project where authority approvals have not been structured into the construction programme — whether at pre-appointment stage or already underway — TrustForce can provide an independent programme review and approval gap assessment. Projects already in construction are recoverable. The cost of restructuring a programme at week eleven is significantly lower than the cost of a 14-month overrun and the lender reporting obligations it generates.

FAQ

Can a programme be restructured once construction has started, or is it too late?

It is rarely too late, though the options narrow as construction advances. The earlier the intervention, the lower the restructuring cost — both in direct variation claims and in the resequencing of subcontract packages. On this project, appointment at week eleven allowed four packages to be resequenced before they were contractually committed. By week twenty, two of those options would have been closed. The baseline question is not whether restructuring is possible; it is what it costs at the point of intervention versus what a full overrun costs.

What is the role of the lender in a situation like this?

On projects with development finance in place, the lender's draw-down conditions typically require programme compliance as a condition of each advance. An authority approval gap that threatens programme completion also threatens draw-down eligibility — which is why lenders, not just developers, have a direct interest in the approval programme. TrustForce's monthly reporting on this project was structured specifically for the lender's draw-down review: each report tied construction progress to confirmed approval status, not to programme assumptions.

How does TrustForce handle the relationship with the main contractor when appointed mid-programme?

Transparently and directly. The contractor on this project was informed of TrustForce's appointment scope at the first site meeting and given a copy of the authority contact audit findings. No contractor relationship benefits from an independent PM operating as an adversary — the goal is a shared understanding of the approval-dependent workstreams and a programme that both parties can commit to. Where the restructured programme required package resequencing, TrustForce negotiated directly with the relevant subcontractors under the contractor's supervision, not around it.