An engineering sample is a learning and verification step, not automatic authorization for production. For a ceiling fan light, approval depends on the complete configuration: controller hardware, firmware, motor, light assembly or driver, harness, enclosure, remote or wall input, and the requirements for the destination market. The stage gates below help OEM teams turn sample feedback into a controlled pilot decision.
Gate 1: Freeze the sample baseline
Before testing, assign identifiers to the controller revision, firmware build, motor and light assembly, harness, enclosure, and relevant drawings. Record the supply and test environment. Keep a sample manifest with serial or lot identification where available, and photograph the assembled unit and connector arrangements when those views help identify the configuration.
List every open assumption. For example, identify whether the light source is final, whether a harness is representative, and whether the tested enclosure matches the intended product. A sample cannot validate an input that was not present or controlled in the test setup.
Gate 2: Agree on observable acceptance criteria
Translate product requirements into checks that a reviewer can observe and record. Typical categories include fan command response, light on/off and any approved dimming behavior, remote or wall-input behavior, command conflicts, startup and restart behavior, indicator or fault response, connector fit, and assembly clearance. Include only functions that are in the released project scope.
For each check, specify the setup, action, expected result, pass/fail rule, and evidence to retain. Agree the criteria before running the test. Numeric limits and safety-related requirements must come from the approved product specification and applicable engineering/compliance process; do not substitute generic internet values.
Gate 3: Test the integrated assembly
Review controller behavior with the actual motor and light combination, not only with an isolated board. Check that the intended wiring and connectors are used, that the harness can be routed and serviced as designed, and that the light and fan commands behave independently or jointly as required. Record abnormal behavior and reproduce it before changing the design where practical.
Use the project’s approved verification plan for electrical, thermal, EMC, mechanical, and regulatory work. An engineering functional check does not by itself establish safety, EMC compliance, or market authorization. The ceiling fan controller validation planning guide explains the importance of defining responsibilities and evidence separately.
Gate 4: Resolve deviations and control changes
Log each deviation with a description, affected configuration, severity or project priority, owner, proposed action, and disposition. Decide whether it is fixed, accepted with documented rationale, deferred from scope, or requires additional testing. Re-test affected behaviors after a hardware, firmware, motor, light, or harness change.
Maintain a simple change-impact record that links the change to affected requirements and checks. A small connector or firmware change can alter assembly, command behavior, or test coverage; review impact rather than relying on the size of the change as a measure of risk.
Gate 5: Prepare the pilot release package
Before the pilot build, assemble the approved bill of materials and alternates policy, released drawings, firmware identifier and programming method, assembly instructions, inspection points, production test specification, label and packaging requirements, and deviation disposition. Confirm that production uses the same approved revisions represented by the release package.
Define what the pilot is intended to learn: assembly flow, test coverage, workmanship, configuration consistency, packaging, or another named objective. Identify sample size and acceptance rules with the responsible product and quality owners; these should be set for the project, not copied from an unrelated product.
Gate 6: Record the production decision
The approval record should name the exact configuration, test evidence reviewed, remaining limitations, and the people authorized to approve engineering, quality, and product release. If market-specific certification or customer approval remains open, state that production release is conditional on those items rather than implying they are complete.
After the pilot, compare build and test results against the agreed criteria. Record nonconformities, corrective actions, and any approved revisions. Update the released documentation before the next build so that purchasing, production, and service teams are working from the same baseline.
Sample-to-pilot record checklist
- Sample manifest and configuration identifiers for hardware, firmware, motor, light, harness, and enclosure.
- Approved requirements and acceptance criteria with setup and evidence expectations.
- Integrated test results, photos or logs where useful, and identified limitations.
- Deviation log with owner, disposition, and retest status.
- Change-impact review tied to affected requirements and validation.
- Pilot BOM, drawings, programming and assembly instructions, and production test outline.
- Named engineering, quality, customer, and compliance approval owners.
- Written release decision and any remaining conditions.
Connect the gates to your product brief
For related design inputs, see the fan light wiring and harness checklist and the fan light controller functional test plan. Share your product requirements, current sample configuration, target market, and expected production timing through the Sankey contact page to establish which gates and evidence apply to your project.