Annual lighting savings depend on load, hours and rate
A savings estimate is strongest when old load, new load, count, hours and the entered cents/kWh stay visible. The result does not choose a replacement fitting or layout; it annualises the lighting energy difference already described by the inputs.
Energy estimate sequence
The savings record stays reliable when the light-output decision is kept separate from the annual energy arithmetic.
- 1Confirm the compared group
Match old watts, new watts and count to the same room, zone or repeated group.
- 2Check the lighting basis
Confirm that output, count and layout have been settled in the relevant lighting note.
- 3Enter operating hours
Hours and days should follow switching, dimming and occupancy patterns.
- 4Set the energy rate
Enter the cents/kWh used for the estimate and keep it visible.
- 5Read payback separately
Payback depends on an entered upgrade cost and a positive annual AUD saving.
Application search intent fit
Route savings searches into one comparable lighting group before payback, controls and schedule assumptions are read.
| Search phrasing | Calculator record | Carry forward |
|---|---|---|
| Lighting energy savings calculator | Old load, new load, count, hours, days and cents/kWh for one lighting group. | kWh change, AUD change, schedule basis and rate assumption. |
| LED retrofit payback | Replacement case where light output and fitting count have already been checked. | Simple payback, upgrade cost basis, maintained-light note and glare or beam checks. |
| Common area running cost | Long-hour corridor, lobby or shared-area group with a clear operating pattern. | Timer or sensor state, overnight hours and controlled-zone split. |
| Negative savings or higher load | New load, count or schedule is higher for the entered case. | Reason for extra load, output gain, longer hours or changed room use. |
Assumptions to record with the output
The annual result should travel with its assumptions. Without them, the kWh and AUD figures are hard to check later.
| Assumption | Why it moves the result | Estimator note |
|---|---|---|
| Driver-inclusive watts | Input power should represent the load carried by the circuit or fitting group, not only a lamp label. | Record measured or datasheet input power where it is available. |
| Hours per day | Every extra operating hour repeats the load difference across the year. | Base the value on switching behaviour, trading hours or the operating-hours schedule table. |
| Days per year | A weekday-only office and a seven-day corridor can have very different annual totals. | Keep seasonal closures or weekend operation visible. |
| Entered cents/kWh | The dollar result changes when the entered energy rate changes, even if kWh stays fixed. | Write the rate beside the result when comparing options. |
| Upgrade cost | Simple payback depends entirely on the entered cost and a positive annual saving. | Keep supply, access and labour scope outside the energy line unless they are deliberately included in cost. |
Reading kWh, AUD and payback
The result panel separates physical energy from money. Review the kWh change first, then read the AUD and payback numbers.
| Result | Technical meaning | Review item |
|---|---|---|
| Annual kWh change | Old annual energy minus new annual energy for the entered group. | Check old watts, new watts, count, hours and days before discussing cost. |
| Annual AUD change | The kWh change multiplied by the entered cents/kWh. | Revise the rate for a new site, account period or sensitivity check. |
| Simple payback | Entered upgrade cost divided by annual AUD saving. | Treat it as a screen only; it is not a finance or maintenance model. |
| Negative saving | The new connected load is higher for the entered count and operating period. | Confirm whether extra light, a different count or a longer schedule was intentional. |
Boundary of the energy number
The annual estimate is an arithmetic lighting-energy check. It is not a metered account forecast and does not approve a lighting design.
| Open item | Why it remains outside | Technical follow-up |
|---|---|---|
| Dimming and scenes | A group may spend part of the year below full output. | Create a separate case or keep the dimming assumption with the operating-hours lighting schedule. |
| Daylight and occupancy control | Controls can reduce operating hours or average load in ways a single full-load row cannot show. | Split controlled and uncontrolled zones when the pattern differs. |
| Account charges and demand items | A flat cents/kWh entry cannot model every charge on an electricity account. | Keep the rate visible and avoid presenting the result as a metered account outcome. |
| Maintenance change | Lamp life, access equipment and labour may affect the broader case without changing kWh. | Record maintenance as a separate business-case note. |
| Lighting quality | Energy reduction does not prove adequate illuminance, glare control or colour appearance. | Check room-lighting or replacement notes before relying on the energy result. |
Lock the compared group
A clean savings estimate starts with one defined lighting group. That group might be a room, a row of fittings, a tenancy zone or a repeated common-area type. The old watts, new watts, count and operating schedule need to describe that same group.
Whole-building summaries become weak when unlike spaces are blended too early. Offices, amenities, corridors, exterior signs and stores often run on different schedules. Build the estimate from clear groups first, then total the rows if a building-level figure is needed.
Check light output before energy
Energy savings should not be accepted before the light output is credible. A lower-wattage group only helps when the replacement still suits the room, task plane, visual comfort and count. The output question belongs with the LED replacement or room-lighting note before the annual saving is relied on.
Once the lighting basis is settled, the annual energy arithmetic is straightforward. Connected watts are multiplied by the operating period and converted into kWh. The estimator's discipline is keeping the lighting note and the energy note aligned.
Operating hours carry most of the movement
A small fitting in a long-running area can save more annual energy than a larger fitting used occasionally. Corridors, back-of-house rooms, hospitality spaces, car-park entries and shared amenities can have operating profiles that are nothing like a bedroom, meeting room or seasonal store.
Hours per day and days per year should therefore be written as assumptions. If daylight control, occupancy sensing or manual switching changes the pattern, split the lighting group into separate cases rather than burying the effect inside one average.
Treat the energy rate as a stated assumption
No current account structure is built into the estimate. The entered cents/kWh belongs to the person preparing the note. That keeps the result usable across Australian sites and contract periods without implying that one rate represents every account.
A reused estimate should carry the rate used at the time. When the rate changes, the kWh result remains the same but the AUD result changes. Keeping those numbers separate makes later sensitivity checks quick and transparent.
Read kWh before dollars
Annual kWh is the physical energy result. It stays tied to watts, count and run time, so it is the best first check for plausibility. If a small group shows a very large saving, the hours or fitting count probably needs another look.
Annual AUD is the same energy movement priced at the entered rate. It is useful for comparison, but it is less stable than kWh because the rate can change. Keep the kWh and AUD lines together so a future reviewer can update money without rebuilding the lighting case.
Controls need explicit treatment
Dimming, daylight response and occupancy control can change a lighting group's annual energy in two ways. They may reduce output while the group is on, or reduce the hours that the group operates. A single full-load row cannot show those effects unless the assumption is written down.
For early estimating, a full-load baseline is often the cleanest case. Add a separate controlled case when the control pattern is strong enough to justify it. That keeps the baseline visible and avoids hiding control savings inside an unexplained hours value.
Negative savings can be valid
A negative annual saving usually means the entered new load is higher than the old load, or the new count has increased enough to offset a lower watts-per-fitting value. That is not automatically wrong. It may reflect a deliberate lift in light output or a room that was previously under-lit.
Read that result as an energy cost for a lighting improvement, not as an energy-saving retrofit. The lighting justification should sit beside the cost result so the reason for the higher load is visible.
Keep the energy note with the lighting note
The best energy record sits beside the lighting record. It should show old watts, new watts, count, operating period, kWh difference, AUD difference and any entered upgrade cost. The lighting note should still show output, count, target assumptions and any control basis.
That pairing prevents a low-energy result from being mistaken for a good lighting result. Energy is one side of the retrofit case. Illuminance, beam spread, glare, colour appearance and controls still decide whether the room works.