Choose the test area that best matches the conditions covered by the planned rollout, then document the existing lighting, controls, operating state, and visual conditions before anything changes. This commercial lighting pilot setup creates a defensible handoff to a later evaluation scorecard; it does not prove future energy, visual, compliance, or financial performance.
Choose the pilot zone with a representative-condition selector
The best first zone reflects the planned phase's space use, tasks, fixture layout, mounting, occupancy, daylight, and control pattern. A convenient area is useful only if it represents the conditions the rollout is intended to cover.
Use this four-step selector:
- Match the rollout conditions. Compare each candidate with the spaces planned for the next phase. Note the work performed, task locations, ceiling or mounting conditions, fixture arrangement, typical occupancy, daylight exposure, sensors, dimming, schedules, and overrides.
- Compare candidate zones side by side. A uniform space may support one documented zone when these conditions are materially similar. In a mixed-use or irregular facility, compare more than one area rather than letting a single lighting retrofit sample zone stand in for every space.
- Label exceptions. High-bay areas, task-focused workstations, daylight-heavy spaces, occupied areas with limited access, and visually sensitive tasks may need separate zones or explicit exclusions. A known problem area can be valuable when the pilot is intended to address that problem, but label it as targeted evidence rather than typical evidence.
- Record the representation boundary. Document the selected zone, represented conditions, excluded conditions, access or scheduling limits, selection reason, and confirming owner. If conditions differ materially, add a zone or narrow the rollout decision.
| Candidate condition | What to compare | How to label the result |
|---|---|---|
| Uniform space | Similar use, tasks, layout, mounting, occupancy, and controls | Potentially representative if exclusions are explicit |
| Mixed-use or irregular facility | Different tasks, heights, daylight, or control systems | Additional zone needed or rollout boundary narrowed |
| Known problem area | Specific issue targeted by the pilot | Targeted evidence, not typical evidence |
The matrix is a planning aid, not a universal sampling standard. For facilities with mixed ceiling conditions, document the differences before selecting separate design zones or narrowing the rollout boundary. The final choice should state exactly what the zone can represent and what it cannot.
Build the baseline evidence log before anything changes
Create the before-change record while the existing system is still operating. Record its state before moving, cleaning, replacing, or reprogramming anything that could affect the comparison. Mark unknown fields as open items with an owner instead of filling them with assumptions.
A usable baseline log should include:
- Equipment and layout: zone identifier, boundaries or dimensions, marked layout, fixture count, fixture type, visible labels, mounting arrangement, circuit or control grouping, and baseline fixture-power inputs where available. State how equipment was counted or measured, and preserve the source of each value.
- Operating conditions: date and time, normal schedule, occupancy state, daylight conditions, active control settings, sensor behavior, dimming level, and overrides. Capture relevant occupied and unoccupied states when they normally occur rather than treating one snapshot as the facility baseline. The DOE commercial lighting controls evaluation guide supports recording normal occupied and unoccupied operating conditions along with the related schedule and control state.
- Visual observations: tie each observation to a location and task. Note distribution, uneven light, task visibility, glare, shadows, reflections, dark corners, and known problem spots without turning those observations into universal performance claims.
- Controls and changes: separate lighting-only changes from control, schedule, occupancy, and maintenance changes. Record sensor behavior, overrides, operator actions, and any setting that could affect a later comparison.
- Maintenance and access context: note recent maintenance, lamp or fixture condition, temporary obstructions, cleaning status, access limits, observer, photos, and marked layouts.
- Assumptions and evidence references: identify the measurement method, observation conditions, project requirements, missing records, and fields that remain unknown. A documented baseline and post-retrofit light-level measurement plan is stronger than an informal before-and-after impression.
Use a project-approved method for any formal light-level comparison. Do not adopt a universal illuminance threshold or a protocol-specific connected-load example simply because it appears in a reference. The goal is a repeatable record whose conditions and method another reviewer can understand.
Define commercial lighting pilot acceptance checks without creating a second scorecard
The baseline log captures as-found conditions before the change. This register defines the repeatable checks to perform later under stated conditions, so it should not duplicate the baseline inventory or the existing pilot scorecard's ranking, tradeoff analysis, financial review, or final expansion evaluation.
Define acceptance criteria for the lighting sample zone as project-specific observations, not universal numbers. Each check should name the location, task, operating condition, observation method, applicable project requirement, owner, status, and evidence reference.
Check light and task conditions in the selected zone
For each relevant task location, state what will be compared: light distribution, task visibility, glare, shadows, reflections, and known problem areas. Tie the observation to the space use and the approved project requirement. If the project has adopted a cited standard or requirement with a numeric value, record that source in the register; otherwise, use a repeatable qualitative observation and leave the threshold open.
| Check | Condition and method | Status and owner |
|---|---|---|
| Task visibility and distribution | Named task locations under the stated operating condition, using the project-approved observation or measurement method | Ready to observe, observed, or open; assign an owner |
| Glare, shadows, and reflections | Same locations, viewpoints, and relevant daylight or control state | Record the observation, exception, and evidence reference |
| Controls and occupancy response | Schedule, dimming, sensors, overrides, and occupied or unoccupied states observed separately when controls change | Record the status and who will resolve an open item |
| Observation evidence readiness | Evidence needed to repeat the check is available or identified as missing | Mark the status and reason without repeating the baseline inventory |
Check controls, occupants, and evidence readiness
When controls are part of the pilot, observe scheduling, dimming, sensors, overrides, and occupancy-related behavior separately from the fixture change. Capture operator or occupant feedback as location- and condition-specific observations, not as a universal verdict. Record installation constraints or unresolved questions only when they affect whether a proposed check can be performed consistently.
The register is ready for handoff when each proposed check can be observed consistently under its stated conditions. For project-specific lighting design support, provide the selected zone, baseline record, and applicable requirements so the design input remains tied to the actual space. Setup completeness is not proof that the retrofit will meet a performance target.
Verify electrical, controls, and installation inputs before installation
Before installation, create a register showing which inputs are confirmed, unknown, or need review for the actual equipment and project. Category labels, voltage ranges, dimming descriptions, or certifications alone do not establish site compatibility.
Record the current value or evidence source, status, owner, and required review for:
- existing voltage and fixture wattage;
- circuit or total-load information and expected inrush-current information;
- control type, sensor rating, dimming method, and 0–10 V requirements where applicable;
- the proposed fixture, driver, sensor, and control combination, including exact documentation;
- manufacturer instructions, access limits, work schedule, and any separation between fixture and control changes; and
- applicable project, code, permitting, utility, or rebate requirements identified by the project team.
Compare the proposed approach with the actual circuit, controls, mounting and access conditions, manufacturer instructions, and project requirements. If you are reviewing product categories, commercial lighting categories may help organize options, but selection still requires an exact SKU, driver, control, installation, and site review.
Before installation, have a qualified electrical or lighting professional verify unresolved circuit, load, controls, manufacturer-instruction, code, permitting, and safety questions. Stop and resolve material compatibility or compliance questions rather than proceeding from this setup guide alone. This article does not provide wiring instructions or a jurisdiction-specific code conclusion.
Document the handoff: expand, revise, or investigate
Use the completed setup brief to decide whether the pilot is ready for later evaluation. The handoff indicates setup readiness, not retrofit success.
- Expand to the planned evaluation when the zone rationale and representation boundary are documented, the baseline log is sufficiently complete, acceptance checks are ready, installation inputs are reviewed, and required professional reviews are complete for the planned work.
- Revise the setup when the gap is fixable. Examples include an unrepresentative zone, missing baseline fields, inseparable fixture and control effects, or an observation method that cannot be repeated consistently. Correct the record, add a zone, separate the changes, or narrow the decision boundary.
- Stop and investigate when material compatibility, installation, code, permitting, safety, or baseline questions remain unresolved. Obtain the required project evidence and qualified review before proceeding.
File one pilot setup brief containing the zone record, representation boundary, baseline evidence log, acceptance-check register, open items, photos or marked layouts, change record, and review status. Then hand that brief to the existing scorecard process, which owns later result ranking and expansion analysis.
FAQ
The answers below keep the setup task separate from the later evaluation of pilot results.
What should be tested in a commercial lighting pilot?
Observe the proposed fixture change and any separate control change at the task locations and under the operating conditions named in the project requirements. Include installation constraints or feedback only when they affect the repeatability or interpretation of the observation.
How do you choose a representative retrofit sample area?
Choose a zone matching the rollout's space use, task demands, fixture layout, mounting conditions, occupancy, daylight, and control pattern. If those conditions vary materially, use additional zones or limit what the lighting retrofit sample zone represents.
What should be measured before rolling out new lighting?
Create the as-found record before changing the system, including the equipment, operating state, visual context, maintenance context, measurement method, and unknown fields. Use the project-approved method for any formal comparison.
What are lighting sample zone acceptance criteria?
They are repeatable, project-specific observations tied to a location, task, operating condition, method, and requirement. If a requirement has a numeric threshold, record its approved source instead of adopting a generic value.
File the one setup brief, obtain qualified review for unresolved electrical, controls, installation, code, permitting, or safety inputs, and hand the completed record to the existing scorecard for later evaluation.
