Lighting carbon estimate notes
Lighting carbon estimate turns a lighting kWh amount and an entered emissions factor into a simple carbon figure.
Carbon sequence
Enter one lighting energy amount, then apply a user-entered emissions factor.
- 1Enter lighting kWh
Use the energy amount for the same group or period.
- 2Add the factor
Enter the emissions factor used for the estimate.
- 3Read kilograms
The first output is estimated kgCO2e.
- 4Read tonnes
The second output converts kilograms to tonnes.
- 5Keep the basis visible
Note the year or source basis outside the result.
Application estimate fit
Match the search phrase to one lighting load, period and assumption set before reading the result.
| Search phrasing | Calculator case | Carry forward |
|---|---|---|
| Lighting carbon estimate | One kWh value multiplied by an emissions factor. | kgCO2e and tonnes CO2e for the entered basis. |
| Annual reporting check | A simple energy-to-carbon conversion for a lighting group. | Year, factor and reporting basis kept visible. |
| Site comparison | One lighting energy figure tested against an emissions factor. | Keep the same kWh across the comparison. |
| Operational note | A quick carbon estimate for a known lighting load. | Use the chosen factor consistently. |
Reading the result
Each output belongs to a bounded lighting energy estimate and should travel with its assumptions.
| Output | Technical meaning | Review item |
|---|---|---|
| Estimated kg CO2e | Lighting kWh multiplied by the entered factor. | Keep the factor visible beside the number. |
| Estimated tonnes | Kilograms divided by 1,000. | Use the same basis as the kg result. |
| Lighting energy | The kWh basis entered for the estimate. | Do not mix periods or control states. |
| Emissions factor | The user-entered factor used in the estimate. | Keep the year or source note in the project file. |
Assumptions that stay visible
Small changes in load, hours, rate or factor can move the result, so the assumptions stay beside the number.
| Assumption | Why it matters | Where it belongs |
|---|---|---|
| Lighting kWh | The energy basis for the estimate. | Use the same period throughout. |
| Emissions factor | The factor drives the carbon result. | Keep the entered value visible. |
| Reporting year | The factor can vary by year or source basis. | Note the year if the result will be reused. |
| Comparison scope | Keep the same lighting group in one carbon note. | Do not blend unrelated areas. |
lighting energy amount before the number
A useful lighting carbon estimate estimate begins with the exact lighting energy amount, not a whole-site average. The same building can include reception lights, display lights, warehouse aisles, amenity rooms and exterior signs that all run for different hours. Naming the group keeps the load, hours and money value tied to one visible lighting job.
That boundary also makes later revision easier. If the fittings, scene level or operating period changes, the row can be revised without rebuilding unrelated areas. Write the space name, fitting family and control group beside the result so another person can check the same case later.
Connected load remains the anchor
Energy and cost estimates move when connected load changes. Count the fittings or enter the load that belongs to the named group, then keep the wattage basis visible. Complete fitting input watts are stronger than a bare lamp value because drivers, control gear and luminaire packages can change the actual load.
The connected-load note does not prove the light level is suitable. A lower load can still be too dim, glary or uneven, while a higher load may support a harder task. Keep lux, beam, colour and measured-light pages nearby when the lighting quality also needs checking.
Hours carry much of the movement
The entered reporting period can move the annual result more than a small wattage change. Seven-day corridors, hospitality scenes, office task rows, seasonal stores and after-hours security lights may all have different operating patterns even when the fittings look similar.
Enter the hours for the same lighting group named in the result. If the group has a normal scene and an after-hours scene, split those cases rather than hiding both in one average. A tidy input line with hours, days and control state is easier to revise than a single unexplained total.
Controls change energy without changing installed load
The same lighting basis can reduce energy by shortening operating time or lowering average output. Occupancy sensing, daylight dimming, timeclocks, scene presets and holiday shutdowns all change the energy case while the installed wattage may remain the same.
Keep full connected load and controlled operation visible as different ideas. That separation lets a user compare the installed capacity, the normal operating case and the reduced-energy case without implying that the electrical installation has changed.
Rates and factors are user-entered assumptions
The emissions factor is user-entered belongs beside the result because it can change while the lighting kWh stays fixed. A rate comparison, carbon estimate or simple payback note is only as current as the entered cents per kWh, emissions factor or annual saving value.
For Australian lighting notes, keep the rate date, account basis or factor source in the project file if the result will be reused. This page keeps the arithmetic transparent; it does not choose an electricity plan, account structure, rebate or finance outcome.
Read comparisons as bounded arithmetic
Energy to carbon conversion is helpful when the two cases share the same lighting group and schedule basis. Rate A and Rate B, old hours and new hours, or full output and dimmed output should describe the same load before the numbers are compared.
A comparison can show the size of a difference, but it does not decide whether the lighting change is appropriate. Light level, comfort, controls, maintenance access and site operating needs still need their own notes when they affect the decision.
Monthly, annual and period values are different
Monthly values are useful for a short period or a local cost note. Annual values are useful for longer operating schedules, carbon factors and simple payback. After-hours and shutdown values describe only the named period, not the whole lighting account.
Keep the period wording in the result. A monthly cost, an annual kWh value and a holiday shutdown saving should not be compared until the period, hours and days have been made consistent.
Australian energy estimate limits
lighting carbon estimate pages on AuLumens are planning estimates for lighting load, kWh, user-entered cost rates, carbon factors or simple payback. They do not model demand items, metered account totals, rebates, tax treatment, electrical design, emergency lighting or certification.
It is a simple carbon estimate, not a formal emissions inventory. Keep account-specific charges, landlord agreements, emissions reporting basis and electrical installation details in the appropriate site file. The value of the lighting estimate is that it records the load, period and assumptions before those wider checks begin.
A concise calculation note
A readable note includes the lighting group, connected load, operating period, output state, user-entered rate or factor, and whether the result is monthly, annual or limited to a named period. For split cases, include both sides of the comparison.
Keep annual kWh and energy-saving pages nearby when the same group also needs cost or period notes. That context makes the result practical. Another person can change the hours, revise the rate, adjust the control state or compare the result with measured energy data without guessing how the original number was produced.