Ceiling Fan Light Controller Functional Test Plan: What to Verify
Prepared and technically reviewed by the Sankey Engineering Team. Updated August 24, 2026.
A functional test plan turns an approved ceiling fan light-controller configuration into repeatable production evidence. Its purpose is not to claim every type of product validation. It should define the observable motor, light, input, and indicator behaviours that a unit or approved sample must demonstrate under a documented setup.
Identify the exact configuration
Put the controller hardware revision, firmware version, motor or approved simulator, light assembly or load, harness, input supply, remote or wall-control path, and optional functions at the top of the plan. A result should never require a reviewer to guess whether the correct light module or firmware was used.
Where programmed parameters affect motor or light behaviour, record their source and confirmation method. This keeps an engineering configuration separate from the approved pilot configuration.
Write observable test steps
Each row should state the initial state, action, expected response, pass criterion, and record. A row might ask the operator to send a designated light command and confirm the approved light state, motor state, and indicator. “Works normally” is not a usable criterion.
When a numerical limit is approved, include the test point, instrument, tolerance, and whether the limit applies to the controller alone or the complete assembly. Do not borrow a limit from an unrelated fan.
Cover combined customer states
Review the motor and light states that a user can actually select: power-up, light only where applicable, selected fan speeds, light changes, direction behaviour if in scope, RF or local command, and approved fault response. Include only functions included in the released build.
If a connected interface exists, decide whether production verifies the complete customer path or an approved, controlled subset. A fixture must remain safe and repeatable while still confirming the functions that matter.
Control failures and records
A failed unit should stop the test, retain its identifier and result, and follow the project’s review and rework procedure. The fixture should reduce connection mistakes and preserve the failed condition for engineering investigation.
At minimum, link the result to the controller revision, firmware or parameters, station or tester, date, and pass or fail outcome. The exact traceability method depends on the approved production plan.
Make the project decision reviewable
Before pilot release, retain the approved controller and firmware identifiers, motor and load configuration, interface and wiring references, representative test setup, results, deviations, and open decisions. Review the package with the OEM product owner, engineering, firmware, and production representatives. It should state what evidence applies to the confirmed product and what work remains under separate responsible owners.
Scope and evidence boundary
This article is an engineering planning resource. It does not certify a product or make a performance, safety, EMC, wireless, reliability, privacy, or market-access claim. Final requirements and evidence must be established for the approved product, destination market, and responsible compliance process.
Explore relevant Sankey motor-control solutions. For an OEM engineering review, share your motor data, light or interface requirements, target market, and expected volume.
Pilot-build review checkpoint
Review the test plan after the first pilot units, using actual fixture and operator observations. Confirm that the documented sequence is unambiguous, that the approved light and motor states can be observed safely, and that a failed result is retained correctly. Update the controlled specification when a legitimate design change changes the evidence needed; do not let informal fixture changes become the production standard.
Frequently asked questions
Does a functional test prove safety or EMC compliance?
No. It verifies the listed functions under the stated conditions. Safety, EMC, reliability, and market compliance require their own evidence.
Should every unit receive identical testing?
Follow the approved quality plan. Some activities may be unit-level while others are engineering, sampling, or incoming-inspection checks.