INTERNATIONAL FACADE & LIGHTING CONSULTANCY
Ideas, principles & practical guidance

Better questions lead to better buildings.

Editorial notes on facade design, lighting strategy and the coordination decisions that influence a building’s long-term performance and identity.

High-rise building facade

What should an early facade brief include?

A practical starting checklist for design intent, context, performance expectations, budget, programme and interface responsibilities.

Read article ↗
Modern facade detail

Integrating facade lighting before details are fixed

Why fixture location, access, cabling, glare and control intent should be part of early coordination—not an afterthought.

Read article ↗
Architectural geometry

Design intent and buildability can work together

How clear assumptions, interface reviews and decision logs reduce ambiguity across the design process.

Read article ↗
Facade design · Practical guide

What should an early facade brief include?

An effective facade brief describes more than the desired look. It gives the project team a shared basis for comparing options, understanding risk and coordinating decisions as the design develops.

1. Establish the architectural objective

Describe the building’s intended character, the relationship to its context, key views, desired transparency or solidity, and the elements that should carry the strongest visual emphasis.

2. Set the project constraints

Record location, orientation, environmental exposure, planning considerations, programme, procurement route, budget assumptions and any known access or maintenance constraints.

3. Define performance expectations

Identify the project-specific requirements for thermal performance, weather protection, acoustics, daylight, fire strategy, safety, durability and cleaning. The relevant specialists and local codes should be identified early.

4. Clarify interfaces and responsibilities

Map the interfaces between facade, structure, interiors, MEP, signage, external shading and architectural lighting. Agree who provides information, who reviews it and when decisions are required.

5. Agree deliverables and review gates

Set out what each stage must produce, how options will be evaluated, who approves decisions and how design changes are recorded. A clear brief helps keep the process focused and accountable.

Lighting design · Practical guide

Integrating facade lighting before details are fixed.

Architectural lighting has a direct relationship with the facade: it needs a suitable mounting position, a reliable route for wiring, access for maintenance and a clear relationship with the material it illuminates.

Early coordination can help the team consider fixture visibility, beam direction, spill light, glare, colour consistency, control zoning and replacement access. Lighting scenes should support the building’s identity and intended use rather than rely on maximum brightness.

Where required, specialist lighting calculations, mock-ups and product submittals should be undertaken by appropriately appointed professionals. A coordinated concept gives these later tasks a clear design direction.

Technical coordination · Practical guide

Design intent and buildability can work together.

Design intent is easiest to preserve when it is expressed in clear drawings, agreed material references, coordinated interfaces and traceable decisions. It should not depend on one image or a verbal understanding alone.

Useful practices include identifying critical junctions, documenting assumptions, recording review comments, agreeing sample and mock-up criteria, and defining how proposed substitutions will be evaluated. These steps do not remove every site challenge, but they create a better framework for discussing them.

Project teams should also be clear about review responsibilities: a design review is not automatically a certification of every aspect of a contractor’s design or installation. Scope and professional responsibilities need to be explicit.

Planning a building facade or architectural lighting project?

Bring your vision to the table. Let’s discuss the brief, constraints and design ambition.

Start a conversation ↗
◔Discuss a project