top of page

LumaQuote

Log In Start Free

Lighting Fixture Schedule for Retrofits: Fields, Example and Scope Checks

Writer: LumaQuote
LumaQuote
Nov 3
4 min read

A lighting fixture schedule for a retrofit is a row-by-row record of the fixtures in scope and what the estimate assumes will happen to each group. Start with the existing inventory, then add a separate proposed scope. Use a new row whenever location, operating hours, controls, installation conditions, or replacement scope change a decision.


In new construction, a fixture schedule typically identifies the specified luminaires for the drawings. In a retrofit, the estimator also needs a field-verified baseline. A fixture tag on an old drawing can help you find the lights, but it may represent equipment that has since been replaced. Keep the drawing reference and the field observation in separate columns if they differ.


What goes on each fixture schedule row?


Give each row an ID that survives changes to the product selection. A label like WH-A-01 identifies a location and fixture group. Keep the ID when a proposed product changes, and create new IDs if the row must be split. Use the same ID in photos, estimate notes, and requests for clarification.


For the existing installation, capture building or floor, space or zone, fixture description, count, input watts per fixture, annual operating hours, and existing controls. Include a source for the watts and hours. A value based on a submittal, a verified measurement, a staff estimate, or a temporary assumption has a different level of confidence. Record the source next to the number so that distinction survives an export.


For the proposed scope, keep separate fields for the proposed action, product reference, proposed quantity, and proposed input watts. Add an installation note when access, mounting, or wiring changes the work. Flag any decision awaiting confirmation, such as whether an emergency fixture belongs in scope. If the proposed product is still being selected, leave it open and name the missing information.


When to split a row


Group fixtures when the same baseline and scope assumptions apply to all of them. Split the group when part of it runs on a different schedule, uses different controls, needs a different product, or will cost materially more to reach. Two aisles can have identical fixtures and still need separate lines because one serves a single shift and the other runs a second shift.


Consider an illustrative warehouse with 40 identical fixtures drawing 78 W each. Zone A contains 20 fixtures that operate 2,000 hours a year. Zone B contains 20 fixtures that operate 4,000 hours a year. Zone A uses 3,120 kWh annually and Zone B uses 6,240 kWh, for a total of 9,360 kWh. Calculate each row as quantity × fixture input watts × annual operating hours ÷ 1,000.


Twenty 78-watt fixtures use 3,120 kWh at 2,000 hours in Zone A and 6,240 kWh at 4,000 hours in Zone B.
Illustrative annual baseline by operating zone.

Using 3,000 hours for all 40 fixtures happens to produce the same total here because the two groups are equal. It still obscures which zone drives most of the baseline. If the project moves ahead in Zone A only, the correct baseline for that phase is 3,120 kWh. A blended schedule would assign it 4,680 kWh. Keep the zone rows even when the proposal rolls them up under one product.


The U.S. Department of Energy's lighting measurement and evaluation protocol provides a reference for documenting the baseline and verifying the retrofit. When lighting hours or controls are uncertain, record what you observed and how you plan to verify the operating pattern. Treat any rebate-specific calculation rules as a separate check for the project.


Reconcile the counts before pricing


Give existing count, fixtures affected, and proposed count their own columns. In a simple replacement those values may match. In a redesign they may differ. For instance, an aisle might have 12 existing fixtures, two explicitly retained, and a proposed layout that replaces the remaining 10 with eight new fixtures. The estimate needs eight new fixtures, a scope for removing 10, and a clear record that two stay. The new quantity in this example assumes a design review supports it.


Keep exclusions visible on the schedule. If an adjacent stockroom was locked during the walkthrough, flag it as unverified and state whether the quote excludes it or carries an allowance. A blank count can be mistaken for a surveyed space with no fixtures. A scope note tells the estimator what to do next.


Before ordering, reconcile the proposed quantities by product against the quote. Before issuing a savings estimate, reconcile the existing fixtures included in the calculation against the audit scope. Those two totals answer different questions. If you revise the schedule after a second visit, keep the revision date and a short note on what changed so the distributor can update the correct line.


How to build the schedule from a field audit


Set up the job by area and space. Record fixture groups at the level you’ll need for pricing, and attach a label or mounting photo to the group where it helps resolve a specific decision. Use room-level notes for site conditions that apply across multiple groups. If one group needs lift access because of its position above equipment, put that exception on its own line.


In LumaQuote Field, you can capture the areas, fixtures, counts, photos, and notes on a phone or tablet. Sign in before heading into a site with weak reception, then record the walkthrough offline and sync when back online. On desktop, review the imported audit before settling the replacement scope and energy assumptions.


If your team already has a schedule format, use the field audit to verify a single area first. Pick one zone where hours or access differ from the rest of the building. Carry that zone through the estimate and check whether another person can trace the count, wattage source, and proposed scope without calling the auditor. That is a practical test before rolling the workflow out to the whole building.


bottom of page