Direct answer: schedule behaviour, not only devices
A whole-home lighting-control schedule should settle which loads and shades belong to each room, the scenes users need, keypad locations and labels, dimming and switching expectations, sensor behaviour, override routes, account access, testing responsibility and handover records before commissioning. A device schedule alone says what is installed but not how the home should behave. The useful document connects the design intent with the current electrical drawings and the selected control system, while leaving circuit design, installation and safety decisions to the appointed electrical and controls professionals.
Begin with real household activities
List the recurring situations that change how light is used: arrival, cooking, dining, entertaining, reading, television, cleaning, bedtime, night circulation and absence. Group them by room and note which scenes should affect only one area and which may span several. Avoid a long menu of near-identical moods that nobody can remember. A useful first pass often includes bright task light, comfortable general light, a lower evening setting and an unambiguous off or pathway function where appropriate. The schedule should describe the activity and affected zones rather than guessing final percentages before the room can be viewed.
Create one scene-and-zone matrix
For each controlled zone, record its drawing reference, fixture or load description, control type and the scenes that affect it. Then add the proposed state for each scene and mark values that must be tuned on site. Lutron planning documents distinguish individual zones from scenes that recall preset levels and recommend consistent programming methods across keypads. The selected manufacturer’s current documentation must govern the actual system. A matrix exposes accidental omissions, such as a decorative lamp that is not controlled, or a shade command that is included on one keypad but absent from the matching room sequence.
Make keypad labels predictable
A label should tell a visitor or household member what pressing the button will do. Use the same word for the same action across the home, keep room-wide and whole-home commands visibly distinct, and decide what button indicators mean. Test proposed names before engraving because labels such as “Relax” or “Scene 2” may be interpreted differently by each person. Show keypad type, button count, location, engraving and related scene on the schedule. Where an app or touch interface repeats the functions, align names across both interfaces so the physical and digital controls do not teach competing systems.
Coordinate shades, sensors and manual control
If motorised shades, occupancy sensors or time-based actions are included, record which scenes they join, when automation is permitted and how a person can override it. Consider daylight, privacy, sleeping patterns, pets, cleaning and unusual hours. Do not assume every shade has a simple on or off state or that a sensor suits every room. Manufacturer guidance notes that scene and status behaviour can differ by device type. Ask the controls specialist to confirm the actual capability, limits and fail-safe behaviour, and keep the final electrical design within applicable DEWA and Dubai Building Code requirements.
Planning example: evening circulation across three rooms
Planning example: a fictional home has an open living and dining area connected to a corridor and guest powder room. The first programme gives each space separate bright, medium and low buttons, creating too many choices at the main entrance. The household instead briefs a whole-area “Welcome” scene, local task controls in living and dining, and a low “Night path” that affects only the corridor and powder-room approach. Final light levels are tuned after furniture and window treatments arrive. This scenario demonstrates the decision process; it is not a completed project or a technical programming instruction.
Commission in layers and record the result
Commissioning should verify that each circuit, fixture and shade responds correctly before scene tuning begins. Review one room at a time, then test whole-home commands and transitions between rooms. Check minimum dimming behaviour, visible flicker, unexpected delays, indicator logic and what happens after power interruption using the selected system’s procedures. Photographing a pleasing room is not enough; the accepted programme needs a written record. Capture the final scene names, zone states, unresolved items, software or account handover status and the person responsible for later adjustments.
Use a pre-commissioning checklist
Hold the review while drawings, labels and programming can still be corrected. Mark each item confirmed, rejected or awaiting a named response.
- Current load and zone list matches the installed works
- Room and whole-home scenes have clear purposes
- Keypad names are consistent and approved before engraving
- Shade, sensor and time-based behaviour is documented
- App names and physical labels agree
- Furniture and window-treatment dependencies are noted
- Testing, tuning and return-visit responsibilities are assigned
- Owner access, backups and handover records are included
Limitations and the next useful step
This article cannot design circuits, select protection devices, confirm product compatibility or programme a proprietary control system. Those tasks require the appointed professionals, current manufacturer information and the actual installation. DEWA publishes electrical regulations and circulars, and Dubai Municipality publishes the Dubai Building Code; the project team must confirm what applies. Next, issue the household-activity list, current electrical drawings and proposed keypad plan to the controls specialist, then request one coordinated scene-and-zone schedule for review. Keep that schedule with the wider whole-property project and commissioning records.
Sources & further reading
Make this useful for your project.
A review of your property and priorities can turn general guidance into a defined brief.
Explore our servicesDiscuss your project
