How a Development Principal Works with the Architect of Record: Who Holds Which Role on a UAE Restaurant Project

An engineering consultancy that acts as architect of record on Dubai fit-outs asked us a fair question: how does a development principal actually work with them on a restaurant project? Owners ask the same question from the other side, usually as “which of these roles do I really need?” Both deserve the same plain answer: which roles a restaurant project in the UAE needs, which of them a consultant may never hold, and how the development principal sits among them as the owner’s representative.

The roles a restaurant project needs

Strip a restaurant development to its parties and there are seven. Some are one person; some are firms; three are held only by licensed parties.

The owner. Decides, approves and pays. The role that every other role reports to, and the one most often under-served, because the owner is usually doing it for the first time.

The architect of record. The licensed architectural consultant whose registration carries the design drawings and the authority submissions for the fit-out — the building permit, the municipality approvals, the civil defence submissions, the completion certificates. In the UAE this role is held by a licensed party in the relevant emirate, and the licence is the point: the drawings are stamped, and the stamp is what the authorities accept.

The MEP engineer. Mechanical, electrical and plumbing design — the kitchen extract, the gas, the cold rooms, the electrical load, the drainage — usually held within the architect of record’s team or by a separately licensed engineering consultant. In a restaurant the MEP design decides whether the kitchen can actually cook the menu, and it is where under-briefing costs the most.

The kitchen and equipment consultant or supplier. The layout, the line, the equipment schedule and the specification. Sometimes a licensed party, often a specialist, occasionally the equipment supplier — which is convenient and a conflict.

The fit-out contractor. Builds what is designed and approved. Appointed against compared quotations, paid by the owner directly, supervised against the drawings.

The operator’s side. The chef, the general manager, the opening team — the people who will run what is built, and who should be reading the drawings before the contractor is.

The development principal. The party that carries the programme between the owner’s decision gates and coordinates every other role as the owner’s representative. This is the role GGB holds.

What the development principal is, and is not

The development principal is not the architect of record and never substitutes for it. It does not stamp drawings, does not make authority submissions in its own name, does not design the MEP. Those are licensed roles and they stay with licensed parties.

What the development principal does is everything the licensed roles are not appointed to do and the owner cannot do alone: read the project’s numbers before the design is briefed, so the room the architect designs is the room the revenue can carry; write the concept, the menu economics and the operating brief the designers and the kitchen consultant design to; coordinate the licensed consultants against the budget and the programme; run the procurement comparisons so the owner appoints suppliers against their own quotations; coordinate the licensing route so the authority submissions the architect of record makes are the right ones in the right order; run pre-opening — recruitment, training, systems, the opening plan — and hand the operation an operating-control layer that survives the engagement.

In short: the licensed roles make the project legal and buildable; the development principal makes it commercially right and operable, and holds the whole thing together for the owner. Neither can do the other’s job, and a project that tries to make one of them do both is where the money goes.

How the two roles actually work together

In practice the relationship runs through four handoffs.

The brief. The development principal delivers the architect of record a brief that already contains the numbers: the seat count the revenue model requires, the price architecture the finish level has to match, the kitchen line the menu needs, the channel mix that decides the back-of-house footprint, and the capital the fit-out has to fit inside. A brief without those is an invitation to design a beautiful room the P&L cannot carry.

The coordination. Through design development the development principal reads every drawing set against the operating brief and the budget — the extract route against the kitchen line, the seating plan against the covers, the bar against the beverage share, the finish schedule against the capital — and brings the operator’s side into the drawing review before the contractor prices it. The architect of record owns the design; the development principal owns whether it is the right design for this business.

The submissions. The architect of record makes the authority submissions under its licence. The development principal coordinates the licensing route around them — the trade licence, the food-safety approvals, the sequencing of permits against the programme — so nothing waits on a submission that could have been made earlier. Who submits what, and when, is written into the programme before the fit-out starts.

The site. During construction the architect of record supervises the design intent; the development principal runs the programme, the procurement, the variations against the budget and the operator’s readiness, and reports to the owner at the decision gates. The two meet weekly and disagree in the room rather than on site.

Who pays whom, and why it matters

Every licensed consultant is itemised in the proposal and approved by the owner in writing before appointment. Every one of them is paid by the owner’s company directly. GGB adds no margin to any licensed consultant, supplier or contractor, and says so in writing — because a development principal that earns on the size of the appointments it coordinates has an interest in their size, and the owner should never have to wonder whether the second engineer was needed.

Where projects go wrong when the roles blur

Three failure patterns recur often enough to name, and each is a role held by the wrong party.

The architect as the development principal. The design is excellent and the numbers were never read; the room seats thirty fewer covers than the rent requires, and the discovery arrives with the first month’s P&L. The architect did their job. Nobody held the other one.

The contractor as the kitchen consultant. The line is laid out by the party that supplies the equipment, and the specification grows to fit the supplier’s catalogue rather than the menu. The extract, the cold storage and the electrical load are then engineered around a kitchen that was never briefed from the food.

The owner as everyone. The most common and the most expensive. A first-time owner coordinating the architect, the engineer, the contractor and the authorities personally, while also opening a restaurant, holds the development principal’s role without its method, and pays for the gaps in variations and delay. Nothing was done wrong by any consultant; the coordinating role was simply vacant.

For the consultancy that asked

To the architect of record wondering how this works from their side: the development principal is the client’s representative who arrives with the numbers already done, the brief already written and the operator already in the room. It makes the design work faster and the submissions cleaner, because the questions that usually arrive from the owner at the end — can the kitchen cook this menu, will the room carry this rent, why does the extract run there — were answered before the first drawing. The licensed roles stay licensed. The coordination stays with one accountable party. The owner deals with one team.

For the owner deciding which roles to appoint

All seven exist on every project whether or not they are appointed. When a role is not appointed, the owner holds it — usually the development principal’s, and usually without knowing. The question to ask each firm proposing to help is which of the seven it holds, under which licence where a licence is required, and who holds the rest. The honest answer names them all.