A useful commercial lighting handoff ties each reviewed area or fixture to six things. These are the approved design reference and its revision, the task or design intent, the criterion and check conditions in the project documents, the related fixture, layout, submittal, and control records, the actual field observation, and a recorded result. That result is a match, a variance, or a question sent to a named reviewer.
When those links exist, a field team can show a real mismatch instead of arguing that a room "should look brighter." The matrix below is a suggested format you can adapt to your project, not an industry-mandated form.
What a Reviewable Commercial Lighting Handoff Should Contain
Build the handoff one row per reviewed area or fixture. Each row should end in a result someone else can retrace to a named, approved document.
| Handoff element | What to record | What the reviewer can conclude |
|---|---|---|
| Approved reference and scope | Document title or ID, revision, area or task | Which record governs this check |
| Intent and criterion | Design intent, project criterion, stated method and conditions | What counts as a match here |
| Fixture and context links | Fixture ID, schedule row, submittal, layout location, control reference | Whether the right configuration is being judged |
| Observation and result | What was found, date, match / variance / question, reviewer | What happens next, and who decides |
A filled-in row might read like this, with placeholders in brackets: [Area ID, task] → [Lighting plan ID, Rev X] → [criterion and conditions quoted from the approved documents] → [Fixture type, schedule row, submittal ID and revision] → [observed condition] → [Variance, routed to the designated reviewer]. Keep the result words strict. "Match" means the observation agrees with the cited criterion. It does not mean the work is accepted or approved.
Set the Approved Design Basis and Review Scope
Start by naming the exact records that control the comparison. A field observation against an undated or superseded drawing can't be reviewed, because the team may be debating different versions of the design. Record these items beside each area or task under review:
- Approved lighting plan or design basis, with its document ID and current revision.
- Fixture schedule and relevant submittals, each with its revision or approval status.
- Area or task under review, defined narrowly, such as one workstation zone or aisle. Avoid "the whole room."
- Existing or retained conditions for retrofit work, listed separately from the proposed new work. Don't assume either one is approved.
Retrofit scope needs extra care, because an undocumented existing condition can look like a design mismatch. As one federal example, VA lighting guidance for renovation projects directs design professionals on VA work to visit the site and document pre-existing conditions. If your team is still deciding whether the work is a straight swap, settle that with our retrofit layout decision guide before you build the handoff rows.
On projects that use formal commissioning, the GSA Commissioning Guide shows one way to keep records connected. On GSA projects, the commissioning record brings together the owner's project requirements, basis of design, submittal review, construction checklists, site visit minutes, and the issues log. The guide also says scope is set project by project. For other stages of a job, our commercial project support hub covers site inputs, layout review, and controls checks.
Turn Design Intent Into Observable Site Criteria
Design intent becomes reviewable when each area has a criterion the field team can actually observe and compare. For each area or task, record the intent in plain words along with the specific criterion, measurement method, and operating conditions stated in the approved project documents.
Copy the criterion and its conditions accurately, ideally word for word, with the page or section reference.
If the documents name a method, such as when to take a reading, which controls state applies, or which surfaces count, the field check must follow that method. If it doesn't, the observation answers a different question. Leave out any value or method the documents don't state.
Here is how a vague concern turns into a usable check. A supervisor says a [task area] "looks too dim." That remark is a prompt, not a test. The next step is to find the approved criterion for that task area and the conditions it names. Then record the observation under those conditions and compare.
Sometimes the approved documents give no criterion, method, or condition for an area. In that case, don't create one. Mark the row as an open question for the designated reviewer and write down what's missing, such as "no stated check condition for [area]." Not every area needs a numeric target. A criterion can also be a layout position, a fixture type, or a control behavior written in the documents. A documented gap is useful, though. It tells the reviewer exactly what has to be defined before anyone can call the area a match or a variance.
Cross-Reference Fixtures, Layout, Installation, and Controls
A field observation is only useful when it points to the right fixture and the right record. Use the project's fixture identifiers the same way across the schedule, layout, submittals, and field notes. Then build a short traceability bundle for each fixture tied to a reviewed criterion:
- Fixture ID to schedule row: the type designation exactly as scheduled.
- Schedule row to approved submittal: the submittal ID and current revision. Use manufacturer specification sheet downloads or other current product documents only to confirm what the approved submittal describes.
- Fixture ID to layout location: the planned position, plus any orientation or mounting context that affects the criterion.
- Fixture ID to control documents: the zone, sequence, or control intent, but only when the criterion depends on it.
Carry forward only the details that matter for the criterion under review. Don't infer what a fixture can do from its product name or category. If a criterion depends on light distribution, the approved submittal's photometric data is the reference. Our guide to aisle-optic photometric files explains why distribution-specific files matter in warehouse aisles.
Installation context can also cross document lines. On VA projects, VA guidance on coordinating lighting submittals calls for lighting equipment submittals to be reviewed alongside ceiling system submittals. On any job, a ceiling or mounting change can affect whether the scheduled fixture fits its planned location.
Substitutions need their own link. If a fixture was substituted, connect its ID to the documented approval and the current project record. An unapproved field change is a variance, not a match. Our article on substitution review evidence covers what that approval record should show.
Record Field Observations and Resolve Discrepancies
Keep the observation separate from the resolution. The field record says what was found, and the project's designated reviewer records or directs what happens next. When a site condition doesn't clearly match, record it in this order:
- Identify the location. Note the area or fixture ID, plus the approved document and revision you compared against.
- Describe what you observed. State the condition plainly. If the project specifies check conditions, note them. If none apply, mark the gap instead of improvising a test.
- Classify the result. Call it a match, a variance, or a question. If you're unsure, it's a question.
- Assign ownership. Record the date identified, the person following up, and the reviewer the project documents name.
- Track status and disposition. Keep the item open until the reviewer's documented decision is logged against the same row.
This sequence provides a practical recording order for project teams. In building commissioning contexts, WBDG commissioning issue-log guidance similarly notes that an issues log typically captures, at a minimum, a detailed description of the issue, date identified, party responsible for corrections, issuing agent, and completion status, with the Owner reviewing and approving issue-resolution decisions.
Field teams shouldn't approve substitutions or decide code compliance themselves. Those calls belong to the reviewer named in the project documents and to the authority having jurisdiction.
FAQs
Does every area in a lighting handoff need a numeric target?
No. Include a numeric value only when the approved project documents supply one, and keep the method and conditions they state with it. Some areas are reviewed against layout, fixture type, or control intent instead. If an area has no defined criterion, list it as an open question for the designated reviewer. Don't fill the gap with an assumed number.
How should an approved fixture substitution appear in the handoff?
Tie the affected fixture ID to the approval document, its date or revision, and the updated schedule or submittal that now governs. That way a field reviewer compares the installed fixture against the approved substitute, not the original specification. If you can't find an approval record, log the installed fixture as a variance. Don't treat it as a match.
Who resolves a conflict between site conditions and the approved documents?
The reviewer the project documents designate. Depending on the contract, that may be the design professional, the commissioning authority, or the owner's representative. On projects that follow the WBDG commissioning process, the Owner reviews and approves issue-resolution decisions. The field team's job is to document the conflict clearly enough that this reviewer can decide.
Should existing equipment in a retrofit be listed in the handoff?
Yes, when it affects what is being compared. List retained or existing fixtures, ceilings, and controls separately from the proposed work, and note which approved document covers each one. That separation keeps an existing condition from being logged as a design mismatch, or wrongly accepted as part of the approved design.
