Feeder System Documentation Requirements: FAT, SAT, and Validation Deliverables

Missing documents delay qualification more than missing features

In regulated manufacturing — medical devices, pharmaceuticals, automotive safety components — a feeder system that works perfectly on the floor still cannot be released to production until the documentation package is complete. A missing electrical schematic, an unsigned FAT report, or an incomplete traceability matrix can hold up qualification for weeks while the supplier scrambles to produce the paperwork. The feeder itself is ready; the paper is not.

This happens because documentation requirements are often specified vaguely in the purchase order, or not specified at all. The supplier delivers what they consider standard, the quality team reviews it against their internal SOP, and the gaps surface during the qualification review — the worst possible time to discover them. Fixing documentation retroactively is expensive, error-prone, and erodes confidence in the supplier.

This guide defines the minimum documentation package for a feeder system in a regulated environment, breaks down what FAT, SAT, and IQ/OQ/PQ each require, identifies the most common gaps, and explains how to specify documentation requirements in the RFQ so there are no surprises. It builds on our FAT vs SAT comparison guide and our IQ/OQ/PQ guide for feeding systems.

The minimum documentation package

Every feeder system, regardless of industry, should be delivered with a baseline set of documents. In regulated industries, this baseline is mandatory; in non-regulated industries, it is still best practice because it reduces troubleshooting time and supports future maintenance.

Each document should be revision-controlled, dated, and reference the specific feeder serial number or order number. A generic manual that does not match the actual configuration of the delivered system is a common source of qualification findings.

• Drawings must match the as-built configuration: not the design intent, not the prototype — the actual shipped unit.
• BOM must list commercial parts by manufacturer and part number: "proximity sensor" is not acceptable; "Omron E2E-X5ME1-Z" is.
• Controller manual must include the actual parameter settings: not factory defaults, but the settings tuned for your specific part and feed rate.

FAT protocol and report

The Factory Acceptance Test is performed at the supplier's facility before the feeder ships. The FAT documentation package consists of two parts: the FAT protocol (written before testing) and the FAT report (completed during and after testing).

FAT protocol defines the test scope, acceptance criteria, test methods, and required equipment. It should be written collaboratively between the supplier and the customer, reviewed and approved before testing begins. A protocol written after the test is not a protocol — it is a summary, and it carries no weight in a regulatory audit.

The FAT protocol for a feeder system should include:

• Scope and objectives: what is being tested and why.
• Test prerequisites: utilities, sample parts, test equipment, environmental conditions.
• Test procedures: step-by-step instructions for each test, including duration, measurements, and observations.
• Acceptance criteria: quantitative pass/fail thresholds for feed rate, orientation yield, jam rate, noise level, and any customer-specific requirements.
• Test equipment list: calibration status and traceability for any measurement instruments used.
• Roles and responsibilities: who performs each test, who witnesses, who approves.

FAT report documents the actual test results. It must include:

• Completed test procedures: each step signed off with actual measured values.
• Deviations: any test that did not meet acceptance criteria, with root cause and disposition.
• Photos and videos: visual evidence of the feeder running with production parts.
• Punch list: open items that must be resolved before or after shipment.
• Signatures: supplier test engineer, customer witness, quality representative.

The most common FAT documentation gap is the absence of a pre-approved protocol. When the supplier shows up on FAT day with a handwritten checklist instead of a formal protocol, the customer's quality team cannot accept the results — even if the feeder performs flawlessly. The protocol must exist before the test, not after.

SAT protocol and report

The Site Acceptance Test is performed after the feeder is installed at the customer's facility. SAT documentation follows the same structure as FAT documentation but addresses a different set of risks: those introduced by transport, reinstallation, site utilities, and line integration.

SAT protocol should reference the FAT results and define which FAT tests are repeated at SAT, which are confirmed only, and which new tests are added. Tests that depend on site-specific conditions — real PLC integration, actual factory air quality, operator interaction, line timing — must be in the SAT scope.

The SAT protocol should include:

• Reference to FAT report: FAT results, punch list status, and any deviations carried forward.
• Installation verification: confirmation that the feeder is installed per the mechanical and electrical drawings, with correct mounting, leveling, grounding, and utility connections.
• Integration tests: PLC handshake signals, safety circuit function, alarm response, and feed rate under actual line timing.
• Environmental tests: performance with real factory air, ambient temperature, and vibration from adjacent equipment.
• Operator workflow: refill access, jam clearing procedure, alarm acknowledgment — tested with actual operators, not engineers.

SAT report follows the same format as the FAT report: completed procedures, deviations, photos, punch list, and signatures. The SAT report is typically the document that triggers the formal release to production in regulated environments.

A common SAT gap is failing to test with actual production parts. FAT is often run with "golden samples" — carefully selected parts that represent the ideal geometry. SAT must use parts from the actual production lot, including the normal range of variation. A feeder that passes FAT with golden samples but fails SAT with production parts has not been validated for its intended use.

IQ/OQ/PQ documentation

In pharmaceutical and medical device manufacturing, feeder systems are qualified through a three-phase process: Installation Qualification (IQ), Operational Qualification (OQ), and Performance Qualification (PQ). Each phase has its own protocol and report, and the documentation requirements are more rigorous than FAT/SAT alone.

Installation Qualification (IQ) verifies that the feeder is installed correctly per the design specifications. IQ documentation includes:

• Installation verification checklist: model/serial numbers, utility connections, mounting, grounding, cable routing.
• As-built drawings: confirmed against the design drawings, with any deviations documented.
• Calibration certificates: for any integrated measurement devices (sensors, counters).
• Software version documentation: controller firmware version, PLC program version, HMI application version.

Operational Qualification (OQ) verifies that the feeder operates correctly across its specified operating range. OQ documentation includes:

• Functional test results: start/stop, alarm response, feed rate adjustment range, orientation yield at minimum and maximum speeds.
• Alarm and interlock verification: each alarm condition triggered and confirmed to produce the correct response.
• Boundary condition tests: performance at minimum and maximum part load, minimum and maximum air pressure, minimum and maximum ambient temperature (if specified).
• Changeover procedure validation: if the feeder handles multiple part types, the changeover procedure is documented and timed.

Performance Qualification (PQ) verifies that the feeder performs consistently under actual production conditions over an extended period. PQ documentation includes:

• Extended run results: typically 3 consecutive runs of specified duration (e.g., 1 hour each) at production speed, with feed rate and orientation yield recorded.
• Statistical analysis: mean, standard deviation, and Cpk for feed rate and orientation yield across the PQ runs.
• Part quality verification: inspection of parts after feeding to confirm no damage, no contamination, correct orientation.

Traceability matrix

A traceability matrix links each user requirement to the test that verifies it, the protocol section that defines the test, and the report section that documents the result. In a regulatory audit, the auditor uses the traceability matrix to confirm that every requirement has been tested and that every test traces back to a requirement.

For a feeder system, the traceability matrix typically maps:

• User Requirement Specification (URS) items → FAT/SAT/IQ/OQ/PQ protocol sections → corresponding report sections.
• Functional requirements (feed rate, orientation yield, jam rate) → OQ test procedures → OQ results.
• Safety requirements (E-stop, interlocks, guarding) → IQ/OQ test procedures → IQ/OQ results.
• Documentation requirements (drawings, manuals, certificates) → IQ verification checklist → IQ report.

The most common traceability gap is orphan requirements: a URS item that has no corresponding test, or a test that does not trace back to any requirement. Both indicate that the qualification scope is incomplete.

• Every URS item must map to at least one test: if a requirement is not tested, it is not verified.
• Every test must trace to a requirement: if a test has no requirement, it may be unnecessary or the requirement may be missing.
• Build the traceability matrix early: during protocol development, not after qualification is complete.

Common documentation gaps that delay qualification

After reviewing hundreds of feeder qualification packages, the same gaps appear repeatedly. These are the items most likely to generate audit findings or delay production release:

1. As-built drawings do not match the delivered unit. The supplier provides the design drawings from the proposal phase, but the actual build has minor differences — a different sensor model, a relocated cable gland, a modified tooling feature. The quality team flags these as deviations, and the supplier must produce revised drawings. This takes days to weeks.

2. Controller parameter settings are not documented. The controller manual describes the parameters but does not record the actual values set during commissioning. When the feeder needs to be replicated or the controller is replaced, there is no record of the correct settings.

3. BOM lists internal part numbers instead of commercial equivalents. The supplier's BOM uses their own internal numbering for sensors, connectors, and coils. The customer's maintenance team cannot source replacements without cross-referencing to commercial part numbers. This is not just a documentation issue — it is a spare parts availability issue.

4. FAT protocol was written after the test. The supplier performed the test, then wrote the protocol to match the results. In a regulated environment, this invalidates the FAT. The protocol must be approved before testing begins.

5. Risk assessment is missing or generic. For CE-marked equipment, a risk assessment per ISO 12100 is mandatory. A generic risk assessment that does not address the specific hazards of the feeder (pinch points, ejected parts, noise) will not satisfy the auditor.

6. Calibration certificates are expired or missing. Any measurement instrument used during FAT or SAT — power meters, sound level meters, air pressure gauges — must have a valid calibration certificate traceable to a national standard. Expired calibrations invalidate the test results.

Specifying documentation requirements in the RFQ

The most effective way to prevent documentation gaps is to specify the requirements in the RFQ, before the supplier quotes the project. This ensures the supplier budgets the engineering time to produce the documents and delivers them as part of the project scope, not as an afterthought.

Include the following in your RFQ:

• Document list with format requirements: specify each required document, the format (PDF, native CAD, etc.), and the revision control standard.
• FAT/SAT protocol ownership: specify who writes the protocol (customer, supplier, or jointly) and the approval workflow.
• Qualification standard: reference the applicable standard (ISPE GAMP 5, ISO 12100, IEC 62443) so the supplier understands the rigor level.
• Traceability matrix requirement: require a traceability matrix linking URS items to test protocols and reports.
• As-built documentation timeline: require as-built drawings and final BOM to be delivered within 2 weeks of shipment, not after qualification.
• Document retention: specify the retention period and whether the supplier must maintain archived copies.

When documentation requirements are in the RFQ, the supplier can price them accurately. When they are added as a change order after the project starts, the supplier treats them as out-of-scope work, and the cost and timeline inflate accordingly.

Frequently asked questions

Who should write the FAT protocol — the supplier or the customer?

The best practice is joint development. The supplier knows the feeder's capabilities and test methods; the customer knows the acceptance criteria and regulatory requirements. The supplier drafts the technical test procedures, the customer reviews them against the URS and qualification plan, and both parties approve the final protocol before testing begins. If the customer writes the protocol alone, it may include tests that are impractical at the supplier's facility. If the supplier writes it alone, it may omit tests that the customer's quality team requires.

Can FAT and SAT be combined into one test?

In non-regulated environments, yes — some customers skip FAT and perform all acceptance testing at SAT. In regulated environments, this is strongly discouraged. FAT and SAT verify different things: FAT verifies the supplier's build under controlled conditions, SAT verifies the installed system under real conditions. Combining them means you cannot distinguish between a supplier build issue and a site integration issue, which makes root cause analysis and responsibility assignment much harder. Our FAT vs SAT guide explains this distinction in detail.

What if the supplier cannot provide CE documentation?

If the feeder will be installed in the EU, CE marking is mandatory. If the supplier cannot provide a Declaration of Conformity, a risk assessment per ISO 12100, and the technical file required by the Machinery Directive, you have two options: find a different supplier, or accept responsibility for the CE marking process yourself. The second option is expensive and legally risky — you become the "manufacturer" for CE purposes and assume all liability. It is almost always better to select a supplier who can provide CE documentation from the start.

How long should documentation be retained?

In pharmaceutical manufacturing, the FDA requires equipment qualification records to be retained for the life of the equipment plus one year, or as specified in your site SOP (whichever is longer). For medical devices, ISO 13485 requires retention for the lifetime of the device plus the applicable regulatory period, which can be 15-25 years. In practice, most companies retain feeder qualification documentation for the entire operational life of the feeder, which is typically 10-15 years. Digital archiving makes this inexpensive; the cost of not retaining it is a regulatory finding.

Do I need separate IQ/OQ/PQ protocols, or can I combine them?

In pharmaceutical manufacturing, separate protocols are the standard and are expected by regulators. Combining IQ and OQ is sometimes acceptable if the scope is small, but PQ should always be a separate protocol because it requires extended production runs that cannot be performed during installation. In medical device manufacturing, the expectation is three separate protocols. Combining them creates a document that is difficult to review and harder to defend in an audit. The incremental cost of three protocols versus one is small compared to the risk of a qualification finding.

Conclusion

Documentation is not overhead — it is the evidence that your feeder system was built, tested, and qualified correctly. The most common reason for qualification delays is not a technical problem with the feeder but a gap in the documentation package: a missing drawing, an unsigned protocol, an incomplete traceability matrix. These gaps are preventable if you specify documentation requirements in the RFQ, require the FAT protocol to be approved before testing, and build the traceability matrix during protocol development rather than after qualification. The cost of producing complete documentation during the project is a fraction of the cost of producing it retroactively under audit pressure. If you need help structuring your feeder documentation requirements or want a supplier who delivers a complete qualification package, contact our engineering team.