Coordinating Architects, MEP Engineers & Lighting Designers in Dubai

Stakeholder roles defined

Before a RACI matrix can be populated, each stakeholder's scope boundary must be clearly defined. Ambiguity about scope leads to both gaps — activities that no one believes are their responsibility — and overlaps — activities where two parties produce conflicting outputs. The following definitions apply to a typical Dubai facade lighting project where the client has engaged a lighting designer, an MEP consultant, a facade consultant, and a main contractor.

Client or owner is the ultimate decision-maker and budget authority. The client approves design concepts, authorizes procurement, and accepts practical completion. On developer projects, the client's representative may be a project director, a development manager, or a facilities management representative — each with different technical understanding and approval authority. Identifying who holds each approval authority at the project outset — and confirming their response time commitments — is a foundational coordination step.

Architect holds design leadership responsibility. For facade lighting, the architect's role is to ensure that the lighting design is consistent with the architectural design intent, integrated into facade drawings, and represented accurately in DRC and DM submissions. The architect does not design the lighting system — that is the lighting designer's scope — but must approve the lighting designer's output as consistent with the building design before it proceeds to engineering.

MEP consultant is responsible for the electrical infrastructure that powers the facade lighting system. This includes the power supply circuit from the distribution board to the luminaire circuit, cable sizing and routing, DEWA submission drawings, and BMS integration at the electrical interface. The MEP consultant does not specify luminaires or design lighting scenes; their scope ends at the luminaire's terminal connection.

Lighting designer is responsible for the photometric design, product specification, control strategy, and commissioning oversight. The lighting designer defines what luminaires are used, where they are positioned, how they are aimed, what scenes they create, and how the control system is configured. The lighting designer's scope does not typically include structural engineering, electrical infrastructure design, or BMS programming beyond the lighting controls gateway.

Facade consultant is responsible for the performance of the building envelope. For facade lighting, the consultant must approve all bracket mounting systems (structural load compliance), cable penetrations (fire-stop and weatherproof detailing), and any modifications to the facade system required for luminaire integration. The facade consultant does not specify lighting products but must confirm that the specified mounting method is structurally and hygro-thermally acceptable.

Main contractor is responsible for delivering the physical installation. The contractor manages subcontractors, coordinates site access, maintains the construction program, and ensures that installation quality meets the specification. The contractor does not design the system; their obligation is to build what the design requires and to raise Technical Queries or RFIs when the design is incomplete or unclear.

RACI matrix: 10 stakeholders × 8 activities

The RACI matrix below defines accountability (A), responsibility (R), consultation requirement (C), and information recipient (I) for the eight core coordination activities in a facade lighting project. Only one party can hold A (accountable) for each activity; multiple parties may hold R, C, or I.

Key: A = Accountable, R = Responsible, C = Consulted, I = Informed, — = Not involved

This matrix should be issued to all stakeholders at the project kickoff meeting and updated when the project organization changes. The most common RACI failure in Dubai facade lighting projects is the absence of a defined accountable party for DM permit submission — a gap that leaves each consultant assuming that another is leading the submission process. The architect typically holds this accountability on UAE projects, with the MEP consultant responsible for the electrical submission elements.

Architect–lighting designer interface

The architect and lighting designer operate on the same design object — the facade — from different disciplinary perspectives. The architect is responsible for the building's visual character, material palette, and massing; the lighting designer is responsible for how that character reads at night. Misalignment between these perspectives — discovered late — generates the most costly redesign cycles in the facade lighting process.

Design language translation is the first coordination task. The lighting designer must translate the architect's design narrative — often expressed in aesthetic terms rather than technical parameters — into a lighting language: correlated color temperature range, luminance levels, beam distribution strategy, and animation behavior. A formal design intent workshop at the start of Phase 2, attended by both the architect and the lighting designer, with the client representative present, establishes shared design language before drawing production begins. The output is a design intent statement — one to two pages — agreed and signed by all parties, that serves as the reference document for all subsequent design reviews.

Rendering approval is the primary design coordination mechanism during Phase 2. The lighting designer produces nighttime visualizations of the facade; the architect reviews them for consistency with the architectural vision; the client approves the agreed rendering before the design is finalized. Rendering approval is not merely aesthetic — it freezes the product selection, zone boundaries, and coverage strategy that the engineering phase will work from. Changes to the design after rendering approval are change orders; changes before are part of the design process. Establishing this boundary explicitly, in the project's scope-of-work documents, prevents the scope of the design phase from expanding indefinitely.

Facade drawing coordination requires the lighting designer's fixture positions to be incorporated into the architect's facade elevation and plan drawings before engineering begins. This is a logistical coordination step: the lighting designer issues a fixture location drawing to the architect; the architect incorporates it into the architectural drawing set; the MEP engineer scales cable routes from the architectural drawings. If this sequence is not managed, the MEP engineer routes cables from a lighting drawing that has since been superseded by an architectural revision, and the clash detection exercise in Phase 3 reveals conflicts that could have been avoided.

MEP coordination: power supply, cable routing, BMS integration

MEP coordination for facade lighting is frequently the source of the most significant on-site coordination failures. The three coordination interfaces — power supply location, cable routing, and BMS integration — each require specific information exchange between the lighting designer and the MEP consultant at defined stages.

Power supply coordination begins with the lighting designer providing the MEP consultant with a lighting load schedule: each circuit's connected load in watts, the required supply voltage and frequency, the power factor of the drivers, and any special power quality requirements (such as flicker-free supply for video-capture facades). The MEP consultant uses this data to size distribution boards, circuit breakers, and cable runs. If the lighting load schedule is issued after the MEP engineer has already sized the electrical infrastructure — a common failure on fast-track projects — the MEP must revise their design, which generates a change order and a program delay. The lighting load schedule should be issued at the end of Phase 2, not the end of Phase 3.

Cable routing coordination requires agreement on the physical path from each distribution board to each fixture or driver enclosure. On high-rise towers, this involves cable routes through risers, across floor plates, and through the facade's cavity or cladding system. Facade cavity routing is particularly sensitive: the facade consultant must confirm that cable containment within the facade cavity does not compromise the cavity's ventilation function or create thermal bridging pathways. The BIM coordination model is the definitive tool for resolving cable routing conflicts; a 2D drawing overlay review is the minimum acceptable approach for projects without a BIM requirement.

BMS integration is the most technically complex MEP coordination interface. When the facade lighting control system connects to the building BMS — typically via a gateway protocol such as BACnet, Modbus, or KNX — the following must be coordinated in advance: the BMS protocol and version; the number and type of integration points (setpoints, status feedback, scheduling); the physical connection point (BMS panel location and available ports); the commissioning sequence (who commissions the gateway: the lighting controls contractor or the BMS contractor); and the ongoing responsibility for gateway configuration changes during the DLP. This coordination scope should be documented in a BMS Integration Protocol issued by the project manager and signed by both the MEP consultant and the lighting controls engineer before the controls system is ordered.

Facade consultant coordination

The facade consultant's role in facade lighting coordination is often underestimated. Their approvals — of bracket loads, penetration details, and thermal bridges — are prerequisites for installation; without them, the installer cannot proceed, and the main contractor cannot defend the installation against the facade warranty claims that arise when these approvals are absent.

Bracket load approval requires the lighting designer or bracket manufacturer to issue a mounting loads schedule to the facade consultant, showing the dead load (fixture and armature weight), the wind-induced dynamic load, and the moment at the bracket's fixing point to the facade. The facade consultant checks these loads against the facade system's permitted point load capacity and the fixing substrate's structural capacity. On aluminum curtain wall systems, permitted point loads are typically defined in the facade engineer's structural calculation package; on precast concrete facades, they are derived from the structural engineer's drawings. Loads that exceed the facade's capacity require either a lighter fixture, a revised mounting strategy, or a structural reinforcement of the facade substrate — all of which affect the design and the cost.

Penetration details must be reviewed by the facade consultant to confirm that cable entry points maintain the facade's fire compartmentalization, air tightness, and waterproofing performance. The detail must show the cable entry method, the intumescent sealing system used to restore fire compartmentalization, and the weatherproof boot or caulked termination used to maintain the facade's weather barrier. Generic penetration details that do not reference the specific facade system in use are not acceptable to most facade consultants; project-specific details, reviewed and stamped by the facade consultant, are required.

Thermal bridging is a coordination issue that applies specifically to facades with thermal insulation continuity requirements, such as LEED or Al Sa'fat Platinum-rated buildings. Metal brackets that penetrate the thermal insulation layer create thermal bridges that reduce the facade's thermal resistance and generate condensation risks. The facade consultant calculates the linear thermal transmittance (psi value) of each bracket penetration; if the aggregate thermal bridging from the lighting mounting system exceeds the permitted value, the bracket design must be revised with thermal break elements. This calculation must be performed before the bracket system is ordered, not after installation reveals a condensation problem.

Contractor management

The main contractor — and their specialist subcontractors for facade lighting installation — are the parties who convert design into physical reality. Effective contractor management during installation combines clear contractual obligations, a structured technical query process, and regular site coordination meetings that identify and resolve issues before they become defects or disputes.

The Technical Query process is the formal mechanism by which the contractor seeks clarification on design intent, specification interpretation, or site conditions that differ from those shown on the drawings. All TQs should be submitted in writing, numbered sequentially, and addressed to the project manager, who routes them to the relevant consultant. The project manager should set and enforce response time standards — typically five working days for standard TQs, two working days for urgent site-affecting TQs. TQs that are not responded to within the agreed time become a contractor's justification for a program extension; tracking overdue TQ responses is a direct project manager responsibility.

RFI tracking serves a similar function for requests that require design clarification rather than specification interpretation. The RFI register should record: RFI number, subject, date submitted, responsible party for response, target response date, actual response date, and resolution description. At project completion, the RFI register provides the audit trail for any as-built deviations from the original design drawings — an essential reference for as-built drawing preparation and for DLP defect investigation.

Site coordination meetings for facade lighting installation should be held weekly, attended by the contractor's site supervisor, the MEP consultant's resident engineer, and the lighting designer for critical installation milestones. The agenda should address: installation progress against the program, materials on site versus required, outstanding TQs and RFIs, upcoming access and access equipment requirements, and any quality non-conformances identified since the last meeting. Meeting minutes, distributed within 24 hours, create the record of agreed actions and prevent the recurrence of the same coordination failure at the next meeting.

Communication protocols

Communication protocols define how information moves between project stakeholders — what format, through which channel, and with what response time obligation. Without defined protocols, project communication defaults to informal channels (phone calls, WhatsApp messages) that leave no audit trail and frequently result in misunderstood or lost information.

BIM coordination is the primary information exchange medium for design coordination on BIM-mandated projects. The facade lighting model — typically a Revit model provided by the lighting designer with luminaire families, cable containment, and bracket geometry — should be uploaded to the Common Data Environment (CDE) on a defined revision cycle, typically weekly during the design phase. Clash detection between the lighting model, the MEP containment model, and the facade model should be run by the BIM coordinator after each model upload, with a clash report issued to all discipline leads within two working days. Unresolved clashes after 10 working days should be escalated to the project manager for resolution.

Meeting cadence should be defined in the project's communication plan. Design coordination meetings (architect, lighting designer, MEP, facade consultant) should meet fortnightly during Phase 2 and weekly during Phase 3. Regulatory submission review meetings (project manager, architect, MEP consultant) should meet weekly during Phases 3 and 4 until all approvals are received. Construction site meetings should be weekly from the start of Phase 6. Commissioning coordination meetings (lighting designer, controls engineer, MEP consultant, BMS contractor) should be daily during active commissioning weeks.

Drawing register management ensures that all parties are working from the current drawing revision. The project manager should maintain a master drawing register listing every drawing in the project, its current revision, and the date it was issued to each stakeholder. Superseded drawings should be clearly marked and withdrawn from circulation. The most common quality failure in facade lighting installation is a contractor working from a superseded drawing — either because the current revision was not distributed promptly, or because the contractor's site team held a physical print of the old revision that was never replaced.

For the complete project timeline and phase-by-phase management procedures, see 8-Phase Facade Lighting Timeline. For procurement coordination and specification documentation, see Procurement Specifications.

Frequently asked questions