Skip to content

GGB project record

Nalan Restaurant, BurJuman — From Site Control to Handover

Restaurant fit-out, programme control and handover BurJuman Centre, Bur Dubai 2019

Inside a live mall, a restaurant fit-out is mostly interfaces: landlord systems, authority dependencies and specialist packages. This record shows them governed to a recorded handover on 12 September 2019.

Founder-led delivery control — inspection discipline, interface coordination and programme governance through to a recorded handover.

The Constraint-to-Handover Timeline

  1. 01

    Site inspected

    Inspection and progress reporting established the true state of works.

  2. 02

    Conflict identified

    Design and execution were reconciled where the site diverged from intent — revised 3D views recorded the correction.

  3. 03

    Interfaces coordinated

    The electrical and SMDB interface with the base building became an owned work package.

  4. 04

    Dependencies governed

    Firefighting, mall-management and Civil Defence dependencies were tracked as programme items, not surprises.

  5. 05

    Specialist packages completed

    Specialist lighting landed inside the same controlled programme.

  6. 06

    Handover recorded

    A completion and handover programme with maintenance documentation closed the record on 12 September 2019.

GGB development framework — the control sequence from the attested record; commercial matters between the parties are never published.

The situation

BurJuman is a managed environment — mall engineering, Civil Defence dependencies and base-build electrical interfaces set the real programme. Control meant inspecting, reconciling design against execution, and owning every interface until handover was recorded.

The mandate

Restaurant fit-out, programme control and handover. Founder-led delivery control — inspection discipline, interface coordination and programme governance through to a recorded handover.

What the mandate covered

  • Site inspection
  • Progress reporting
  • Site photographs
  • Revised 3D views
  • Design and execution reconciliation
  • Electrical and SMDB interface
  • Firefighting coordination
  • Mall-management coordination
  • Civil Defence dependencies
  • Completion and handover programme
  • Specialist lighting
  • Maintenance documentation

How it was run

  1. Established the true state of works through site inspection and progress reporting before promising anyone a date.
  2. Reconciled design against execution where the site diverged from intent, with revised 3D views recording the corrected intent.
  3. Owned the electrical and SMDB interface with the base building as a work package, not a hope.
  4. Governed firefighting coordination, mall-management coordination and Civil Defence dependencies as programme items.
  5. Closed the record with a completion and handover programme, specialist lighting landed, and maintenance documentation handed over.
Decision made
Report the site as it is, not as the programme wishes it were.
What was controlled
Inspection cadence and progress reporting from the first visit.
The record
Site-inspection and progress-reporting records (attested).
What it proves
Delivery control ran on observed fact.
Where the record stops
That the works never slipped — timing beyond the recorded handover is not claimed.
Why it matters to your project
Every fit-out disaster starts with a report that flattered the site.
Decision made
Treat authority and landlord dependencies as programme items with owners.
What was controlled
Firefighting coordination, mall-management coordination, Civil Defence dependencies, the SMDB interface.
The record
Interface and coordination records (attested).
What it proves
The approvals path was governed, not awaited.
Where the record stops
Any authority outcome beyond the recorded handover.
Why it matters to your project
In a live mall, the critical path runs through other people’s systems — control means owning the interface.
Decision made
Close out formally: handover recorded, maintenance documentation delivered.
What was controlled
The completion and handover programme.
The record
The handover record of 12 September 2019.
What it proves
The engagement ended in a recorded handover, not a drift.
Where the record stops
Post-handover trading performance.
Why it matters to your project
A dated handover is the difference between a finished project and a stopped one.

What the record consists of

Site inspection and progress reports
proves delivery-control discipline on a live site
Revised 3D views
proves design work reconciling intent with execution
Interface and coordination records
proves owned interfaces with landlord systems and authorities
Completion and handover programme
proves planned control of the close-out
Handover record
proves delivery to a recorded handover on 12 September 2019

The source records for this project — inspection reports, revised views, coordination records and the handover programme — are held on file and described here rather than reproduced, so client and commercial material stays private. Site photographs stay internal.

Delivered by GGB’s founder through the operating and consulting practices he led at the time; presented here as one continuous professional record.

The outcome

  • Handover recorded on 12 September 2019.

Not claimed

  • Commercial and payment matters between the parties are never published.
  • No trading-performance claim is made — the record proves delivery control and a recorded handover, not commercial results.

Start a Project WhatsApp GGB