DAYLIGHTING

A white-label report engine for daylight & sunlight consultants

Your BRE 209 report, automated, under your name.

Send the model and the engine runs every BRE 209 test on the real geometry: sky at the neighbours' windows, daylight inside the rooms, sunlight hours, sun on the garden. You get back the whole report, laid out and ready for your signature.

0708091011121314151617 21 JUN 21 MAR / SEP 21 DEC E 90°135°S 180°225°W 270° 0°15°30°45°60°
SUN PATHS — LONDON 51.5°NCOMPUTED BY THIS ENGINE · DEV vs SPA ≤ 0.011°
≤ 0.13 pp
VSC dev. vs Radiance, obstructed cases
≤ 0.09 pp
3D mesh ray-cast vs Radiance
45/45
Independent checks passing
0.011°
Solar position vs NREL SPA

Turnaround

The whole report, in minutes.

Every test runs in seconds on a real house.

Deterministic

No AI.

Every figure is computed from the standard's own definitions — nothing guessed, sampled or generated. The same job gives the same numbers, every time, so what you sign today still stands tomorrow.

AThe report

The whole report, with everything you need

Every BRE 209 test, for every window, room and garden the scheme touches — laid out as a finished document under your practice's name, ready for your signature.

TestFamilyWhat it answersBRE 209
Vertical sky componentDaylightDoes each neighbouring window still see enough sky — before and after, with the ratio to its former value§2.2
Daylight distribution & no-sky lineDaylightHow much of each room still sees the sky, and where the line falls§2.2, App C
Daylight factorDaylightIs the room still bright enough inside — mean, median and the share above target across the working plane§2.1
Probable sunlight hoursSunlightSun at each window over the year and in winter, and whether the neighbour loses noticeable sunlight§3.2
Sun on the groundSunlightDoes the garden keep two hours of sun on 21 March over at least half its area§3.3
Shadow studiesSunlightWhere the shadow falls at each hour, existing beside proposed, and the sun the extension takes§3.3

Around the results, everything a signed report carries: the renders, the sun it was cast by, the method and its limits, the published error bounds, the references, and what a second person would need to reproduce it. Every figure says where it came from — your model, a photograph, a survey, or typed in by hand — so a reading off a photograph can never pass for a survey.

A2Worked example

The rear-extension question, answered

Neighbour existing dwelling Proposed extension · 3.0 m sky lost to extension 25° check Window centre · 1.5 m AFL · faces the garden Section · not to scale
VSC · before39.60 %
VSC · with extension29.56 %
Ratio to former value0.746
BRE test — ≥ 27 % or ≥ 0.8 × formerPASS on ≥ 27 %
Garden 2-hour area · 21 Mar87.5 % → 65.6 % PASS

Real output from the validated engine on this geometry. The same before/after pair drives the §3.2 sunlight verdict at the window — annual and winter sunlight hours, and whether the neighbour loses noticeable sunlight. Change the extension depth and run it again in seconds.

BThe app

Made for how you work

We supply the whole app and every service behind it — built around a certifier's job, from the drop to the signed report.

01

Drop the model

Your IFC, and which side you act for — asked once. The neighbourhood comes in by itself: survey heights, mapped outlines, facade photographs.

02

Check the reading

Your file exactly as the engine read it. Verified writes a fingerprint into the report; Something is wrong stops it there.

03

The report

Every BRE 209 test, for every window, room and garden — laid out under your name, in minutes.

04

Sign and send

Under your name, with no watermark. Every delivery is recorded — to whom, and when.

06

Possibilities

What would change the result: where the proposal is free, where it costs sky but stays within guidance, where it makes no difference.

05

Correct what failed

Click the window. Three ways out: our reading of their window, the neighbour's room, or the proposal. Free to prepare.

07

Every revision kept

A sent report is never touched. The next one stands beside it, and what changed is worked out, never typed.

The job in one place

  • Clients
  • Sites
  • Councils
  • Case numbers
  • Deadlines
  • Revisions
  • Refusals & their grounds
  • Deliveries

The demo is a worked practice with eight jobs, a finished report and a real IFC model to run. Nothing you do in it is charged, and nothing leaves your browser.

CSecurity

Safe by design

Your client's drawings stay in your hands. Nothing can be read on the way, and every report you send is on a record that cannot be rewritten.

  1. No NDA needed: stateless by design

    Your model never leaves your computer — only the measurements taken from it cross. And our engine is a stateless machine: it holds nothing between runs, so by design there is nowhere for your data to stay.

  2. Nothing lost or read on the way

    On top of standard HTTPS, what crosses is split into three encrypted pieces. No piece means anything on its own.

  3. A ledger for your protection

    Every report, revision and delivery is sealed to the one before. Nothing can be rewritten, so if a report is challenged you can show what you sent, when, and from what.

DValidation

Proven in the open

Every test is checked against Radiance and published references, and the error bounds are published. The whole record was re-run on 24 September 2026 with zero failures.

EAccess

Built for the consultant who signs

You certify; we supply the engine and the document. Your practice's name, logo and signature block go on the cover and on every page, and ours goes nowhere, with no watermark. The judgement calls stay yours: the neighbour's assumed layout, which rooms count, and which side you act for.

Enterprise & evaluation — talk to us directly

We onboard practices one to one, by enquiry: your first study is run with you on your own geometry. Tell us the practice, the kind of schemes you assess, and the format you work in, and we'll set you up. enterprise@kairoico.com