Field note ·
The acceptance chain: FAT, SAT, punch list and the handover that holds
Acceptance is not a meeting at the end. It is a chain of five links, and the project fails at whichever link was skipped - usually the one that felt bureaucratic at the time.

Five links, one chain
The chain runs: a specification with measurable values, a factory acceptance against that specification on your product, a site acceptance in your plant with your services, a punch list classified by severity, and a handover with a signed document pack and a date.
Each link produces a document that the next link depends on. Skip the specification and FAT has no criteria. Skip FAT and SAT becomes a commissioning exercise under time pressure. Skip the punch list classification and handover becomes a negotiation about what 'mostly finished' means.
The observed pattern is that projects do not fail at the link people worry about. They fail at the link nobody scheduled, which is almost always the document pack and the re-test.
The specification link
The specification must state the rate, the accuracy, the availability, the changeover time, the safety functions and the services drawn - each with a value, a tolerance, a measurement method and a moment of verification.
It must also state the exclusions. Every exclusion is a cost that will otherwise appear later under a different name, usually during the week when everybody is tired.
The specification is also the FAT script. If it cannot be turned into a list of tests with pass criteria, it is not a specification; it is a wish list with paragraphs.
The FAT link, run on your parts
Factory acceptance proves the machine against the specification on the supplier's floor. It should run on production parts or on parts that represent them, with the fixture and the programme that will be used in production.
The tests are: rate over a defined period at the specified mix, accuracy on a sample with a stated measurement method, safety functions one by one, changeover timed end to end, and the services consumption measured rather than assumed.
The output is a report with measured values, a punch list classified A/B/C, and a written statement of what will be closed before shipment and what will be closed on site. That classification is what prevents an argument at handover.
The SAT link, in your plant
Site acceptance proves the machine in its real environment: the plant's power quality, the plant's air, the plant's network, the plant's operators, the plant's product and the plant's interfaces.
Most SAT surprises are not machine faults. They are installation issues: a foundation that is not level, a supply voltage outside the specification, a network drop that was never installed, an interface signal that neither party implemented because both assumed the other had.
Run a readiness check two weeks before SAT using the same checklist. Photograph the floor, measure the supply, prove one signal each way. Cheap while there is time, expensive afterwards.
The punch list, classified
Class A: prevents production, or is a safety defect. Must be closed before handover. Class B: affects performance or reliability but production can run. Closed within an agreed period, with a date. Class C: cosmetic or documentary. Closed within the warranty period.
The classification is the whole value. A list of forty items with no severity is a list that will be argued item by item, and the argument will be about priority rather than about facts.
Each item needs: description, evidence, owner, target date and closure evidence. A punch list without owners is a complaint list.
The handover link
Handover is a document event, not a handshake. The pack: as-built drawings, IO schedule, risk assessment with the safety functions listed, FAT and SAT reports with measured values, spare parts BOM with manufacturer numbers, commissioning parameters recorded, training records, and the warranty terms with their start date.
The parameter record is the most underrated item. Without it, a fault two years later is forensic: someone has to reconstruct which setting changed and when. With it, the fault is diagnostic.
Set the warranty start date explicitly in the handover document. The common dispute is not about coverage; it is about whether the clock started at shipment, at installation or at first production.
The re-test that closes the loop
Retention released after a defined re-test period - commonly 30 days of production - is the mechanism that makes handover real. The re-test repeats the SAT performance tests, checks the punch list closures, and confirms the parameters are unchanged.
If retention is released at signature, the supplier's incentive to close Class B items ends at signature. If it is released after a re-test, the incentive survives the week when everybody wants to move on.
The acceptance chain in full, with the documents and the classification scheme, is worked through in our plant equipment guide.
Why this is worth the paperwork
The chain costs perhaps two weeks of project time across a six-month programme, and it converts a set of verbal understandings into a set of documents. When a machine underperforms in year two, the difference between a warranty claim and an argument is whether the acceptance records exist.
It also changes supplier behaviour before the fact. Suppliers prepare differently for a buyer who has a FAT script and a punch list classification than for one who has a purchase order and a handshake.
The five documents that decide a warranty claim
The FAT report with measured values, the SAT report with measured values, the punch list with closure evidence, the commissioning parameter record, and the handover certificate with the warranty start date. Those five decide almost every warranty argument before it starts.
The strongest of the five is the parameter record, because it is the only one that describes the machine as it was proven rather than as it was promised. When performance drifts, the parameter record answers whether the machine changed or the conditions did.
The weakest, in practice, is the punch list, because it is the document most often closed verbally. A punch item closed without evidence is a punch item that will reopen at the worst possible moment.
Who signs what
The supplier's commissioning engineer signs the measured values; the buyer's representative signs the acceptance; the safety assessor signs the safety functions; and the project owner signs the handover. Four signatures, four responsibilities, and none of them interchangeable.
Where one person signs everything - common in small projects - the documents still need to state which role each signature is exercising. Otherwise a signature that was meant to witness becomes a signature that accepted, and the difference appears in year two.
When acceptance fails
Acceptance fails most often on one of three items: rate at the specified mix, read or accuracy rate, or a safety function. The response should be written before the test, not negotiated after it.
The written response has four parts: the failure is recorded with the measured value, the cause is diagnosed jointly within a stated period, the remedy is agreed in writing, and the re-test repeats the failed test in full rather than a shortened version. A shortened re-test is how a failure becomes a concession.
The commercial mechanism that makes this work is the payment milestone. If a milestone is tied to the acceptance, the supplier has an incentive to diagnose quickly; if it is tied to shipment, the incentive is to argue.
The handover meeting that closes the project
The handover meeting should have an agenda that is entirely documentary: the pack is complete or it is not, the punch list is closed or it is not, the training records exist or they do not, and the warranty start date is agreed or it is not.
It should end with a single signed page listing those four items and the re-test date. That page is the project's last chance to be unambiguous, and it is the page that gets read two years later when something goes wrong.
Two practical habits keep the meeting short. Everything is read before the meeting rather than in it, and every open item has an owner and a date before anyone leaves the room. A handover meeting that becomes a discussion is a handover meeting that will happen again. The meeting should also be the moment the operating team is introduced to the parameter record, because that is the document they will need first.
What to check
- Turn the specification into a FAT script with pass criteria before ordering.
- Run FAT on production parts with the production fixture and programme.
- Classify punch items A/B/C with owner, date and closure evidence.
- Handover pack includes the commissioning parameter record and warranty start date.
- Release retention after a defined re-test, not at signature.