A completed commercial lighting pilot scorecard should produce one of three bounded outcomes: Go, Revise and retest, or Stop or escalate. Brightness is only one row. The decision should also account for task visibility, distribution or uniformity, visual comfort, worker and operator response, controls, usability, maintenance, retrofit disruption, and conditions the pilot did not test.
Use the framework below before installation, then complete one row for each acceptance area. A Go decision applies only to the tested configuration, locations, schedules, and operating conditions. It does not prove that a broader rollout will perform the same way everywhere.
Score the Commercial Lighting Pilot as Go, Revise, or Stop
Set the decision structure before the test begins. Record the applicable project requirement or qualified review criterion, the evidence source, the operating context, and the person responsible for each unresolved action. Do not average out a material failure in one area because another area looks better.
| Acceptance area | Evidence and operating context | Status and required action |
|---|---|---|
| Task visibility | Record task-related results, the task reference, measurement method, units, location, operating mode, and applicable criterion. Note whether the retrofit or new installation changes the task environment. | Go when the documented task requirement is met under the tested conditions. Revise and retest when the result falls outside the project criterion or the evidence is incomplete. Assign the design or review owner. |
| Distribution or uniformity | Capture readings or other documented observations across representative work areas. Include layout, mounting, adjacent lighting, and control state. | Mark Go only when the applicable distribution or uniformity requirement is supported. Otherwise, identify the affected zone and retest condition. |
| Comfort and color appearance | Record glare or discomfort observations and relevant color-appearance concerns by task, zone, time, and operating mode. | Use Revise and retest for a recurring issue that may be addressed through layout, optics, output, or control changes. Use Stop or escalate when a material concern remains unresolved. |
| Worker and operator response | Use consistent questions about visibility, task confidence, discomfort, color appearance, control convenience, and change from baseline. Record recurring versus isolated responses. | Treat repeated patterns as contextual evidence for action, not as proof of code or safety compliance. Assign an owner for follow-up. |
| Controls and transitions | Observe switching, sensors, dimming, daylight response, overrides, schedules, and recovery after interruption when included. Log the control state and transition. | Go requires observed behavior to match the intended sequence and site responsibilities. Unwanted shutoffs, delays, false triggers, or confusing overrides require correction and retesting. |
| Usability and maintenance | Record operator understanding, reporting paths, access, configuration changes, troubleshooting information, maintenance materials, training, and disruption. | Keep the row at Revise and retest until the responsible team can operate and service the tested system as required. Escalate unresolved electrical, access, safety, or code-related concerns to the responsible qualified professional. |
| Baseline or retrofit disruption | Separate baseline conditions, installation disruption, and ongoing operating results. Document the same method, locations, and relevant conditions for baseline and pilot readings. | Use the comparison only when the conditions are interpretable. If site changes obscure the result, identify the missing evidence and repeat the affected comparison. |
| Untested conditions | List zones, tasks, schedules, seasons, weather exposures, control modes, mounting conditions, and site differences outside the test. | Keep these items outside the Go claim. Assign additional review or testing before expanding the authorized scope. |
Complete the scorecard as a project record:
- Write the question and applicable criterion before installation.
- Attach the measurement, observation, interview, or trend-data source to the relevant row.
- Record location, task, time, shift, occupancy, daylight or weather, layout, and control state when they affect interpretation.
- Give every unresolved material issue one action, owner, and retest or review condition.
This is a practical acceptance model, not a universal lighting standard. Status labels become defensible when each row points to the project requirement and the evidence supporting the decision.
Choose Questions, Zones, and Observation Windows
A meaningful pilot tests the conditions that could change the rollout decision. Define observable questions first, then choose zones and time windows that represent actual work, operating transitions, and the differences the broader project will contain.
Match the Test to Real Work
Select representative and high-consequence locations rather than only the easiest or brightest area. Ask which differences could change the result:
- task type and visual demand;
- room or aisle geometry, mounting height, and fixture arrangement;
- occupancy, traffic, daylight, and adjacent lighting;
- shift schedule, control coverage, and operator responsibilities; and
- weather or exposure for outdoor areas.
For a single-zone pilot, list materially different layouts or tasks that remain outside the test. For a multi-zone pilot, compare consistency between zones instead of reporting only the best result. A warehouse team can use warehouse uniformity planning when layout differences affect zone selection, and ceiling-height considerations when mounting conditions vary.
Record excluded zones directly on the scorecard. An untested office task, warehouse aisle, retail display, gym area, industrial work point, or outdoor exposure is a scope limitation, not an implied pass.
Observe Normal Use and Transitions
Use an observation plan that matches actual occupancy and operating changes:
- Verify the nominal schedule against actual operation with people familiar with the site. Note overrides, vacancies, cleaning shifts, and other exceptions. The commercial lighting evaluation protocol supports checking schedules against actual use rather than relying on a building schedule alone.
- Define windows for occupied work, relevant shifts, daylight or weather conditions, and control transitions. Do not label a short or single-condition visit representative by default.
- Log occupancy, daylight, weather, control mode, site changes, and temporary installation disruption during each window.
- Observe switching, dimming, sensor response, overrides, and recovery where those transitions affect the decision.
- For a retrofit, capture baseline and pilot readings with the same documented measurement method, locations, and relevant operating conditions. Separate baseline conditions, installation disruption, and ongoing operation.
- Record exclusions, missed transitions, and conditions that the schedule did not cover.
This process makes a comparison more interpretable. It does not create a universal sample size or observation duration. Appropriate coverage depends on the tasks, site, project requirements, and conditions that could alter the result.
Measure What Affects Work and Comfort
Capture evidence that explains whether the tested lighting supports the work, not just how much light the sources produce. Compare each result with the project brief, applicable requirements, or qualified professional criteria rather than an invented universal threshold.
Record Technical Conditions
Use the project brief, applicable requirements, or qualified professional criteria to define the acceptance comparison. The applicable maintained-illuminance and uniformity criteria should be recorded with the task or space reference, units, source, and allowable variance where applicable.
Record these fields with each technical result:
- task and measurement location;
- baseline or pilot condition;
- instrument or measurement method;
- task-related output and distribution or uniformity result;
- visual comfort or glare observation;
- relevant color-appearance observation;
- daylight, occupancy, layout, adjacent lighting, and weather; and
- control mode, schedule, and transition state.
A brighter result can still be unsuitable if it creates glare, poor distribution, distracting color appearance, or an environment that workers cannot use comfortably. If the project has no applicable criterion for a row, flag that gap for qualified review instead of inventing a pass value. A related guide to visual comfort factors can help frame the questions, but it does not establish the project's acceptance threshold.
Make Worker Feedback Comparable
Ask workers and operators the same short questions in each tested area. Keep the questions tied to the work, and record the context rather than collecting unstructured preferences:
- Ask about visibility, glare or discomfort, color appearance, task confidence, control convenience, and change from baseline.
- Record zone, task, time, shift, occupancy, control state, and whether the response is recurring or isolated.
- Compare patterns across similar tasks and conditions.
- Connect recurring issues to a scorecard row, corrective action, and owner.
Consistent occupant and operator feedback can identify comfort, task, and usability friction that a measurement may miss. Treat it as contextual decision evidence. Worker preference alone does not establish code compliance, safety compliance, or a required technical result.
Test Controls, Usability, and Maintenance
The installed system must work in the space and under the intended operating sequence. A feature listed in a product description is not evidence of compatibility, commissioning, correct sensor behavior, or user understanding.
Watch the Controls in Operation
Observe the actual sequence during occupancy and transitions, then compare it with the intended schedule and site responsibilities:
- switching, dimming, and sensor response;
- sensor location and coverage;
- daylight response, when included;
- overrides and recovery after interruption;
- delays, unwanted shutoffs, false triggers, or task conflicts; and
- control mode, time, occupancy, and transition for each material issue.
The control compatibility, commissioning, and maintenance checks provide a useful process reference for field acceptance. Use current project documentation for the actual sequence and responsibilities. A static demonstration is not a substitute for observing the installed behavior.
Check Day-to-Day Serviceability
Ask the operators and maintenance team whether they can use, explain, adjust, and report the system when conditions change. Record:
- access needs and configuration changes;
- troubleshooting paths and maintenance documentation;
- staff training and reporting responsibilities; and
- recurring complaints and disruption implications.
Assign each unresolved issue to a design revision, operating procedure, or qualified professional review. Keep the related scorecard row at Revise and retest until the required behavior and responsibility are clear. This keeps maintenance and usability from disappearing behind a successful first walkthrough.
Define What a Successful Pilot Authorizes
Use the completed rows to authorize only the tested scope. A bounded pilot decision has three possible actions:
- Go: The tested configuration meets the documented project criteria for the tested locations, schedules, operating modes, and conditions. The decision record identifies the evidence and any remaining limitations.
- Revise and retest: A specific acceptance row needs a design or operating change. Name the change, owner, affected location, and conditions the next test must revisit.
- Stop or escalate: Pause the affected scope when material visibility, comfort, control, usability, maintenance, safety, or compliance concerns remain unresolved. Route the issue to the responsible project lead or qualified professional.
Before broader deployment, list untested zones, tasks, schedules, seasons, weather exposures, control modes, mounting conditions, and other site differences. The tested configuration and conditions only define the supported boundary of the decision. A successful pilot does not prove full-site performance.
Attach the completed scorecard, evidence, limitations, corrective-action owners, and untested-conditions list to the rollout decision record. Use that record to authorize the tested scope, assign a retest, or pause expansion.
FAQ
What should a commercial lighting pilot test besides brightness?
Test task visibility, distribution or uniformity, visual comfort, relevant color appearance, worker and operator response, controls, usability, maintenance, and the operating conditions around each result. The scorecard should also show whether the evidence came from a baseline comparison, field observation, measurement, interview, or control log.
How do you judge whether a lighting pilot passed?
Review each acceptance row against its documented project criterion and evidence, then assign Go, Revise and retest, or Stop or escalate. A material unresolved issue should remain visible in its own row rather than being canceled out by stronger results elsewhere.
What makes lighting pilot acceptance criteria defensible?
Defensible criteria connect to real tasks and project requirements, name the evidence method and operating context, distinguish baseline from pilot conditions, and assign owners to open issues. They also avoid unsupported universal thresholds. If the project does not supply a criterion, record that gap for qualified review instead of converting a preference into a pass value.
Does a commercial lighting pilot guarantee full-site performance?
No. It supports a bounded decision for the tested configuration, locations, schedules, and conditions. Different zones, tasks, seasons, weather exposures, mounting conditions, or control modes can change the result and should be listed before the team expands the rollout.
