What it means
A buyer may order a machine built to its specification, and before shipment both sides can test it at the factory, where finding problems may be easier than after installation. A fictional packaging company orders a new line, and its engineers visit the maker's factory and run agreed checks, so the machine is not shipped until defined critical issues are closed.
The FAT protocol should be agreed ahead of time, listing equipment identity, drawings, test steps, expected results, tolerances and who witnesses, because a demonstration is not enough without criteria. In a fictional case, a supplier starts a motor and says it works, so the buyer asks to see safety interlocks and throughput under the agreed test plan, and results are recorded.
The test environment may use simulated loads or temporary utilities and cannot always reproduce the customer's full site, so note these limits and reserve site tests for installation effects. A fictional conveyor passes at factory voltage and simulated product weight, yet after installation it still needs checks with the real upstream and downstream equipment.
Manufacturers may use a digital twin for virtual FAT, and Siemens describes such validation for machine builders. A virtual test can supplement, but not automatically replace, the physical acceptance required by the contract, so a fictional project that tests control logic virtually before the machine is complete still keeps the final physical checks on the agreed schedule.
The buyer or a third-party inspector may witness tests, so specify whether remote viewing is permitted and how evidence is captured, because attendance does not by itself mean acceptance and a fictional customer watching via video needs a test record containing instrument readings and signatures, not merely an attendee list. Calibration and measurement quality matter, since a pass based on an unverified instrument may be challenged, so record device IDs and certificates where required; in a fictional pressure test using a gauge with expired calibration, the parties repeat the measurement with a verified gauge before release.
Non-conformities should be classified by severity: a safety defect may block shipment, while a minor documentation issue may be closed later if the contract allows, and each exception needs an owner. A fictional panel passes performance tests but lacks a label, so the buyer conditionally releases it only if the agreed protocol permits that exception and specifies correction.
A FAT checklist can include readiness, witnessed results, corrective actions and a release or hold decision, and the supplier's test record should support the decision, since a generic certificate without results is weak evidence. A fictional machine passes eight of ten scenarios, so the team logs two failures and reruns them after repair, and the final report shows both original and retest outcomes.
A factory pass does not prove shipping caused no damage, so inspect on arrival and use site acceptance tests to verify installation, connections and integration; a fictional transformer passes at the manufacturer's works and, after transport, the site team inspects it and performs required commissioning checks. Payment milestones may be tied to FAT completion or shipment release, so read the contract before assuming the test signature transfers title, risk or final acceptance, as a fictional client learns when a witnessed test sheet is signed yet installation tests are still required before final payment.
The test should include failure modes and safety functions, not only normal operation, using practical scenarios based on risk and never unsafe conditions, and software and configuration versions should be captured, because a fictional firmware update after FAT may invalidate earlier results until the affected functions are retested. Documentation such as drawings, manuals, spare parts and training plans may be FAT prerequisites or handover requirements, so state the boundary and allow time for corrections and retests, since rushing a test just before collection can create expensive site fixes, and remember that the FAT is a pre-shipment evidence gate that strengthens confidence but does not replace site commissioning, warranties or continuing quality control.
In practice
Real-world examples.
Example
A machine's safety interlock is checked at the supplier factory.
Example
A failed scenario is repaired and retested before release.
Example
Site integration is tested after the equipment arrives.
Formula
Calculation
No universal score: release follows the protocol's required passes and treatment of documented exceptions.Case study
Seen in the real world.
In this fictional case, North Mill orders an automated packing line. The first FAT reveals a failed emergency-stop scenario. The supplier repairs the logic and reruns the witnessed test. The buyer releases shipment under the contract, then schedules site integration checks after installation.
Watch out
Common mistakes.
- Treating a factory demonstration as an agreed acceptance test.
- Assuming FAT replaces site commissioning.
- Signing release without tracking failed tests and retests.
Questions
People also ask.
Where does FAT happen?
Normally at the supplier's factory or works before shipment.
Does passing FAT mean final acceptance?
Not automatically; the contract may require site testing and other milestones.
Can FAT be remote?
If the parties agree on method, evidence and applicable test requirements.
From the founder's library

Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%