PMO Setup for a UAE Developer — From Reactive Reporting to Controlled Delivery in Four Months

A UAE-based developer — a family-owned business managing a portfolio of seven concurrent projects across RAK and the Northern Emirates, ranging from a 180-unit residential scheme to a single-floor commercial fit-out — had no central oversight function. Each project was managed by a separate team: some internal staff, some seconded from the main contractor, one managed directly by an external consultant. The board received status reports in four different formats, on four different schedules, with no common definition of what "on programme" or "on budget" meant across the portfolio.

In the six months before TrustForce was appointed, two projects had moved from green to red status in the space of a single board meeting — not because they had deteriorated rapidly, but because the reporting format used by those project teams did not surface risks until they became confirmed delays. The board's concern was not the delays themselves. It was that they had not seen them coming.

TrustForce was appointed to design and stand up a PMO for the developer's portfolio. Four months after appointment, a functioning PMO was operational: a standardised reporting framework across all seven projects, a single portfolio dashboard reviewed at monthly board level, a risk register maintained centrally with named owners and escalation timers, and two projects that had been quietly drifting now formally recovered and tracking to revised completion dates. The developer's board described the first portfolio review under the new framework as the first meeting in two years where they felt they understood the actual state of the portfolio.

Seven projects reporting in four formats is not a cosmetic problem. It is a governance problem. When each project team defines progress in its own terms — one reports percentage complete against programme, another reports against budget spend, a third reports milestone achievement without reference to the programme — the board cannot make comparative judgements about where to direct attention or resource. Every project looks manageable in isolation. The portfolio picture is invisible.

The two projects that moved from green to red without warning shared a specific characteristic: both were being reported against spend, not programme. Both were on budget at the point they turned red — which is how they had remained green for so long. One had been spending at plan because its contractor had front-loaded preliminaries and was behind on measurable works. The other had been spending below plan because a procurement package had not been awarded, a fact that had not appeared in any status report because spend was tracking to budget.

Neither project team had reported dishonestly. Both had reported accurately against the metric they were using. The metric was wrong.

The PMO TrustForce designed for this developer was built on independent verification, not consolidated reporting. Each project team continued to manage their own project. TrustForce attended one site visit and one programme review per project per month — not to supervise, but to verify. The portfolio dashboard was built from TrustForce's direct assessment of each project's status, cross-referenced against the project team's own reporting. Where the two diverged, the divergence was the first item on the monthly board agenda. On four occasions in the first four months, TrustForce's assessment identified a risk that the project team's report had not surfaced. In three of those four cases, the project team agreed with the assessment when the evidence was presented. In one case, they disagreed — and the board heard both positions.

The two projects identified as quietly drifting — the residential scheme and a commercial office fit-out in Fujairah — were not in crisis. They were two to three months behind a programme that had not been formally updated since mobilisation, against a completion date that the contractor had informally flagged as unachievable in a site meeting six weeks earlier. The flag had not reached the board.

Recovery on both projects followed the same sequence. TrustForce issued a programme recovery notice to each contractor within the first six weeks of appointment, requiring a revised programme with recovery measures identified and costed. Both contractors submitted revised programmes. One recovery programme was accepted without amendment. The second required two rounds of review — the contractor's initial recovery measure proposed accelerating the fit-out phase by adding a night shift, which the Fujairah Municipality site working hours conditions did not permit. The revised recovery programme, which resequenced two fit-out packages rather than extending working hours, was accepted and the project tracked to its revised completion date without further slippage.

A PMO that does not meet these conditions will produce reports but will not improve delivery. Each condition is a design requirement, not an operational preference:

• Independent verification built in: the PMO must have direct access to project evidence — site visits, programme files, contractor submissions — not just project team reports
• Common status definitions agreed before the framework is launched: "on programme," "at risk," and "in recovery" must mean the same thing across every project in the portfolio
• Risk register owned centrally with named escalation owners and response timers: a risk with no owner and no timer is a risk that will not be acted on
• Board reporting cadence set by portfolio complexity, not by convention: monthly is appropriate for a seven-project portfolio at this scale; a 20-project portfolio at higher capital value warrants fortnightly
• PMO scope defined in writing before appointment: the boundary between PMO oversight and project team authority must be documented and agreed with project teams before the first review — ambiguity about who holds sign-off on programme changes generates conflict that undermines the PMO's credibility within weeks of launch

If you are a UAE developer or business owner managing more than three concurrent projects and your board is receiving status reports that do not give a consistent picture of portfolio health, the problem is structural — not a matter of asking project teams to report more carefully. TrustForce designs and stands up PMO functions for UAE developers and multi-project businesses, with engagement models that range from full PMO design and operation through to a structured handover to an internal team. If your current reporting is not telling you what you need to know before problems become delays, that conversation should happen before the next board meeting.