A factory acceptance test becomes meaningful when it demonstrates agreed requirements under documented conditions. A generic checklist may show that a machine powered on, but it may not confirm performance, guarding, changeover or data functions needed for the project. Write the protocol with the supplier and technical owner before the equipment is complete.

Trace each test to a requirement
List the specification clause or functional requirement, test method, setup and pass criterion. Identify which modes, tooling and product variants are covered. Define test materials and whether the buyer or supplier provides them. Where output or accuracy is evaluated, state the measurement period, sample size and instrument.
Control test conditions
Record machine configuration, software or recipe version, utilities, environmental conditions and operator method. Confirm calibration status for instruments that determine acceptance. If a test is witnessed remotely, agree camera views, data sharing and how results are retained. A video is useful evidence but does not replace the recorded values and protocol.
Separate failures from punch-list items
Log each deviation with description, severity, owner, target date and required evidence of closure. Decide which open items prevent shipment and which may be completed before commissioning. Retest affected functions after a correction, and update the test record with the result.
Connect FAT approval to site acceptance
List functions that can only be verified after installation, integration or training. Do not treat a successful factory test as proof that the complete line will meet site output. Keep the FAT record, machine configuration and open-item list with the handover documentation.
Acceptance criteria and payment milestones should match the signed contract. Have qualified technical and commercial leads approve the protocol and final sign-off.