On a large development the word "architect" describes several distinct jobs, often held by different practices. The design architect is one of them. It is also the one most frequently misunderstood — including, occasionally, by the people commissioning it.

The confusion has consequences. Clients who assume a design architect will carry a project to completion are surprised when the appointment ends. Clients who assume the role is purely aesthetic underestimate how much of a building's cost and buildability is fixed during it.

What the role covers

The design architect is responsible for establishing what the building is: its form and massing, how it sits on its site, how people move through it, the arrangement and proportion of its spaces, the character of its materials and façade, and the logic that holds those decisions together.

In practical terms that usually means:

  • Interrogating the brief — often rewriting it, because the brief a client arrives with is frequently a description of a solution rather than a problem
  • Analysing the site: orientation, views, prevailing wind, access, adjacency, and whatever the planning framework permits
  • Testing massing options against yield, cost and experience
  • Developing the architectural language — façade strategy, material palette, the way the building meets the ground and the sky
  • Producing the design documentation that everyone downstream builds from

At COMO Residences on Palm Jumeirah, Benjelloun & Partners acted as design architect for Nakheel. The work in that role included the tower's twisting silhouette — a form that gives every residence an open diagonal view to the sea — and the terraces and planted balconies that soften the boundary between inside and out. Those are design architect decisions. They were taken early, and they determine much of what the building is.

Where the role ends

A design architect appointment typically concludes when the design is sufficiently developed for another party to take it into technical documentation and construction. That party is variously called the architect of record, the executive architect or the delivery architect depending on market convention.

That practice produces the construction documentation, handles the technical detailing, and carries the professional and statutory responsibility for what is built. It is substantial, skilled work, and it is not a lesser role — it is a different one.

The handover is where projects are most often damaged. A design intent that is not documented with enough clarity, or a delivery team that treats the design as a starting suggestion rather than a specification, produces buildings that resemble the renderings only loosely. Good design architects anticipate this: they document not only what the design is but why each decision was taken, so that when a substitution is proposed later, the consequence is legible.

Why developments split the role at all

The split exists for reasons that are largely practical.

Specialisation. The skills that produce a distinctive tower are not identical to the skills that produce thousands of coordinated construction drawings on a fixed programme.

Local delivery. Construction documentation and statutory submission require deep familiarity with local codes, authorities and contractor practice.

Risk allocation. Separating design from delivery lets a developer allocate professional liability where each party is best placed to carry it.

Continuity. Delivery can run for years. A design architect engaged for the design phase can move at the intensity design requires without carrying a multi-year documentation load.

The distinction from lead consultancy

A third role is often confused with both: the lead consultant, who coordinates the entire consultant team — structural, MEP, façade, landscape, acoustics and statutory inputs — under a single point of accountability.

A design architect may also be the lead consultant. Frequently it is not. Where the two are separated, the design architect influences the building; the lead consultant governs how the disciplines resolve against one another. We hold lead consultancy as a distinct capability precisely because the accountability is different in kind.

What good looks like in the role

Judged properly, a design architect's work is assessed on whether the idea survives contact with reality.

At Fairmont Residences Solara Tower in Downtown Dubai, the tower rises 270 metres with each floor stepping and shifting against the one below, producing a terraced profile that catches light through the day. A stepping form of that kind is straightforward to draw and considerably harder to build economically — every shift has structural and façade consequences. The measure of the design work is whether the idea remains intact once those consequences are absorbed.

In practice the test of a design concept is whether its central idea survives technical development and value engineering. A concept whose quality depends on a single expensive gesture is fragile. One whose quality comes from massing, orientation and proportion tends to hold, because those decisions are already embedded in the structure of the building rather than applied to its surface.

Common misconceptions

"The design architect draws the construction drawings"

Usually not, where the role is split. The design architect produces design documentation; the architect of record produces construction documentation. Different documents, different purpose, different liability.

"Design architect means the aesthetics only"

Massing, orientation, circulation and structural rhythm are design architect decisions, and they largely determine cost, efficiency and buildability. Very little of the role is surface.

"Naming a design architect is marketing"

It is attribution. On a project with several architectural parties, stating which practice held which role is simply accurate — and it is why we describe the COMO appointment as design architect rather than something vaguer.

Why the distinction matters to a client

If you are commissioning, the practical consequences are:

  • Scope. Know which role you are buying. A design architect fee does not include construction documentation unless stated.
  • Programme. Plan the handover. It is a defined moment requiring defined deliverables.
  • Design protection. Decide who safeguards intent during delivery. If nobody is appointed to, nobody will.
  • Attribution. Agree early how each party is credited. It is easier before completion than after.

Our architectural design and concept design capabilities describe how we structure these appointments, and the full set of capabilities shows where each sits in the sequence. If you are scoping an appointment and want to talk it through, get in touch.