
Food Equipment Site Acceptance Test: Installed-Line Protocol and Retest Checklist
A food equipment site acceptance test checks the installed line against agreed requirements. Its records support the decision to accept the line. It covers the site conditions and connections named in the agreed protocol.
The line runs, but what did the witness actually accept? That question gets harder when settings change during the visit. A clear protocol gives your team a shared basis for testing, recording failures and deciding what to repeat.
Use this guide for the SAT gate within food production line commissioning. The sample records below are adaptable templates. Set their limits and methods through your project review before use.
Key Takeaways
- Define the installed setup and who can approve it.
- Reuse factory evidence only where its scope still applies.
- Link each result to a requirement, observation and attachment.
- Keep failed results when corrections lead to retesting.
- Separate test completion, equipment acceptance and food release.
Planning a purchase? Use our equipment selection framework and send Loyal your product and proposed acceptance requirements to discuss the project scope.
Define the Food Equipment Site Acceptance Test Scope

Name the installed boundary and setup
Start the food equipment site acceptance test with a named boundary. List the machines, transfers and controls in scope. Include the connections supplied by the buyer. Name exclusions so nobody mistakes an untested upstream process for an accepted part of the line.
Use a cover sheet that lets a later reviewer name the exact setup. Record the protocol ID and revision, equipment IDs, approved layout and interface schedule. Add the software version, recipe or settings record, and products or pack formats covered.
Name the executor, witness and acceptance authority separately. The person running a test may lack the right to accept the line. Agree who can approve a change to the method or expected result while work is in progress.
For the food equipment site acceptance test cover sheet, include the criteria references, planned attachments, exclusions and open starting checks. Give each supporting document a revision. A layout title without a version leaves room for two people to test different boundaries.
Reuse FAT evidence with a documented reason
Review the food processing equipment FAT record before choosing site checks. For each requirement in scope, name the factory evidence and any open item. Note what changed after shipping. Then state whether to reuse the evidence or run a site test.
Factory approval covers the tested conditions. Installed utilities, buyer-added equipment or changed settings need their own review. The food equipment site acceptance test should show why a factory result remains relevant rather than copying its pass box.
Illustrative scenario: A standalone conveyor has a factory test record. The buyer adds a transfer at the installed line. Keep the factory evidence for its original scope and list the added transfer as a site check. This example records a question to resolve; it claims no successful outcome.
Freeze the agreed protocol before execution. If the boundary changes, revise the affected tests and obtain the named approval. For your food equipment site acceptance test, define what signatures mean in the project documents.
Do not infer rules for payment or warranty from a generic checklist. The same applies to automatic acceptance.
Release the Installed Line for Controlled Testing
Verify installation, access and utility evidence
Readiness gives permission for a named test. It does not close the food equipment site acceptance test. Check that the required installation checks and utility records exist. Confirm safe test plans before releasing the next activity.
In Great Britain, HSE inspection guidance addresses equipment whose safety depends on installation conditions. Base the checks on a risk review. The reviewer needs the skills for that work. Keep that review distinct from the SAT signature.
Record utility evidence against the demand expected during the test. A connection label alone cannot show the conditions at the equipment while it runs. Use limits agreed for the project and skilled reviewers; this guide supplies no universal pressure, voltage or temperature setting.
For a food equipment site acceptance test readiness sheet, use these fields:
| Starting check | Evidence reference | Responsible reviewer | Status | Activity held |
|---|---|---|---|---|
| Installed layout and access | Approved installation record | Installation lead | Ready or held | Named test |
| Utilities under planned demand | Site measurement record | Utility reviewer | Ready or held | Named run |
| Safe test arrangements | Approved method and review | Competent reviewer | Ready or held | Named check |
| Materials and hygiene | Release record and lot IDs | Site quality lead | Ready or held | Product run |
Confirm test materials, hygienic readiness and people
Name the materials, formats and sample labels before the food equipment site acceptance test begins. Agree who supplies them and who controls their use. Confirm who will run the line and whether cleaning is complete. Check access for the witness and the route for raising a concern.
If a test needs a site resource that is not ready, name it. Record which test must wait and who can release that hold.
Check the site’s applicable food-safety scheme edition. FSSC’s equipment-management guidance is identified as V6; its official Version 7 FAQ gives the transition timetable. V6 audits remain allowed through 30 April 2027, with V7 upgrade audits starting 1 May 2027. Confirm the applicable edition with the site’s scheme reviewer.
Keep this readiness review alongside the site’s food production quality standards guidance. If a required record is absent, hold the affected activity and assign an owner. Don’t record the food equipment site acceptance test as passed merely because the team arrived.
Build a Food Equipment Site Acceptance Test Protocol

Give every test a result and evidence reference
A tick cannot explain which setting, sample or observation made a test pass. Build each food equipment site acceptance test row around a requirement and its agreed result. Use the agreed food equipment acceptance criteria as the basis rather than inventing limits during execution.
Use this blank record structure. Split it across linked form pages if the fields become hard to read:
| Record group | Fields to complete |
|---|---|
| Identity | Test ID, requirement ID and revision, protocol revision |
| Starting conditions | Installed setup, settings, starting checks, material and sample IDs |
| Method | Approved procedure reference, instrument or observation method, expected response |
| Execution | What happened, date/time, executor, witness, attachment reference |
| Disposition | Pass, fail, not tested or held; deviation ID; reviewer |
Define the status labels before testing. Use pass when the recorded evidence meets the approved criterion. Use fail for an observed mismatch.
Use not tested when execution did not occur, and held where a stated starting check blocks it. Agree what each label means in your project.
For the food equipment site acceptance test evidence index, assign each attachment an ID. Record its filename, related test and date/time. Keep the original file alongside any marked-up copy.
A reviewer should be able to trace a result. They should not have to guess which photo belongs to it.
Illustrative scenario: An approved method checks a transfer’s feed response to a downstream status. The controller records the signal, but the agreed material-feed response is absent. This example concerns evidence recording; qualified personnel must define the safe method.
| Worked record field | Illustrative entry |
|---|---|
| Test / requirement | SAT-IF-A / approved interface schedule, current revision |
| Expected response | Feed response specified by that schedule |
| What happened | Signal recorded; specified feed response absent |
| Evidence | Linked event record and witness observation |
| Result / next action | Fail; open DEV-A and hold closure pending review |
Distinguish observing from approving
Keep the test entry and witness record visible. Ask the approver to review the evidence and scope. For a food equipment site acceptance test, “witnessed” should describe who took part, not silently grant the right to accept the line.
For remote witnessing, agree the camera view, test IDs, time references and local evidence owner. ARANOW’s linked video description presents an external supplier example of remote FAT/SAT interaction. Use it to frame questions about remote witnessing. It does not show Loyal services or replace your protocol.
Before the call, agree who keeps the local record. Give remote witnesses the same test IDs as the site team. Keep their questions with the test row.
If a connection drops, record what the witness missed. Agree how to cover the missing evidence. Do not sign for an unseen check. To discuss your proposed food equipment site acceptance test scope, share the product, interface schedule and criteria with Loyal.
Execute Food-Specific Checks and Capture the Result
Check agreed functions, interfaces and hygienic access
During the food equipment site acceptance test, capture what happened under the named conditions. Skilled staff should use approved methods for normal operation, stops, restart and inspection functions. Keep this article’s records separate from the detailed procedures used to perform those checks safely.
For US facilities within its scope, 21 CFR 117.40 addresses equipment cleanability, installation access and contamination protection. It also addresses relevant instruments and control devices. These are reasons to collect appropriate evidence, not a universal SAT form or a certification claim.
Record food-specific checks at the installed line. Note where each check took place. Ask whether the agreed access can be demonstrated in its actual location. Keep access notes distinct from proof that cleaning works.
A photo of an opened cover shows access. It cannot prove that a cleaning process meets its goal.
Use the following evidence prompts for the food equipment site acceptance test:
| Installed condition | Agreed observation | Record to retain |
|---|---|---|
| Transfer and receiving equipment | Specified interface response | Setup, event record, actual response |
| Cleaning and inspection access | Access described in the approved requirement | Location, observation, unresolved restriction |
| Inspection and rejection, if included | Required detection and physical disposition | Test-item identity, observed result, attachment |
| Product or format run | Agreed product and process checks | Lot, settings, conditions, sample references |
Link material runs to conditions and samples
Keep the food equipment site acceptance test sample record tied to the test ID. Note material lots, format, settings and any site condition that affects the result. Distinguish start-up material, rejected material and accepted output using the agreed definitions.
If the protocol includes output measurement, reference its approved counting method and test period. Leave detailed capacity analysis to that test package. A displayed speed is not, by itself, the record of accepted output required by the agreed method.
Preserve raw observations before summarizing them. If someone changes a recipe or setting mid-run, mark when it changed and which samples belong to each setup. That lets the food equipment site acceptance test reviewer decide which records belong to the final setup.
A finite run only supports the conditions it covers. Do not extend a good sample to all products, future operation, shelf life or pathogen control. Ask the site quality lead to decide how to use or dispose of the food. Link work outside this scope to the wider commissioning record.
Control Deviations, Retests and the Acceptance Decision

Keep the deviation and review what changed
A repair is a change to review, not proof that a test now passes. Keep the original food equipment site acceptance test result and open a linked deviation. Record the requirement, actual mismatch, evidence and effect on the planned acceptance decision.
Give the issue an owner. Name who can approve the proposed fix. Record the changed part, document, software or setting with its revision.
If the cause is still unknown, say so. A fix can remove a symptom without proving its cause.
Use a deviation record with fields for impact, correction owner, change reference, proposed retest scope and closure authority. Link it to both the failed test and the retained as-found evidence. For the food equipment site acceptance test, keep those links visible after closure.
Illustrative scenario: A controls change addresses the missing feed response in the worked example. Before closure, the engineer reviews which stop and restart checks the change could affect. The next step is an approved retest scope, not an invented successful result.
Execute and review the retest
Use this retest checklist as a record to adapt to your project:
- Link the original test, deviation and as-found attachments.
- Name the correction and final setup revision.
- Review effects on related functions and previously passed tests.
- Confirm unchanged criteria, or obtain approval for revised criteria.
- Approve the retest method, scope, people and starting checks.
- Record materials, samples, conditions and what happened in the retest.
- Attach raw results and complete the affected checks.
- Record the review decision, remaining holds and closure authority.
Do not lower a criterion solely to remove a failure. If requirements genuinely change, keep the reason and approval with the new revision. Your food equipment site acceptance test record must show which result was judged against which requirement.
If retesting fails, retain that result too. Update the deviation with the next action and hold the affected decision. If it passes, link the evidence and check that all approved retest work is complete. A successful local check does not close an unrelated missing document.
Sign only the documented scope
Assemble the executed food equipment site acceptance test protocol, evidence index, deviations, retests and final setup record. Add remaining open items, their owners and any approved restrictions. Keep document handover and training records identifiable rather than hiding them in a test score.
Keep three decisions distinct. Was the test done? Is the equipment accepted within the named scope? Has the site quality lead released the food?
Name who makes each decision. If the contract allows a limited acceptance, record its exact scope and limits. A template cannot grant that permission.
Before signing, ask whether an absent colleague could reconstruct the decision from the pack. They should see what was tested and what failed. They should also see what changed and what remains held. That is the practical closing check for a food equipment site acceptance test.
Food Equipment Site Acceptance Test Questions
Does a passed FAT replace site acceptance testing?
A passed FAT supports the conditions tested at the supplier’s premises. Review it against the installed setup before reusing evidence. Utilities, added transfers and changed settings may need site checks. Your food equipment site acceptance test protocol should name what carries forward, why it remains applicable and what still needs testing.
What should a food-equipment SAT protocol record?
Record the requirement and revision, installed setup, starting conditions, approved method, expected result and what happened. Link materials, samples, instruments and attachments where relevant. Add the executor, witness, result and deviation reference. The purpose is to let an authorized reviewer follow the evidence behind each decision without having to recall the visit from memory.
What happens when a required test is not performed?
Mark the required test as not tested or held, using the status definitions agreed for the project. State the reason, responsible owner and next action. Keep the gap visible in the acceptance record.
A missing result is not a pass. Do not silently remove the test from scope.
What needs retesting after a software or mechanical change?
Review the changed function and any related checks that the change could affect. Record that review and obtain approval for the retest scope. Repeat the original failed check and the affected checks under approved conditions. Retain the original failure, changed setup, actual retest evidence and the named reviewer’s closure decision.
Does SAT approval release food for commercial sale?
SAT approval concerns the agreed equipment acceptance scope. Food release remains a separate decision under the site’s food-safety and quality controls. Do not infer sale permission, sanitation effectiveness or shelf-life evidence from an equipment signature. Ask the site’s responsible quality authority how trial materials and finished samples must be held, used or disposed of.
Agree the next SAT decision. A useful food equipment site acceptance test ends with a traceable setup and a clear list of remaining holds. Return to the added-transfer example: the missing site evidence needs an owner, approved method and recorded result. It cannot be settled by repeating the factory pass.
Before your next review, gather the installed boundary, available FAT record, current criteria and open questions. Send Loyal your intended product and proposed SAT requirements to discuss your project. Define the next decision and the evidence needed to make it, then keep both with the final executed protocol.
