Owner Acceptance Testing for Lighting Controls: What to Verify Before Closeout

Why it matters

"Acceptance testing is the final proof that the programmed system performs the way the owner was promised it would."

On a live project, the difference between a good controls design and a painful one usually comes down to how clearly the behavior is defined before anyone starts programming or testing.

Where projects get stuck

• Testing is done only from the programmer’s perspective, not the owner’s.
• The test plan does not cover the behaviors the occupants will actually notice.
• No one documents the pass/fail status in a way that survives closeout.

Field checks

• Use a written test plan before the closeout meeting starts.
• Verify the occupant-facing behaviors, not just the hardware response.
• Capture results in the turnover package while the test is still fresh.
• Make sure the owner knows what was tested and what remains pending.

Bottom line

"Acceptance testing should leave the owner with confidence, not a list of unexplained mysteries."