Build a lighting fixture schedule from a site walk one location at a time. Give each room or zone its own row, write down what you saw and what the plans or specs say, and label the row with a status. Then check the draft against current project documents before anyone uses it for pricing or release.
This guide uses three working statuses: confirmed, estimated, and open. They are a suggested way to coordinate the work, not an industry standard. Their value is simple. A reviewer can tell at a glance which rows are backed by a document, which rest on an assumption, and which are waiting on an answer.
Build a location-by-location draft schedule
Your first usable draft is one row per location, with each row showing its source and status. Merge rows later. If you combine too early, you lose track of which count came from which room.
Work in this order: record the location, capture the observation and any document basis, assign a status, then reconcile. Keep what you saw on site apart from what a plan sheet or spec section says. Those are different kinds of evidence, and a reviewer needs to know which one supports each entry. The sample below uses placeholders only.
| Location / tag | Known information and source | Status and next action |
|---|---|---|
| [Room or zone ID] / [Tag] | Plan [sheet, revision] shows [requirement]; field matches | Confirmed: cite [document or approval] |
| [Room or zone ID] / [Tag] | Count of [qty] based on [estimate basis] | Estimated: confirm basis with [reviewer] |
| [Room or zone ID] / [Tag pending] | Existing [observed fixture]; replacement not selected | Open: need [missing answer] from [reviewer] by [date] |
A confirmed row still names its source, so anyone can recheck it. An estimated row carries its basis in the same row, which keeps it from passing as an approved selection. An open row is blocked until someone gives the named answer.
This row-by-row structure matches a published public-sector method. For school lighting upgrades, DOE's school lighting specification guidance gives each fixture and lamp type a unique identifier and collects existing-equipment details room by room. It then builds a spreadsheet that pairs each unique type with a replacement lamp, retrofit kit, or new luminaire. The status column above is an added working convention. It is not part of the DOE method.
Connect each entry to its requirement, tag, and fixture record
A row is traceable when a reviewer can follow it from the room to the source behind every value. These core fields make a practical working template. Your plans, specs, or reviewer may call for more.
- Location or zone ID: Ties the row to a specific place, so you can match it to plan sheets and to the field.
- Fixture tag: Groups identical types across rooms without losing the room-level rows beneath them.
- Observed condition: What you actually saw, such as the existing fixture type or how it is mounted. Mark anything you inferred rather than saw.
- Quantity and basis: State whether the number was counted on site, taken from a plan, or estimated. If it is estimated, name the method. For rooms where a raw count is not enough, check the fixture count inputs that affect the number.
- Requirement source: The sheet, spec section, revision, or written reviewer direction. If nothing exists yet, write "none." Do not leave the field blank.
- Fixture identification: When a selection exists, write the manufacturer, model, and configuration exactly as the current document shows them. Leave missing specs empty rather than filling them from a similar product.
- Status and next action: The label, plus who acts next.
When sources conflict or look out of date, record both values in the row. Do not pick one and call it confirmed. The uncertainty is part of the record.
Add mounting, controls, electrical, or layout fields only when the project documents or the responsible reviewer ask for them. For example, if a warehouse row is open because spacing is undecided, our warehouse lighting uniformity guide explains why layout tools such as IES files matter to that decision.
Reconcile the draft and route open items before release
Before pricing or release, compare every row against current project documents and turn each gap into a named open item. Nothing should look approved just because it made it into the schedule.
- Match rows to current documents. Check each location, tag, quantity, and requirement against the latest plans and specs, and note the sheet and revision. If information is missing, conflicting, or outdated, mark the row open and name the document or decision needed.
- Log each discrepancy as an open item. Write down the missing answer, the responsible reviewer, and the next action. Do not average two counts or choose between two drawings on your own.
- Check selected fixtures against exact-model documents. Compare only the information for that exact model or configuration: SKU, label, and current spec sheet. If a row lists one of our fixtures, pull the current sheet from our specification download page. A spec sheet describes the product. Whether it meets the project requirement is the reviewer's call.
- Route technical and code questions to qualified reviewers. Send unresolved mounting, controls, electrical, product-suitability, and code questions to the right person. That may be a licensed electrician, lighting designer, engineer, or the authority having jurisdiction. The schedule helps coordinate the work, but it does not replace circuit design or code-compliance judgment. Project criteria can also shape the schedule itself. For projects governed by the cited DoD criteria, lighting plans and details call for a separate luminaire schedule plus controls and control strategies for each space. On Sioux Falls city projects, the City's contractor standards page links to local lighting standards and engineering documents.
- Release by row, not by document. A reviewer must resolve or accept each open item before the schedule counts as final for the decision it affects. Keep unaffected rows marked separately so they can move ahead. An estimate becomes a committed selection only after the review or approval it needs.
Before ordering, make sure every row on the purchase list is confirmed and cites a current document. Hold the order on any row that is still estimated or open. If a selection is new to the owner, a short trial rated with a commercial lighting pilot scorecard can bring up comfort, controls, or maintenance concerns before a full rollout.
FAQs
What should I do if no current plans exist at the time of the walk?
Record your observations anyway. Enter "none" as the requirement source, and keep those rows estimated or open. Then ask the owner or design team for the current drawing set or a written requirement. Change the rows only after that document arrives.
How do I keep an estimate from being priced as a firm number?
Put the basis next to the estimate in the same row, and carry the estimated label into the quote. One option is to group estimated rows as a separate section with their assumptions listed. That way a supplier or client can see which quantities may change.
My field count doesn't match the plan count. Which one goes in the schedule?
Neither one wins by default. Record both numbers with their sources, mark the row open, and ask the responsible reviewer which condition governs. A mismatch on a retrofit may point to a change the drawings don't show yet.
Can one fixture tag cover several rooms?
Yes, once each room has its own row. The tag groups identical types for pricing and ordering, and the room rows keep each location traceable. If one room later needs a different selection, you can split it off without rebuilding the schedule.
Does an existing fixture on a retrofit walk tell me what the replacement should be?
No. The existing fixture is an observed fact, and it belongs in the observed condition field. The replacement stays open until a plan, spec, or reviewer sets the requirement. That matters because the new fixture's mounting, controls, or output may need to differ.
