Who Owns the Decisions on Your Project?

Most UAE project overruns do not start with a bad contractor or a late delivery. They start with a question no one can answer cleanly: who owns the decisions on this project? When that question has no clear answer, decisions default to whoever shouts loudest, whoever holds the largest contract, or whoever happens to be in the room. The project does not fail in one moment. It drifts — variation by variation, delay by delay — until the cost and timeline are unrecoverable.

The sponsor, typically a senior executive or developer, intended to remain strategic. Instead, they spend their time reacting to problems that should have been resolved below their level weeks earlier. Contractors make calls that protect their margins. Consultants defer to avoid liability. Nobody is watching the whole programme. This is the most common pattern TrustForce encounters on UAE projects where no independent PM was appointed. It is not a people problem. It is a structural problem — and it has a structural solution.

Decision accountability is not a personality trait or a management style. It is a structure: a defined, documented framework that establishes who decides what, at what threshold, with what information, and by when. On a well-run project, every open decision is tracked as a programme risk. Every workstream — design, procurement, authority approvals, cost, technology, operations — feeds into a single delivery framework. The project sponsor receives consolidated reporting, not a flood of separate updates from separate parties, each presenting their own version of the project's health.

On projects without independent PM, that structure rarely exists. Each party manages its own workstream in isolation. The connections between them — the handoffs, the dependencies, the sequencing decisions — fall into gaps. Nobody is accountable for the gaps. By the time the sponsor realises the programme has slipped, the decisions that caused the slip were made weeks or months earlier, by people who had no visibility of the downstream impact. The damage is done. Recovery costs more than prevention would have.

On UAE construction and fit-out projects that reach a PM for the first time after things have gone wrong, the pattern is consistent. A developer or corporate client appoints a main contractor, a design consultant, a cost consultant, and an MEP specialist. Each party has a contract. Each party has a scope. Nobody has authority over the whole. The main contractor's programme is the de facto master schedule, but the main contractor's interests are not always aligned with the client's. When a decision is needed — a design change, a value engineering proposal, an authority submission — it goes to the client. The client, lacking programme context, either delays or decides without full information. Both outcomes cost time and money.

In Ras Al Khaimah specifically, authority approvals are among the most under-managed workstreams on construction projects. They require early coordination with RAK Municipality, the Civil Defence authority, and sector-specific bodies depending on the building use. When authority approval milestones are not built into the master programme from day one — with a named owner, a submission schedule, and escalation triggers — they become the single most common cause of programme delay. TrustForce manages authority approvals as a primary workstream on construction projects, not an afterthought. The difference in timeline outcomes is measurable.

An independent PM establishes decision accountability through four mechanisms, implemented at programme outset — not after the first crisis.

Decision authority matrix. Every category of decision — design, procurement, cost variation, programme change, authority submission — is mapped to a named decision-maker with a defined threshold. Below the threshold: the PM decides. Above the threshold: the sponsor is briefed and decides within an agreed timeframe. Nothing sits in a queue waiting for someone to claim ownership.

Open decisions register. Every unresolved decision is logged as a programme risk, with an owner, a due date, and an impact assessment. The register is reviewed weekly. Decisions that age past their due date are escalated automatically. The sponsor sees the register as a live dashboard, not a retrospective report.

Single programme view. All workstreams — contractor, consultant, specialist, authority — are integrated into one master programme. Dependencies are mapped. Handoffs are owned. When a delay in one workstream threatens another, the PM identifies the impact before it becomes visible on site.

Sponsor reporting protocol. The sponsor receives one consolidated report: programme status, cost position, open risks, and decisions required at sponsor level. Not one report per consultant. One report. Calibrated to what the sponsor needs to know to make informed decisions — and nothing more.

On UAE fit-out projects that reach a PM after things have gone wrong, the health assessment finds the same position. The client ran the project without independent oversight. The contractor managed the programme. The design consultant managed the drawing register. The cost consultant tracked variations independently. Multiple sets of instructions reached the contractor from different parties — the design consultant, the cost consultant, the client's own team — without any of them being cross-referenced. The variation exposure is significant. The programme has slipped. The contractor is contractually within their rights on every claim.

The first action is not to address the variations. It is to establish who owns the decisions going forward. A single instruction channel is agreed. A variation authority matrix is documented. A weekly programme review with all parties present is instated. That structure — which should have existed from day one — stops the exposure from growing. The lesson is consistent: the cost of independent PM is a fraction of the cost of a single unmanaged variation sequence. The accountability structure pays for itself before practical completion.

This is a practical diagnostic for any UAE project sponsor, developer, or corporate decision-maker preparing to mobilise a project. If you cannot answer each question clearly, you have an accountability gap.

1. Who is the single point of contact for all programme decisions below sponsor level? If the answer involves more than one person or party, the answer is effectively nobody.

1. Who owns the authority approvals workstream? Specifically: who is responsible for submission schedules, tracking, chasing, and escalating authority decisions in Ras Al Khaimah or your emirate of delivery? If this is assumed to sit with the contractor or a consultant, confirm it in writing — and confirm they have done it before.

1. How will variation instructions reach the contractor? Is there a single instruction channel, a named issuer, and a cost-impact review before instructions are issued? If not, your variation register will grow faster than your programme.

1. What does the sponsor receive, and how often? If the answer is "reports from each consultant," that is not consolidated reporting. It is noise. One report, one owner, one version of the truth.

1. What threshold triggers a sponsor decision? If every decision escalates to the sponsor, the sponsor is the project manager. Define the threshold. Protect your time. Trust the PM to hold the line below it.

If your project is in pre-mobilisation, the time to establish decision accountability is now — before contracts are signed and before workstreams diverge. If your project is already in delivery and you recognise the pattern described here, the accountability structure can be imposed mid-programme. It is harder, and it costs time, but it is recoverable. TrustForce provides independent PM for construction, fit-out, digital, and business change programmes across the UAE, operating from Ras Al Khaimah as a project management company in Ras Al Khaimah. See the full range of project management services we provide and the sectors we work in. For an understanding of how authority approvals specifically create decision accountability gaps on RAK projects, see Why Authority Approvals Derail UAE Construction Projects.