NIGHT PROGRAMME
What happens after dark and which parts of the place need to behave differently.
For public-realm architecture teams
Senior after-dark expertise, only when your project needs it.
Add specialist capability without building a lighting department.
We work inside your existing architectural workflow - carrying design intent into technical lighting without adding permanent headcount or taking over authorship.
25+ years in architectural lighting · public realm · international practice
02
After dark, the same place becomes a different design problem.
Architectural intent is the starting point. Before engineering, it has to be developed for darkness, spatial hierarchy, changing use, optical behaviour, integration, identity and time.
Architectural intent
- Quiet
- Event
- Water
- Landscape
- Movement
- Identity
After-Dark Design Judgment
Darknesswhat should remain dark
Spatial hierarchyprimary, secondary, background
Public realm after darkmovement, use, perception
Temporal statesevening, events, late hours
Adaptive infrastructurechanging uses, not one fixed scene
Custom integrationmounting, optics, details
Heritage & place identityculture, material, memory
Media / dynamic statesarchitectural relevance
Technical definition
- lx
- cd/m²
- optics
- mounting
- controls
- loads
- compliance
03
After-Dark Design Intent Sprint
From architectural concept to an after-dark brief your technical team can use.
5-8 working days + one technical review
A compact capability your team can switch on when a project needs it.
InputYOUR ARCHITECTURAL CONCEPT
SPATIAL HIERARCHY
What becomes primary, what stays background and where darkness should remain.
STATES & BEHAVIOUR
How the environment changes through the evening, events, seasons and operating conditions.
VISUAL VERIFICATION
Key evening views and states allow the architectural team to see and test the design before technical development.
Key evening states are tested before engineering.
TECHNICAL PRINCIPLES & CONSTRAINTS
The relationships, decisions and constraints that need to survive engineering.
OutputBRIEF FOR YOUR ENGINEER / MANUFACTURER
ENGINEER / MANUFACTURERFIRST TECHNICAL ITERATIONONE SUPREMATICS REVIEW
04
Your team remains the author.
We join between concept and technical development, develop the after-dark layer, then step out. Your architecture, engineer/vendor relationships and delivery structure stay intact.
Your architectural teamowns concept + project decisions
Suprematicstemporary after-dark specialist
Your engineer / manufacturertechnical delivery
Visible specialist or white-label, depending on how your team works.
05
Start with one live project.
We join briefly, develop the missing after-dark layer and hand the project back to your existing workflow.
- 01Concept ready
- 025-8 working days
- 03Engineer / vendor handoff
- 04First technical iteration reviewed
Keep the capability only if it proves useful.
Bring us a live project.
If a project is moving from concept into technical development, that is usually the right moment to talk.