An as-installed lighting asset register should record what is actually in the ceiling, not what the plans assumed. Each entry needs an asset or group ID, an exact location, the retrofit scope, the installed type and configuration, any confirmed control link, document references, and maintenance dates. Build it by drafting entries from the closeout files. Then walk the site and confirm each one against what you can see.
Every value should list its source. Anything you can't confirm should stay marked as unknown or conflicting until someone resolves it. Give one facility role ownership of the register so it changes every time a fixture is serviced or replaced.
What to Record in an As-Installed Lighting Register
Record enough for a maintainer to find the right fixture, know what's in it, and reorder parts without opening the ceiling first. The table pairs each field with where to check it and how it helps later.
| Record item | What to capture and where to check it | Later use |
|---|---|---|
| Asset or group ID | Unique tag; match to label or drawing mark | Ties work orders to one entry |
| Location | Building, floor, room or zone; confirm on site | Finds the fixture fast |
| Retrofit scope | What changed; closeout scope plus site view | Shows which parts are original |
| Installed type and model | Type, model, configuration from submittals or label | Guides like-for-like replacement |
| Control relationship | Zone or device link, only if records confirm it | Shows what a service call affects |
| Document references | Spec sheet, warranty, closeout file name | Points to the source record |
| Maintenance dates (NPS) | Date installed or cleaned; next scheduled replacement or cleaning | Plans relamping and cleaning |
| Stock and ordering (NPS) | Remaining stock; manufacturer, contact, ordering info | Speeds reorders |
The rows marked NPS, plus lamp type and location, come from the NPS facility notebook worksheet, a maintenance worksheet in a federal lighting retrofit workbook. That worksheet is a good maintenance starting point, but it isn't a full retrofit handover template. The other rows are fields we suggest adding so the record also reflects the installation itself. They aren't a published standard or a legal requirement.
Scope deserves its own field because the same ceiling grid can hide very different work. For fluorescent troffers, the DOE Better Buildings fact sheet separates three troffer retrofit options. You can replace only the lamps with TLEDs, install an LED retrofit kit that replaces the lamps and other luminaire components, or replace the whole luminaire, housing included. Write down which one happened. A lamp-only job leaves the original housing in place, and a full replacement doesn't. For older fixtures that stayed on site, our guide to screening an existing fluorescent fixture covers the ballast, wiring, and mounting details worth noting. Projects like a T8 to linear high bay retrofit swap out the fixture type entirely—such as installing an HPLH01 linear high bay fixture—so describe the new unit instead of the old one.
Your working file also needs two columns the table doesn't show. The first is the source of each value, such as a document name or "site walk" with a date. The second is a status, such as documented, observed, or unresolved. For document references, link to a stable file whenever you can. For our fixtures, current spec sheets are on our specification download page.
Build and Verify Records from Closeout Files and a Site Walk
Here's a working method you can adapt: draft from the paperwork first, then confirm on site. Each step should leave something visible in the register.
- Gather the closeout package. Put submittals, as-built drawings, spec sheets, warranty papers, and any control or commissioning notes in one folder. Result: a file list you can cite by name.
- Draft candidate entries. Build one entry per fixture or group from the drawings and schedules, and record which file each value came from. Result: draft entries marked documented but not yet observed.
- Walk the site with the draft. Match each entry to a real location and to any visible tag, label, or fixture type. Result: entries marked observed, with the date and the name of the person who checked.
- Record only what you saw. A readable label counts as evidence. A setting or control link you can't see doesn't. If the project included daylight or occupancy controls, confirm those links in the commissioning records. Our overview of daylight harvesting controls explains how those systems get commissioned. Result: observations stored separately from document values.
- Leave mismatches open. If the site doesn't match the file, note both versions and add a follow-up instead of choosing one. Result: a follow-up list.
- Close the pass. Every entry should end up either checked or needing follow-up. Keep this walk visual only and leave electrical testing to qualified staff.
Federal property management follows a similar habit. GSA inventory guidance for federal personal property says trained property managers should physically check or view assigned property. It also says procedures should explain how to handle differences found during the count. That guidance isn't written for lighting, but the same two habits work in a lighting handover: check in person, and put your discrepancy handling in writing.
Choose Fixture-Level Records or Traceable Groups
Use one entry per fixture when fixtures need to be tracked separately. Use a group entry only when a maintainer can still tell exactly which fixtures belong to it. No rule sets a group size, so base the choice on traceability.
- Fixture-level entries fit fixtures that differ in configuration, sit on different control zones, or have their own service history. They also fit when a work order has to name one specific unit.
- Group entries fit a set of identical fixtures in a single clearly defined area. The entry has to list the location, the member count or IDs, and the features they share.
- Split a group when it drifts. If one fixture gets a different replacement or a new control link, pull it into its own entry. Don't let the group describe equipment that no longer matches.
Illustrative example: a break room with 12 matching troffers on one switch could share one group entry. A warehouse aisle where 3 of 10 fixtures have sensors needs those 3 recorded individually.
Flag Missing or Conflicting Information
A missing value and a disputed value need different next steps, so label them differently. Neither one should look verified in the lighting asset register.
- Unknown: no source gives a value. Leave the field empty of guesses and note what's missing, for example "Unknown: no model on label, not in submittals." Next step: find the missing document or check the nameplate at the next service visit.
- Conflicting: two sources disagree. Keep both references, for example "Conflict: closeout schedule differs from observed label." Next step: send it to the project contact or record owner to resolve.
- Never fill the gap silently. Don't pick the likelier value, copy a spec from a similar fixture, or delete the flag without a resolution note.
These labels are suggested wording, not an official vocabulary. The idea behind them matches GSA guidance on handling differences found during a federal property inventory, which asks for written procedures but doesn't prescribe lighting-specific labels.
Assign an Owner and Keep the Register Current
Name one facility role, such as the facility manager or maintenance coordinator, to own the lighting asset register. Update it when something changes, not on a set calendar.
- The owner keeps the register and its source files available, closes open follow-ups, and approves edits.
- Whoever does the work records it. After a service call, the technician logs the entry ID, the date, what changed, and the evidence, such as a new label photo or a packing slip.
- Update when: a fixture is replaced, a component is swapped, a fixture moves, or a control relationship changes with documentation. If a sensor or dimmer from our indoor lighting accessories replaces an original device, update the control field and the document reference together.
- Keep the history. Where your system allows it, save the earlier value or a change log instead of overwriting it.
- Route open flags to the owner so they don't sit in someone's notes.
FAQs
Can a grouped entry still help me find one failed fixture?
Yes, as long as the group lists its member IDs or a clear layout reference, like a drawing mark for each position. If technicians keep writing "third fixture from the door," the group is too coarse. Break it into fixture-level entries.
What if the closeout package doesn't mention controls at all?
Leave the control field marked unknown and note that no control record was found. Visible sensors or wall devices can be logged as observed hardware. Don't record which fixtures they control until commissioning records or the installer confirm it.
What should I do with a fixture that matches no closeout record?
Create an entry for it anyway, using its location and whatever the label shows, and mark it as observed with no matching document. Then ask the project team whether it was part of the retrofit or left over from before. That way the fixture stays on record while the question is open.
Do I need special software to keep the register?
No specific tool is required. A spreadsheet or a maintenance system both work if they can hold a source and status for each value, link to documents, and keep a change history. Choose whatever your maintenance staff will actually update.
