2. Freeze Four Project Documents Before the Electrician Pulls Cable
2.1 Marked-Up Control Plan
The first document is a fully marked-up control plan. A generic switch symbol is not enough. Every control point needs a unique ID and a visible relationship to doors, beds, cabinetry, mirrored cabinets, curtains, ceiling fixtures, and major furniture. For new homes, each sensor location should also be assigned a unique ID, intended function, and clear mounting position. Multi-way locations such as stairs, corridors, garage entries, primary-bedroom entrances, and bedside positions should be linked clearly on the same plan. For apartments, hotels, or repeat housing, create a room-type template first and record unit-specific field changes as controlled deviations rather than relying on crews to repeat a layout from memory.
2.2 Control Point Schedule
The second document is the Control Point Schedule. Each row represents a physical wall box, not an entire room. At minimum, record the building or unit, room, box ID, drawing reference, mounting height, box standard, usable depth, gang count, function of every channel, circuit number, load type, dimming method, multi-way role, supply conditions, protocol or gateway dependency, product family, drawing revision, approval status, and owner.
| Control-point field | Required project entry |
| Box ID | Unique code linked to the current drawing |
| Location | Building, unit, room, wall, and drawing reference |
| Functions | Function assigned to every button or channel |
| Electrical role | Direct load, scene command, auxiliary control, or other approved role |
| Load data | Circuit ID, fixture or equipment, driver, control method, and design load |
| Items still open | Only choices that remain within the approved installation envelope |
| Release evidence | Approved drawing, box detail, wiring diagram, and named owner |
A control-point record must be detailed enough for site verification, linking one box ID to a specific wall, circuit, and accountable owner. A general note such as “provide a smart switch at the entry” cannot support construction release, inspection, or later traceability.
2.3 Load and Dimming Compatibility Matrix
The third document maps every controlled circuit to its actual load. Record the fixture or equipment type, driver or motor information, control method, operating voltage and frequency, design load, starting or inrush conditions, permitted minimum and maximum load, dimming requirement, dimming type, and the party responsible for compatibility approval. If the fixture is not selected, the status should read “not released” or “switching only; dimming not approved,” rather than assume that every LED will work with one dimmer.
2.4 Scope and Approval Matrix
The fourth document resolves cross-trade gaps. Who updates the drawings? Who supplies the back boxes? Who signs off fixture compatibility? Who owns the gateway, low-voltage enclosure, network switch, and backup power? Who creates rooms, binds devices, programs scenes, and transfers the administrator account? If these questions do not have a named company or person, the real project status is not “coordinated”; it is “unowned.”
NaLiteSmart Project Coordination: Before sample approval or bulk selection, the project team can provide NaLiteSmart with the destination market, supply conditions, back-box drawing, Control Point Schedule, load and dimming matrix, multi-way requirements, protocol requirements, and certification scope. NaLiteSmart can use these inputs to narrow the candidate combination across lighting, scene, dimmer, fan, curtain, power-control, and thermostat products while aligning neutral or no-neutral versions, protocols, faceplate families, and OEM/ODM scope. This product review does not replace local code approval or electrical sign-off, but it can expose missing project information before ordering.
