Acceptance Template
Bottling Line FAT Test Record Template
Record FAT conditions, acceptance criteria, actual results, evidence files, punch-list items, responsibilities, and closure decisions.
A factory acceptance test record should show what was tested, under which conditions, what evidence was captured, and which issues remain open. A short video of a running machine is useful context, but it is not a complete FAT record. The template below helps buyers turn an agreed test plan into a traceable result.
1. Record the test identity
| Header field | Required record |
|---|---|
| Project | Buyer, supplier legal entity, project code, purchase order or contract reference |
| Equipment | Line section, machine name, model, serial or supplier reference |
| Test control | FAT protocol revision, test date, location, participants and roles |
| Test materials | Product or substitute, bottles, caps, labels, film, cartons and approved limitations |
| Operating basis | Format, fill volume, target output, test duration, utilities and environmental conditions |
2. Use one row for every acceptance item
Recommended columns are item number, requirement, test method, acceptance criterion, actual result, status, evidence reference, issue number, responsible party, target date, and closure approval. Status options should be controlled: pass, conditional pass, fail, not tested, or not applicable. A blank cell should never be interpreted as a pass.
3. Cover more than continuous running
- Safety devices, guards, emergency stops, alarms, interlocks, and restart behavior.
- Product-contact parts, cleaning access, drainage, leakage, and visible workmanship.
- Start, stop, normal production, low supply, blocked discharge, reject handling, and fault recovery.
- Output at the agreed measurement point, fill checks, closure checks, labeling, coding, packing, and reject criteria.
- Recipe selection, format changeover, tools, change parts, settings, and repeatability.
- Electrical drawings, manuals, backups, parts lists, certificates requested by contract, and training records.
4. Build an evidence index
| Evidence ID | File naming example | Minimum context |
|---|---|---|
| Photo | FAT-P-014_filler-nameplate.jpg | Date, machine, view, related test item |
| Video | FAT-V-008_line-run-format-A.mp4 | Start and end time, format, speed display, line discharge |
| Measurement | FAT-M-003_fill-check.csv | Method, instrument, sample sequence, unit, result |
| Document | FAT-D-021_electrical-drawing-revB.pdf | Title, revision, issue date, approval status |
Evidence should be understandable after the visit. Avoid unnamed phone files, isolated screenshots, or results without the tested format and criterion.
5. Control the punch list
Each issue should state the observed condition, acceptance item, production effect, immediate action, permanent correction, owner, target date, retest method, evidence, and closure decision. Separate cosmetic observations, missing documents, incomplete scope, adjustment needs, and failed performance criteria. Do not let shipment erase unresolved issues; state which items must close before packing and which can be controlled later by written agreement.
6. Sign the result without hiding conditions
The final page should summarize passed items, conditional items, failed items, not-tested items, open punch-list items, deviations accepted by the buyer, and the next release decision. Signatures or approvals should identify role and date. Approval of the record should not silently waive requirements that remain explicitly open.
The buyer and qualified technical parties should define the actual acceptance criteria before the order. This template organizes records; it does not create engineering guarantees or regulatory approval.
Questions buyers ask
How long should a FAT run?
The duration depends on the contract, equipment, product, format, output, and risks. The agreed protocol should state warm-up, stable-run, interruption, changeover, and measurement periods.
Can water replace the real beverage?
Sometimes a substitute supports mechanical testing, but its limitations must be recorded. Product behavior, temperature, viscosity, foaming, hygiene, packaging, and shelf-life conditions may require separate validation.
What happens to items that cannot be tested?
Mark them not tested, explain why, identify the later verification stage, responsible party, prerequisites, and acceptance record.