Lighting Energy Baseline Worksheet

An energy baseline starts with what is already there

A lighting energy baseline is a plain note of the existing lighting condition before annual kWh, lighting power density or change estimates are compared. It should name the connected load, operating hours, control state, area boundary and measured-light condition. Without those fields, an energy number can look tidy while still hiding a mismatched room, changed schedule or daylight-heavy reading.

For Australian homes, small businesses, schools, offices, clinics, hospitality spaces and warehouses, the baseline should stay practical. It is not financial advice and it does not promise an energy result. It simply keeps the starting note clear enough for later comparison. The connected load to annual kWh guide explains the numeric path from watts to annual energy. This page keeps the baseline assumptions around that path.

Note the area before recording the watts

The area boundary should be written before connected load is counted. A baseline for a whole tenancy is different from a baseline for one meeting room, one corridor, one warehouse aisle or one retail counter. When a boundary is vague, later comparisons may mix areas that never had the same hours or control state.

For density checks, the measured area should match the lighting power density note. For annual energy checks, the load should match connected load and the schedule should match operating hours. Keep all three fields visible.

Connected load needs a countable line

Connected load is the lighting wattage connected to the named boundary. A good baseline says how the watts were counted: luminaire schedule, nameplate, circuit note, previous site note or measured estimate. If the count is uncertain, the uncertainty should stay beside the number rather than being smoothed away.

When luminaire output or wattage information is recorded, keep it near luminaire output notes. For density examples, compare the same area with lighting power density examples. A luminous efficacy check can sit beside a note when lumens and watts are known.

Operating hours need zone-level wording

Operating hours are often the most fragile part of a lighting energy baseline. A building may be open for long hours while a storeroom, classroom, amenities area or back corridor has much shorter active time. The baseline should name the hours band and whether the zone is normally on, occasionally on, sensor-controlled or scene-controlled during that band.

For note shape, keep operating hours lighting schedule beside lighting control zones and operating hours. The hours note should describe the period being compared, not a best-case or worst-case story.

Control state keeps the baseline honest

The same connected load can represent different energy assumptions when controls are involved. A zone may be fully on for one period, dimmed for another period and off during vacancy. A baseline should name the control state before annual kWh is calculated.

Control notes belong with lighting control notes. If dimming is part of the note, keep the observed or stated range near dimming range. If the baseline includes daylight-linked conditions, keep those readings near daylight vs electric lighting notes.

Measured-light baseline belongs beside, not inside, the energy line

Energy notes and light-level notes answer different questions. Annual kWh says how much energy a lighting group may consume under stated assumptions. A lux reading says how much light arrived at a point or plane under a stated condition. A good baseline keeps both available without treating one as proof of the other.

When measured readings are part of the baseline, keep the note near lux meter reading notes and measured illuminance. A repeat set can be summarised with lux meter average only when the same plane and condition are grouped. The measuring sequence itself sits with how to measure lux levels.

Annual kWh and density comparisons need traceable inputs

Once the baseline fields are recorded, annual kWh and density estimates can be compared without losing the assumptions. Annual kWh needs connected watts, hours and any control-state factor. Lighting power density needs connected watts and area. Efficacy needs lumens and watts for the same luminaire or group.

For formulas, keep annual lighting kWh formulas close to business lighting energy notes. A numeric estimate can sit beside lighting power density, energy change comparison or luminous efficacy when the inputs remain visible.

Keep replacement scenarios distinct from the baseline

A baseline can later be compared with another lighting condition, but the existing note should stay intact. Do not overwrite the old connected load, hours or measured-light condition with a proposed condition. Make a separate comparison row so the existing condition, changed condition and assumptions can be read side by side.

The lighting power density and energy use guide helps keep watts per square metre distinct from annual kWh. The lux meter before and after notes page helps when measured readings are repeated under changed conditions.

Compact lighting energy baseline note

A compact baseline note can sit in a spreadsheet, site note or content table. The important part is that every comparison points back to the same boundary, watts, hours, control state and measured-light condition.

The baseline is clearest when it stays modest. It notes the existing Australian lighting condition before comparison, names the assumptions, and keeps measured illuminance distinct from annual kWh. That makes later estimates easier to read without presenting the page as advice about money, regulation, rebates or guaranteed energy outcomes.