Authorize a commercial lighting pilot when a bounded, representative installed zone can answer a material question about the wider rollout—such as distribution, controls behavior, installation effort, operating disruption, or stakeholder acceptance. Proceed with design or rollout when those conditions and success criteria are documented; defer when the team lacks a usable test zone, baseline, decision owner, technical information, or review path. A live pilot provides field evidence, not electrical, code, listing, permit, or commissioning approval.
Choose a Commercial Lighting Pilot, Proceed, or Defer Before Buying
Name the unresolved question before authorizing anything. Choose a pilot when a representative installed test can answer it, proceed when the relevant conditions and criteria are sufficiently known, or defer when the basis for either route is missing.
- Pilot: Choose this route when the question is observable in a bounded zone that reflects the rollout risk. The project lead should complete the pilot brief, name the decision owner, and assign technical reviewers before authorizing installation.
- Proceed with design or rollout: Choose this route when the relevant spaces, lighting approach, controls, constraints, representative zones, and success criteria are sufficiently documented without a live test. The design or commissioning lead should release the verified scope and testing responsibilities.
- Defer: Choose this route when the team cannot define the question, baseline, representative zone, decision owner, technical information, or review path. The project sponsor should document the missing information and assign the review needed to make the decision defensible.
A federal field evaluation used in-place testing under representative conditions and gathered installer and occupant feedback. That evidence supports the planning logic for a bounded test, not a universal requirement; see the representative in-place test guidance.
Match Each Uncertainty to a Pilot Test or Technical Review
Use a physical test when the uncertainty can be observed in a representative operating space. Use design, product, electrical, controls, code, permit, or stakeholder review when the missing answer is documentary, compliance-related, or impossible to measure in the proposed zone.
| Project condition | Why a pilot may help | What to test | Use review, redesign, clarify, or defer instead when |
|---|---|---|---|
| Mixed tasks or distribution | Different work areas may expose different glare, shadow, contrast, surface-response, or distribution issues. | Observe representative tasks and the locations most likely to change the fixture or distribution choice. | The zone cannot represent materially different tasks. Split the design or review those zones separately. |
| Occupied operations or repeated complaints | A bounded test can reveal installation effort, disruption, complaint recurrence, and response during normal work. | Observe affected users, operators, access needs, work continuity, and complaint patterns under relevant operating conditions. | The site cannot support controlled access or the affected users cannot participate. Clarify operations and schedule before installing. |
| Unusual ceilings, surfaces, mounting, or retrofit conditions | Plans may not show how existing conditions affect placement, access, distribution, or maintenance. | Test the field condition that could change layout, sequencing, access, or scope. | The uncertainty concerns structural, electrical, listing, code, or permit requirements. Obtain the responsible technical review instead. |
| Controls or system integration | A live test can expose switching, dimming, sensor, schedule, or interaction behavior that depends on the occupied site. | Observe the documented operating sequence and record unintended interactions and setup issues. | Compatibility, calibration, protocol, or integration ownership is unresolved. Assign the controls stakeholders and review current documents. |
| Unclear baseline or nonrepresentative zone | A test without a usable comparison or decision question can create false confidence. | First define the current problem, baseline, rollout locations, and evidence that would change the decision. | Clarify the problem, zone, owner, or criteria before installation. Defer if the team still cannot make the test informative. |
Do not treat one convenient test area as proof for unlike zones. The project lead owns the routing decision, while the electrical, controls, design, and operations owners own the reviews within their fields.
Select a Representative Zone and Write the Pilot Brief
The best zone is not necessarily the easiest one to access. Select a location that exposes the task mix, ceiling and surface conditions, operating schedule, existing lighting, controls, and stakeholder concerns most likely to affect the rollout. Document why it represents the locations it informs, what it cannot establish, and which materially different areas need another zone or separate design review.
Choose a Zone That Exposes the Rollout Risk
The zone owner should capture baseline photos, plans or sketches, existing fixture and controls information, operating conditions, complaint history where relevant, and access or disruption constraints. Record the proposed configuration and compare baseline and proposed conditions under comparable operating circumstances. The DOE/FEMP measurement and verification framework provides customizable logic for baseline and post-installation comparisons when those conditions affect the decision. Customize the observation plan to the project question and operating cycle.
Record the Brief Fields and Decision Rules
The project lead should circulate a brief containing these fields before authorizing pilot preparation:
- Zone and baseline: pilot boundary, locations informed, current conditions, operating schedule, task mix, known complaints, photos or sketches, and assumptions.
- Proposed configuration: intended fixture and control approach, placement assumptions, procurement boundary, affected operations, and changes the pilot is allowed to test.
- Measures and observation windows: task usability, comfort, distribution, controls behavior, disruption, access, maintenance implications, stakeholder checks, and the operating conditions under which each is observed.
- Owners and handoffs: decision owner, facilities and operations contacts, stakeholder reviewers, electrical or project reviewer, controls reviewer, manufacturer or submittal reviewer, and authority or code contact where relevant.
- Documentation and change control: test dates, installation notes, photos, issues, requested changes, assumptions changed, and the person authorized to approve a revision.
- Decision rules: evidence that means go, revise and retest, or no-go; the review date; the unresolved issue that blocks expansion; and the owner who makes the final authorization.
Set the observation period to cover the operating cycle needed for the decision. Do not use a standard number of days as a substitute for representative tasks, schedules, controls use, and stakeholder review.
Measure the Pilot in Terms of the Rollout Decision
Measure only what can change the wider scope, configuration, controls, operating plan, installation approach, or stakeholder decision. Compare proposed and baseline conditions under comparable tasks and operating states, and assign an owner and consequence to each observation.
Check Task Usability, Comfort, and Distribution
The facilities or user representative should observe representative tasks for glare, shadows, contrast, visual comfort, consistency, distribution, and surface response where those factors affect the work. Log the location, task, operating condition, and pattern of each complaint or usability issue. Keep the scorecard multidimensional rather than reducing the decision to brightness alone.
Check Controls, Operations, Installation, and Maintenance
The controls owner should observe switching or dimming behavior, sensor response, unintended interactions, and performance against the documented operating schedule. The operations lead should record installation constraints, access, work-area disruption, staffing effects, maintenance implications, and issues that could change placement, controls, sequencing, scope, or schedule. Record electrical, code, listing, and product-documentation questions as separate actions for the responsible qualified reviewer.
Check Stakeholder Acceptance Against the Rules
Ask designated operators, affected users, facilities or maintenance staff, project leads, and other relevant stakeholders the same decision-focused questions. The project lead should document acceptance, objections, requested changes, observation conditions, and unresolved issues, then classify each item as go, revise and retest, or no-go under the approved brief. Stakeholder feedback informs the rollout decision but does not close a technical review item.
Verify Technical and Project Constraints Before Installation or Expansion
The pilot owner should use current submittals, manufacturer instructions, site information, project documents, and qualified review for model-specific and compliance decisions. Group the pre-installation and pre-expansion checks by owner:
- Electrical or project reviewer: Verify the proposed voltage, fixture wattage, total load, inrush current, circuit or system assumptions, mounting conditions, access, and any site information needed for the design. This is a review task, not a wiring procedure.
- Controls reviewer: Verify the control type, sensor rating, documented sequence, operating schedule, and 0–10 V compatibility where applicable. Name integration stakeholders early when lighting interacts with HVAC, BAS, security, or other systems. The controls integration roadmap supports early ownership, requirements, control narratives, sequences of operation, and commissioning responsibilities.
- Manufacturer or submittal reviewer: Obtain current instructions, technical submittals, listings or ratings, controls documentation, and mounting information for the actual proposed equipment. A pilot result or inventory listing does not prove product suitability or compatibility.
- Authority, code, or permit reviewer: Determine which local code, permit, inspection, listing, or authority requirements apply to the project and who is responsible for satisfying them.
- Occupied-site coordinator: Approve access, work windows, notifications, temporary conditions, shutdown coordination, and protection of normal operations.
- Expansion and commissioning owner: Before wider installation, document owner requirements, design intent, approved quantities and scope, design changes, unresolved technical issues, functional-testing responsibilities, issue tracking, and operations documentation. The IES commissioning guidance describes commissioning as a quality-assurance process tied to owner and designer criteria, testing, issue tracking, and operations documentation.
Record the Outcome and Take the Next Action
Close the project with one decision record containing the tested zone and conditions, baseline, proposed configuration, observation period, measures, stakeholder feedback, technical review status, changes, unresolved risks, and authorized decision-maker. Tie each finding to a route and an accountable owner.
Authorize pilot preparation, not pilot installation, when the brief is complete and the remaining uncertainty is answerable by the bounded test. The project lead should circulate the brief, assign owners, obtain current documents, and schedule the review gate; installation follows only after the responsible pre-installation checks are complete. Proceed with design or rollout when representative findings and project documentation support the wider scope, and have the design or commissioning owner release the verified scope and functional-testing path. Defer when the zone, criteria, or technical path is insufficient; the project sponsor should define the missing information and responsible review before buying or expanding.
When procurement begins, use a comparable quote package to compare plans, quantities, controls, submittals, ship-to details, and timing. First complete the pilot review gate or verified design, then assign the owner who can authorize the next route.
Commercial Lighting Pilot FAQs
The questions below address common planning boundaries that remain after the decision record is complete. They do not replace the project brief or technical review.
When does a commercial lighting pilot make sense?
A pilot makes sense when a representative installed zone can answer a material question before wider commitment. If two areas differ materially in task mix, mounting, or operating conditions, do not combine their conclusions; define a separate zone or review for the difference.
What should a commercial lighting pilot measure?
Measure only an observation that could change a named rollout choice. If a finding cannot alter scope, configuration, controls, operations, installation, maintenance, or stakeholder approval, leave it out of the decision scorecard and retain it only as background.
How long should a commercial lighting pilot run before a go-or-no-go decision?
Run it through the operating cycle that matters to the decision, and reopen the observation period if a relevant task, schedule, controls state, or stakeholder group has not occurred. Set the review date and rules in the brief instead of adopting a standard number of days.
When is a lighting pilot not enough?
A pilot is not enough when the zone, baseline, or decision criteria cannot support a useful conclusion, or when a technical question remains outside field observation. Label that issue unresolved in the decision record, name its responsible reviewer, and hold expansion until the review path is complete.
