How to Design Towards WELL Lighting Compliance Without Outsourcing Every Decision
A project team can own most of the lighting work. What it cannot do is turn a certification process into a self-declaration or leave evidence until the end.
Can you design towards WELL lighting compliance without hiring a specialist for every decision? Yes. Can you design casually, tick a few boxes and declare the project certified? No.
That distinction matters because too many teams swing between two extremes. Either they outsource the whole topic and stop understanding the design, or they reduce WELL lighting to a lux target and a tunable-white fixture schedule. Both approaches miss the point.
You can own the design without pretending you can self-certify the outcome.
Who should own what?
| Workstream | Primary owner | What lighting must contribute |
|---|---|---|
| Scorecard and strategy | WELL AP / project lead | Clear interpretation of which lighting requirements affect design and evidence |
| Daylight and facade | Architect / facade / sustainability | Exposure goals, glare risk, shading logic and interior coordination |
| Electric lighting | Lighting designer | Visual task, vertical illumination, glare, spectrum, quality and energy logic |
| Controls | Lighting / electrical / integrator | Narrative, zoning, scenes, schedules, override and commissioning intent |
| Product evidence | Designer / manufacturer / contractor | Verified photometry, spectral data, colour, flicker, driver and controls |
| Performance verification | Authorised testing process | A commissioned system and clear records ready to be measured |
Start with the scorecard, not the fixture catalogue
Before selecting a single luminaire, confirm the WELL version, project type, boundary, space types and Light concept features being pursued. The applicable requirements can change based on how the project is registered and which optimisations the team selects.
Create a simple compliance matrix. For each Light feature, record the design requirement, responsible discipline, drawing or calculation needed, product data needed, site verification method and status.
This sounds administrative, but it changes the entire workflow. It stops the lighting team from discovering at the end that a requirement depended on interior surface reflectance, workstation planning, shading, controls or commissioning information that nobody owned.
Design daylight first
WELL does not treat electric light as the only source of useful light. Daylight, views, shading and occupant exposure are part of the conversation.
Map the occupied zones against the façade and daylight availability. Identify where people will spend long periods, where glare is likely, where blinds will remain closed in real operation and where electric light must support the space even on difficult days.
A façade that produces high daylight on paper but forces occupants to close blackout blinds for most of the day is not a successful lighting strategy. Daylight quantity, glare management and the actual use of the space must be designed together.
Separate visual light from circadian light
Horizontal lux on a desk answers a visual task question. Circadian-effective exposure is more closely connected to light reaching the eye, its spectrum, timing and duration.
Do not assume that a space meeting a horizontal illuminance target automatically meets a circadian objective. Do not assume that a higher CCT automatically solves it either.
Where the selected WELL pathway requires melanopic or circadian-related performance, use the current approved metric and measurement plane. Record the assumed eye height, direction, schedule, daylight contribution and electric-light contribution. The project should be able to explain how the result was achieved, not only display a final number.
Control glare through the whole room
Glare is not solved only by buying a “low-glare” downlight. Source luminance, shielding, luminaire size, spacing, room reflectance, observer direction, workstation orientation and screen position all matter.
Surface reflectance is particularly easy to overlook. A dark ceiling and dark walls can increase contrast and change the visual experience even when the luminaire itself has good optics. Interior design decisions therefore belong inside the lighting compliance workflow, not outside it.
Run the relevant glare assessment using the actual geometry and actual photometric files. If the ceiling height, desk layout or luminaire changes, recalculate.
Specify controls as an operating sequence
“Provide daylight sensors and dimming” is not enough.
State which zones respond to daylight, which are occupancy-controlled, what the minimum dim level is, what happens after hours, how manual override works, how tunable-white scenes behave and what settings are protected after commissioning.
A system can be technically capable of supporting WELL and still fail because the final scene programming does not match the design intent. The sequence of operations is part of the lighting design.
Build the documentation while designing
Do not wait until certification submission to assemble proof. Maintain the fixture schedule, photometric files, calculation reports, spectral data where needed, reflectance assumptions, control narrative, annotated plans and product approvals as the design develops.
Every drawing revision should update the compliance matrix. Every substitution should trigger a technical review. Every site change that affects light distribution, reflectance or controls should be recorded.
This is where many teams spend unnecessary money on consultants. The consultant is not being paid only for specialist knowledge. They are being paid to reconstruct decisions that were never documented.
What you can own internally, and where to bring help
Most project teams can internally manage requirement mapping, lighting intent, preliminary calculations, fixture data, control strategy and the documentation structure. Bring in specialist support for ambiguous pathways, complex circadian modelling, difficult daylight and glare conditions, formal certification interpretation and performance verification.
Alya can translate requirements into project checks, connect those checks to drawings, calculations, product records and control narratives, and show what evidence is still missing. Alya does not certify WELL. It should never pretend to.
Compliance should be the by-product of a well-run design process, not a rescue operation three weeks before submission.
The goal is not to avoid expertise. It is to stop outsourcing understanding. A strong team should know what it is designing, why the requirement exists, how it will be tested and what evidence will survive handover.
Primary Sources and Fact-Check Notes
- WELL Certification overview Official certification-process overview.
- Understand the architecture of WELL v2 Official explanation of concepts, preconditions and optimisations.
- What is performance verification? Official description of on-site, third-party assessment.
- ANSI/IES TM-39-25 Current IES flicker reference.
Fact-checked 25 August 2026. Confirm the adopted standard and local requirements for each project.