A lighting-control schedule that says “occupancy sensors and daylight dimming” is not yet an operating plan. It does not say which luminaires respond, what triggers a change, how far they dim, who can override the response, or how the installed result will be tested. Those missing decisions are where a sensible design becomes a frustrating room.
The document that connects the design to programming is the sequence of operations. For commercial lighting, it is a plain-language, testable description of how each control zone behaves in normal use, after hours, under daylight, and during a fault or emergency condition. DOE’s controls guidance frames documentation as a core part of selecting a system, not a closeout afterthought. Its lighting-controls resource is a useful reminder that system capability and documentation should follow project objectives.
This checklist is a practical way to write that sequence so the electrical drawings, controls submittal, programming, and functional test all describe the same installed system. It supports—but does not replace—the adopted energy code, life-safety requirements, manufacturer instructions, or direction from the authority having jurisdiction.
Start with a zone that has an operational purpose
Draw a zone around an activity, a daylight condition, or a safety requirement—not simply around the nearest circuit. A conference room, its presentation wall, its circulation path, and a glazed perimeter may need different responses even when their fixtures are supplied from the same panel.
For every zone, name four things before selecting the control device:
- Controlled load: the fixture group and any separate layers, such as general, display, decorative, or egress lighting.
- Input: occupancy/vacancy sensor, photocell, schedule, wall station, building-management command, or an approved combination.
- Action: switch off, dim to a stated level, recall a scene, or hold a level.
- Limits: the occupied level, unoccupied level, timeout, fade, minimum dim setting, and conditions in which an override takes priority.
Avoid treating the technology name as the sequence. “0–10V” and “DALI” describe interfaces; neither one decides whether a wall station takes precedence over a daylight sensor or what occurs after the room is vacant. Confirm the selected fixture, driver, and control combination together, including any low-end dimming constraint. Our dimming-protocol guide explains why that compatibility decision belongs in the submittal rather than in field assumptions.
Write the normal state first, then its exceptions
Start the narrative with the expected condition during the building’s real operating hours. State the time schedule, which zones are enabled, and the approved way an occupant can change the scene. Then add each exception deliberately: local override, manual-on/vacancy behavior, daylight response, cleaning or after-hours mode, and an emergency or loss-of-communications condition where applicable.
A usable sequence can be written in a compact table:
| Condition | Required response | Acceptance check |
|---|---|---|
| Scheduled occupied hours | General-lighting zone enables; the local station recalls the documented occupied scene. | Confirm the programmed schedule and scene levels against the approved record. |
| Space becomes vacant | After the approved timeout, the zone follows the specified off or dimmed state. | Walk the sensor coverage area, then verify timeout and resulting level. |
| Available daylight rises | The designated daylight zone responds without changing non-daylight zones. | Test with the final shades, furniture, and glazing conditions; record the calibrated setpoint. |
| Local override | An occupant can make only the intended change for the stated duration; the system resumes its programmed state afterward. | Operate each allowed station and confirm both the limit and return behavior. |
| Loss of normal power / emergency condition | The documented emergency arrangement performs as designed; normal controls do not obscure the required emergency operation. | Perform the project’s approved integrated test and retain the result. |
The values in that table must be project decisions, not generic defaults. For example, do not copy a sensor timeout from a typical detail when the room is occupied by still users, has obstructions, or has a code-specific requirement. Likewise, daylight response should identify the controlled fixtures and the tested field condition, not merely say “daylight harvesting.”
Make functional testing a submittal requirement
Functional testing is where a sequence becomes verifiable. DOE’s commercial-code field-study material describes lighting-controls testing as a check that hardware and software operate as designed, including verification of sensor placement, sensitivity, programming, schedules, and photosensors where applicable. The program’s testing measure also calls for documentation certifying the installed controls meet the applicable requirements.
Assign responsibility for each test before installation. The Better Buildings exterior-controls guidance gives a useful model: test calibration, adjustment, programming, and operation against construction documents and manufacturer instructions; confirm occupancy-sensor placement, sensitivity, and timeout; confirm photosensor operation; and confirm time-based programming. Its commissioning checklist is aimed at exterior lighting, but the verification structure is useful indoors as well.
For each test, the closeout record should identify the zone, date, tester, input used, observed response, pass/fail result, deficiency, and final programmed value. A screenshot alone is not proof that a ceiling sensor sees the occupied area or that a daylit row dims independently. Pair programming records with observed tests in the completed room.
Keep the handoff usable after the installer leaves
The owner needs more than device cut sheets. Deliver a labelled controls plan, final control-zone names, approved schedules and scenes, sensor locations, the sequence of operations, functional-test results, login/administration process where relevant, and maintenance or recalibration guidance. DOE describes commissioning handoff as final documentation of the process, systems information, and actions taken, plus a plan for future testing and reporting. Its federal-facilities process provides a clear framework: plan, investigate, implement, then hand off and integrate.
Training matters too. Show facilities staff how to use the local override, identify a failed device, adjust only the permitted settings, and locate the final record. If a scene, schedule, or sensor setting is changed later, revise the record; otherwise the next renovation begins from an unreliable baseline.
The takeaway
A good lighting-controls sequence is not a prose version of a product data sheet. It names each zone’s load, inputs, normal response, exceptions, limits, and acceptance test. Put those decisions in the drawings and submittal before programming begins, test them in the completed room, and leave the owner a record they can operate. That discipline makes controls easier to commission—and much harder to value-engineer into ambiguity.