OdysseyGPT

Free template

Factory acceptance test protocol template for machines (Excel and CSV)

For machine builders and their customers: a test table with each acceptance criterion as the contract writes it, a punch list with categories and owners, and a sign-off block.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

A factory acceptance test protocol is the document a machine builder and its customer work through and sign during the FAT. This free Excel template has a header for machine, order, specification revision and participants, a test table with requirement reference, acceptance criterion, result and pass, fail or open, a punch list and a sign-off block.

Key Takeaways

  • Every test row points to a clause in the customer's specification or the contract.
  • Acceptance criteria are agreed before the FAT and copied word for word. The template supplies none.
  • A Fail or Open result always raises a punch item with a category, an owner and a date.
  • The example has 13 tests and 6 punch items for an invented carton packing machine (PO-EX-5860).

Download the machine FAT protocol

Both files are free under CC BY 4.0, with no form to fill in. The XLSX opens in Excel, Google Sheets, LibreOffice and Numbers. The CSV carries the table only; the header block is in the XLSX. Here the CSV holds the test table; the punch list is in the XLSX.

Protocol or readiness checklist: which one you need

Two different documents get called a FAT checklist. One is filled in during the weeks before the test and asks whether you are ready for the customer to arrive: procedure approved, instruments calibrated, earlier inspections closed. That is the FAT readiness checklist template. The other is the protocol on this page, run on the day itself: each test, its criterion, what was measured, and whether both sides accept it. A machine FAT needs both, in that order.

  • Project managers and commissioning engineers at machine builders, who write the protocol and lead the test.
  • The customer's project, production and maintenance staff, who watch the tests and sign.
  • Quality engineers, who follow the punch list until the last item is closed.

What the machine must achieve, for how long and with which material is a matter for the contract and the customer's specification. Some contracts also name a standard or an industry guideline for a test method. Check the governing standard or contract. For how the factory test relates to the one at the customer's site, see FAT vs SAT and site acceptance test.

Header block

Header block fields, with the invented example values
FieldExample
MachineCarton packing machine, type EX-CP-200 (fictional)
Serial no.EX-M-3318 (fictional)
CustomerExample Consumer Goods Ltd (fictional)
OrderPO-EX-5860 (fictional)
Customer specification and revisionMS-EX-01 Rev 3 (invented machine specification)
Approved layout drawingLD-EX-5860 Rev C
FAT date(s)2027-05-18 and 2027-05-19
LocationSupplier's assembly hall
Participants, supplierProject manager; commissioning engineer; controls engineer
Participants, customerProject engineer; production lead; maintenance technician
Test materialCustomer's cartons and leaflets, formats A and B, as delivered for the FAT
Protocol no.FATP-EX-5860 Rev 0

Example tests: a carton packing machine

Invented example tests for machine EX-M-3318
Test no.Requirement referenceTest descriptionAcceptance criterion (as written in the contract)Measured or observed resultResultPunch item
1MS-EX-01 2.1Documents present at the FATApproved layout drawing, electrical diagrams and risk assessment available at the approved revisionAll three present; revisions match the document listPass
2MS-EX-01 3.2Build check against the approved layout drawingMachine built as LD-EX-5860 Rev COperator-side guard door hinged on the opposite side to the drawingFailP-01
3MS-EX-01 5.1Emergency stops and guard interlocks, each one operated in turn with the machine runningEvery emergency stop and every guard interlock stops the machine4 emergency stops and 6 interlocks operated; the machine stopped each timePass
4MS-EX-01 6.1Dry run at nominal speed, no product60 minutes with no fault stop (MS-EX-01, invented customer figure)60 minutes run; no stopsPass
5MS-EX-01 6.2Output, format A, customer's cartons, one operatorAt least 120 cartons per minute, averaged over 30 minutes (MS-EX-01, invented customer figure)123 cartons per minute over 30 minutesPass
6MS-EX-01 6.2Output, format B, customer's cartons, one operatorAt least 90 cartons per minute, averaged over 30 minutes (MS-EX-01, invented customer figure)86 cartons per minute over 30 minutesFailP-02
7MS-EX-01 6.3Rejected cartons during the format A output runNo more than 0.5 % of cartons rejected (MS-EX-01, invented customer figure)11 of 3,690 cartons rejected: 0.3 %Pass
8MS-EX-01 6.5Missing-leaflet detection: 20 cartons without a leaflet fed in at random20 of 20 detected and rejected (MS-EX-01, invented customer figure)20 of 20 rejectedPass
9MS-EX-01 6.6Changeover from format A to format B by one trained operatorNo more than 20 minutes, with the supplied tools only (MS-EX-01, invented customer figure)24 minutesFailP-03
10MS-EX-01 7.1Operator panel texts and alarm listPanel texts in English and German; alarms as appendix B of MS-EX-01English complete; German text missing for 14 alarmsOpenP-04
11MS-EX-01 7.3Noise at the operator positionThe level stated in MS-EX-01 7.3, measured by the method named thereNot measured: background noise in the assembly hall too high for a valid readingOpenP-05
12MS-EX-01 8.2Compressed air consumption during the format A output runNot above the figure on machine datasheet DS-EX-CP-200 (supplier's stated figure)Below the datasheet figure; reading attachedPass
13MS-EX-01 9.1Documents handed over at the FATDraft operating manual and spare parts list handed to the customerDraft manual handed over; spare parts list not readyOpenP-06

Every acceptance figure in the example, such as the output rates, the changeover time and the reject percentage, is an invented customer's figure from an invented specification (MS-EX-01) and is labelled that way. None is a requirement of any standard. Three tests failed and three are open, so the protocol ends with six punch items. Every example value is invented: the project, customer, bidders, purchase order, prices and every document, certificate, serial and report number do not exist. Standards are named but not quoted.

Punch list and sign-off block

Invented example punch list from the FAT on 2027-05-18 and 2027-05-19
ItemTest no.Description and agreed actionCategoryOwnerDue dateClosedClosure evidence
P-012Guard door hinged on the wrong side. Re-hang as the layout drawing and re-check the interlock.ASupplier, commissioning engineer2027-05-26No
P-026Format B output below the contract figure. Find the cause, correct it and repeat test 6 with the customer present or by video, as agreed.ASupplier, project manager2027-06-02No
P-039Changeover took longer than the contract figure. Supplier to propose quick-release fixings for the carton magazine; repeat at site acceptance.BSupplier, commissioning engineer2027-07-15No
P-0410German alarm texts missing. Customer to confirm the translations; supplier to load them.BCustomer, project engineer2027-06-10No
P-0511Noise not measured. Measure at the customer's site during site acceptance, by the method the specification names.BSupplier, project manager2027-07-15No
P-0613Spare parts list not handed over. Send with the shipping documents.BSupplier, project manager2027-06-02YesSpare parts list SPL-EX-5860 Rev 0, sent 2027-05-21
CategoryCommon meaning
AMust be closed, and the affected test repeated, before the machine is released for shipment.
BMay be closed after shipment, by a date both sides agree, usually by the site acceptance test.
Sign-off block fields, with the invented example values
FieldExample
Outcome of the FATAccepted with punch list. Category A items to be closed and re-tested before shipment
Released for shipmentNo: release follows closure of P-01 and P-02
Open punch itemsCategory A: 2. Category B: 3
Deviations from the test planTest 11 not run; moved to site acceptance by agreement
For the supplier (name, signature, date)Project manager, 2027-05-19
For the customer (name, signature, date)Project engineer, 2027-05-19
AttachmentsOutput run counts; air consumption reading; photographs of P-01

Category A and B are common labels, and contracts define them differently or use other names. Use the contract's definitions. If it has none, agree them in writing before the first test.

Result values

ResultUse it when
PassThe result meets the acceptance criterion as the contract writes it, and the customer's representative saw it or accepted the record.
FailThe test was run and the result does not meet the criterion. Raise a punch item.
OpenThe test was not run, not finished, or its result is disputed. Raise a punch item saying what is left to do and where.

Columns and what to write

ColumnWhat to write
Test no.Running number, in the order the tests are run.
Requirement referenceThe clause of the customer's specification or contract that the test proves. A test with no reference is a test nobody ordered.
Test descriptionWhat is done: the format, speed, duration, material and who operates the machine.
Acceptance criterion (as written in the contract)The criterion copied from the specification or contract, with its figure and unit. Agree it before the FAT; do not write it on the day.
Measured or observed resultWhat was measured or seen, with the figure and unit, written during the test.
ResultPass, Fail or Open (drop-down). Fail rows turn red; Open rows amber.
Punch itemThe punch list number raised for a Fail or Open result. Blank for Pass.
Punch list columns
ColumnWhat to write
ItemPunch item number, quoted in the test table.
Test no.The test that raised the item.
Description and agreed actionWhat is wrong or unfinished, and what both sides agreed will be done about it.
CategoryA or B (drop-down), as the contract defines them. Rows that are category A and not closed turn red.
OwnerThe person who closes the item, supplier or customer.
Due dateThe agreed date (YYYY-MM-DD).
ClosedYes or No (drop-down). Set Yes only when the customer has seen the evidence.
Closure evidenceThe re-test record, photograph, document or site check that shows the item is done.

How to run a FAT with the protocol

  1. Before the FAT, fill in the header block and write one row per test, with the requirement reference and the acceptance criterion copied from the customer's specification or the contract.
  2. Send the protocol to the customer for agreement before the FAT date. A criterion argued over on the day is a test nobody can pass.
  3. On the day, record who is present, then run the tests in order. Write the measured or observed result as it happens, with figures and units.
  4. Set the result: Pass, Fail or Open. For every Fail or Open, raise a punch item on the second sheet and put its number in the test row.
  5. Agree a category for each punch item using the contract's definitions, then an owner and a due date. If the contract defines no categories, agree them in writing before the first test.
  6. At the end, fill in the sign-off block: the outcome, whether the machine is released for shipment, the count of open items, and any test that was left out or changed.
  7. Both sides sign and date the protocol before anyone leaves. Each takes a copy.
  8. As punch items close, set Closed to Yes and note the evidence. Take the open items to the site acceptance test.

Writing the test table from the customer's specification

The hard part of a FAT protocol is its second column: finding every clause in the customer's specification that needs a test, and copying the criterion correctly. In OdysseyGPT's Inspection & Testing module, FAT Readiness Check (beta) reads the customer's requirements, the ITP and the test procedure and lists what is not yet covered or not yet in place before the test. Customer Specification Review (beta) lists the customer's requirements with the page each one comes from. Your engineers write the tests and agree the criteria with the customer. Tools marked beta are open on request, and we onboard each team ourselves.

Want us to run the check for you?

Send your ITP and the customer's quality requirements. We send back what is covered, what is missing and what still needs evidence before the FAT.

Get the free ITP and FAT readiness check

New templates by email (optional)

Your download does not depend on this.

We use your email only for this. See our privacy policy.

Frequently asked questions

What is a FAT protocol?

The agreed list of tests for a factory acceptance test, with space to record each result and the signatures of both sides. Once signed, it is the record of what the machine did before it left the builder's works.

What should a machine acceptance test include?

Whatever the contract and the customer's specification call for. Typical subjects are a build check against the approved drawings, safety functions, a run at the contract output with the customer's material, changeover, reject handling and the documents due at the FAT. The template gives the layout, not the list.

Who writes the acceptance criteria?

They come from the contract and the customer's specification. The builder usually drafts the protocol from those documents, and the customer approves it before the test date.

What happens when a test fails at the FAT?

Record the actual result, mark the row Fail and raise a punch item. The two sides then agree whether it must be fixed and tested again before shipment or can be closed later, and write that down before they sign.

How is a FAT protocol different from a FAT checklist?

A readiness checklist is used beforehand, to confirm that documents, instruments and earlier inspections are in order. The protocol is used during the test, to record results and sign them off. Most machine orders use one after the other.

References

Creative Commons Attribution 4.0 International

Creative Commons

Visit source

Related Pages