Use FAT to prove agreed functions before dispatch, commissioning to install and establish the equipment, and SAT to confirm site-dependent performance. Every test needs prerequisites, samples, duration, pass criteria, evidence and deviation handling.
Why this matters
Acceptance testing works when it is connected to the URS and quotation. A showroom demonstration is not automatically a FAT, and commissioning should not be an undefined opportunity to decide whether the machine is acceptable.
Decision table
| Stage | Purpose | Evidence |
|---|---|---|
| FAT | Prove agreed functions before dispatch | Check sheets, settings, counts, samples and deviations |
| Pre-dispatch | Confirm actions, documents, spares and delivery readiness | Release record |
| Commissioning | Install, connect, align and integrate | Utility and interface checks |
| SAT | Prove site-dependent output and operation | Timed production run |
| Handover | Transfer operation and support information | Manuals, backups, training and open actions |
Information to collect first
- Freeze test product, packs, materials and acceptance version.
- Confirm instruments and calibration.
- Define good count, rejects, interruptions and restart rules.
- Test critical formats, recipes, interlocks and faults.
- Record deviations with owner and retest route.
- Separate observations from pass/fail criteria.
Recommended method
- 1
Trace every test to a requirement.
- 2
Run dry functional checks before product trials.
- 3
Challenge normal stop, restart, starvation and blockage.
- 4
Retain samples and settings.
- 5
Close critical actions before release.
Common mistakes to avoid
- Using standard forms without project requirements.
- Testing only the easiest product.
- Resetting faults without recording the cause.
- Accepting a short peak-speed burst.
- Leaving training and documentation to the end.
Questions people also ask
What is the difference between FAT and SAT?
FAT is performed before dispatch; SAT is completed after installation and focuses on site-dependent results and interfaces.
How long should an acceptance run be?
Long enough to expose replenishment, heating, material-roll and recovery behaviour; agree the duration for the project.
Can actions remain after FAT?
Yes when risk and responsibility are agreed, but critical safety or core performance failures normally prevent release.
What should be handed over?
Manuals, drawings, software backups, settings, spares, training records, certificates, test evidence and actions.
Continue to the appropriate specialist route
Use the links below after defining the product, pack, output and acceptance criteria.