Lighting Operating Hours: How to Verify Them During an Audit

Short answer: Verify lighting operating hours by control group, using the site schedule plus evidence of when the lights actually run. Account for cleaning, overtime, holidays and existing controls. Keep the source and date beside each annual-hours assumption before using it in a savings forecast.
Introduction
An ESCO can measure fixture watts carefully and still overstate savings if the hours are wrong. A distributor can make the same mistake by applying one building schedule to offices, storage rooms and exterior lights.
This guide focuses on checking the hours input during a commercial lighting audit. For the complete financial calculation, see our lighting retrofit ROI guide. The numbers below are examples, so verify every input on your own project.
Separate occupied hours from lighting hours
Ask when the lights turn on and off, not just when the business opens. A facility open from 8 a.m. to 5 p.m. might switch lighting on earlier for receiving and leave it on later for cleaning. A storage room inside that facility might have an occupancy sensor and operate for much less time.
Start with groups that share a control and usage pattern. Record the room or zone, fixture group, normal schedule, existing controls and exceptions. Split groups when their lighting operation differs materially. Similar fixtures do not necessarily have similar hours.
Audit question | What to retain |
Who switches or schedules this group? | Staff role, timer or control-system reference |
When are lights actually on? | Start/stop times by day type, including after-hours work |
Which days are exceptions? | Holidays, shutdowns, overtime and seasonal changes |
What supports the estimate? | Interview date, schedule document, trend or logger record |
Watch for groups that ignore the building schedule entirely. Photocell-controlled exterior lighting runs dusk to dawn, which is roughly 4,000 to 4,400 hours a year depending on latitude, whether the building is open or not. Timer-controlled exterior lights may switch off at a set time, so check the actual setting. Stairwells, exit paths and other lighting that must stay on run close to continuously. Applying the office schedule to these groups is one of the most common hours errors in a lighting audit.
Choose evidence that fits the decision
For an early budget, a documented facility-manager interview and schedule review may be enough to establish a preliminary assumption. Identify it as estimated. Ask someone who knows the evening and weekend operation as well as the daytime staff.
For a material savings commitment, resolve uncertainty before treating the assumption as fixed. Review available lighting-control trends, operator logs or temporary logging. A programmed command alone does not establish actual operation if local overrides, faults or manual switches change what the lights do.
DOE's measurement and verification options describe how documented schedules, logs, estimates and measurements can support different verification approaches. Select the approach appropriate to the project and contract; a walkthrough estimate is not automatically verified performance.
Prioritize groups where uncertain hours could change the recommendation. If the uncertain group represents most of the projected savings, a convenient building-wide default deserves more scrutiny.
Build an annual-hours calculation that someone else can check
For a simple fixed schedule, multiply hours per day by operating days per year, then document exceptions. For mixed schedules, calculate each day type separately and add the results. Count overlapping periods only once.
Illustrative office schedule: lights run 12 hours per weekday for 52 weeks, with ten full weekday closures and no weekend lighting. The initial schedule gives 12 × 5 × 52 = 3,120 hours. Removing 10 × 12 = 120 closure hours gives 3,000 annual hours.
This is a planning convention using 260 weekdays, not an exact calendar count for every year. For a dated study, count the actual operating weekdays and closures in the reporting year. If cleaning keeps lights on during a closure, subtract only the hours actually removed.
Retain the calculation as well as the final number. A record that says “3,000 hours, confirmed with facilities manager on November 5; ten full closures excluded” is more useful than an unexplained schedule label.
Check short-term logging before annualizing it
Temporary logging can establish when sampled lighting operates, but the sample needs to represent the usage groups and the monitoring period. Check installation, timestamps, on/off detection and whether the device actually recorded usable data. Logger installation on electrical equipment should be done by qualified staff.
The Uniform Methods Project commercial lighting protocol describes lighting operating-hours logging and sampling by usage group. Use the applicable project or program protocol when one is required. Do not turn a single convenient room into evidence for the whole building.
Record unusual events during monitoring: an inventory shutdown, a holiday, construction or a temporary extra shift. A representative workweek still needs a separate treatment for annual closures and seasonal operation. There is no universal monitoring duration that makes every building representative.
DOE's baseline and M&V planning guidance explains why baseline documentation matters before equipment changes and why monitoring scope depends on variability.
Show how uncertain hours change the savings
Consider 60 fixtures reduced from an assumed 90 W to 35 W each, with no change in quantity or operating schedule. The connected-load reduction is 60 × (90 − 35) ÷ 1,000 = 3.3 kW. Both wattages are example inputs that must be verified for an actual project.
Annual-hours scenario | Energy saved/year | Value at US$0.14/kWh |
2,400 hours | 7,920 kWh | US$1,108.80 |
3,000 hours | 9,900 kWh | US$1,386.00 |
3,600 hours | 11,880 kWh | US$1,663.20 |
Each row multiplies 3.3 kW by the stated hours. These scenarios exclude demand charges, maintenance, HVAC effects, rebates and controls changes. The range is a sensitivity check, not a confidence interval. It shows why resolving the schedule can matter before issuing a firm savings forecast.
Keep existing and proposed control effects separate
If lighting operation changes after the retrofit, calculate baseline and proposed energy separately. For constant-power groups, annual kWh = fixture quantity × system watts × annual hours ÷ 1,000. Subtract proposed energy from baseline energy.
Do not reduce annual hours for occupancy control and then apply another savings percentage for the same off-time. For dimming, simple on-hours may not capture the changing power. Use a supported energy model or measured power profile rather than assuming every dimmed hour is a full-power hour.
Keep emergency, security and continuously operated lighting separate where appropriate. Do not alter required operation to improve a savings estimate. Our commercial lighting controls guide covers the related scope questions.
Record the assumption with the field audit
In LumaQuote Field, set the schedule for each fixture group on site, alongside quantities, photos and notes. When the audit syncs to desktop, those hours carry into the energy and savings calculation, so whoever reviews the proposal sees the number and the reason behind it in one place.

A fixture group in LumaQuote set to a two-shift schedule: 16 hours a day, 260 days a year, or 4,160 annual hours.
Keep interview notes and source references with the relevant audit record. Keep raw logger or control-trend files in the project folder so the evidence is easy to find later.
Before issuing the retrofit proposal, have the estimator confirm the hours, source, unresolved exceptions and whether the figure is estimated, measured or contractually agreed.
Try it on one real area with the Free plan. Three projects and the field app are included.
Frequently asked questions
Can I use 8,760 hours for a commercial building?
Only for lighting that actually operates continuously through a 365-day year, or a clearly identified scenario. Building access around the clock does not establish that every fixture runs continuously. A leap year has 8,784 hours.
Can a utility's default hours replace site evidence?
Use a required program assumption where its current rules specify one, and identify it as a program value. Keep any separate customer forecast transparent about its own basis. One utility's defaults are not national operating schedules.
How do I keep the evidence with the hours?
Record the source and date next to each schedule: interview, posted schedule, control trend or logger. In LumaQuote, notes and photos stay with the fixture group, so the reviewer can see where the hours came from.

