FDA Documentation Support From Your Manufacturer

Who holds the submission, and who holds the evidence

There is a recurring confusion in device sourcing that costs brands time and, occasionally, a rejected filing: the belief that a contract manufacturer can “handle the FDA” for you. It cannot, and any manufacturer that says it can is misrepresenting how the system works. A regulatory submission belongs to the party that puts the device on the market—the brand owner and its regulatory team. The manufacturer’s job is different and specific: to produce the technical evidence the submission rests on.

That distinction is not a disclaimer. It is the operating boundary of the relationship, and getting it clear before you sign is one of the higher-leverage things a sourcing manager can do. This guide draws the line: what the brand owns, what the manufacturer provides, what the common document set looks like for a home-use device, and how to verify a manufacturer’s documentation capability before it is your problem.

The line: brand owns the filing, manufacturer owns the file

Think of it as two stacks of paper that meet but never merge.

The brand’s stack is the regulatory strategy and the submission itself: the device classification, the regulatory pathway (for a US device, that may be a premarket notification such as a 510(k), or another route depending on class and claims), the intended-use and indications-for-use statements, the labeling claims, and the correspondence with the agency. Whoever writes the claims and signs the filing carries the regulatory liability for them. That is the brand and its regulatory consultants. It cannot be delegated to a factory, because the factory does not own the claims.

The manufacturer’s stack is the technical foundation those claims stand on: the design documentation, the component and materials data, the test records, the production records, and the quality-system evidence that the device is built consistently and to specification. A submission is only as strong as this stack. A well-run manufacturer produces it as the natural output of its quality system; a weak one produces it as a scramble at the end of your program, if at all.

The two stacks connect at a single seam—the manufacturer hands its evidence to the brand’s regulatory team, which assembles and files. Draw that seam clearly in the contract and most of the downstream friction disappears.

What “documentation and testing support” actually includes

When a manufacturer offers documentation and testing support, that phrase should resolve into concrete deliverables. Ask for them by name:

• Design documentation. Design inputs and outputs, drawings and revision history, the bill of materials with component specifications and sourcing data, and the risk-management file. For a device where the manufacturer also does design work, this is the design-history evidence; for build-to-print, it is the incoming design under revision control.
• Test reports. Results against the safety and electromagnetic-compatibility standards the target markets require—for medical electrical equipment, the IEC 60601 family; for the electronics, EMC and hazardous-substance testing—plus coordination with the third-party test labs that issue them.
• Production records. The batch or device records that prove each unit was built in accordance with its specification: the “how this lot was actually made” evidence, traceable to component lot numbers, process parameters, and inspection results.
• Change management. A controlled process for engineering changes, with revision control and impact assessment, so that a change made after the submission does not quietly invalidate the evidence it was based on.

Notice what is not on that list: writing the submission, corresponding with the agency, or holding any registration or clearance. Those belong to the brand. A manufacturer contributes the foundation; it does not file.

The common document set for a home-use device

This is general guidance, not a substitute for your regulatory team’s judgment—the exact set depends entirely on the device, its class, and its claims. But for a home-use device, the evidence a brand typically needs from its manufacturer clusters around a recognizable core:

• Device description and specifications
• Bill of materials with component and materials data (including biocompatibility data where the device contacts skin)
• Design and manufacturing drawings under revision control
• Risk-management file
• Verification and validation test protocols and reports
• Electrical safety and EMC test reports for the target markets
• Production and inspection records demonstrating consistent manufacture
• Quality-system records (the manufacturer’s ISO 13485 evidence)
• Labeling and instructions-for-use inputs, where the manufacturer contributes to them

A brand’s regulatory team maps this evidence onto whatever submission format the target market requires. The manufacturer’s responsibility is that each item exists, is current, and is traceable. If a manufacturer cannot produce this set on request for an existing program, treat that as the answer to whether it can produce it for yours.

The quality system underneath it all

The reason a mature manufacturer produces this evidence routinely is that its quality system is built to. ISO 13485:2016 is the medical-device quality management standard, and its requirements—design controls, traceability, records of production, corrective and preventive action—are precisely the machinery that generates the documentation a submission needs. In the United States, the FDA’s Quality Management System Regulation (QMSR), which replaced the older Quality System Regulation under 21 CFR 820 and aligns it with ISO 13485, governs the quality system for devices on the US market. The convergence is the useful part for a buyer: a manufacturer running a genuine ISO 13485 system is already producing evidence in the shape US expectations require.

This is why the quality system, not the sales pitch, is the thing to audit. For how to verify one rather than trust the certificate, see our guide on ISO 13485 contract manufacturing.

How to verify documentation capability before you sign

Documentation capability is easy to claim and easy to check. Do the checking before the contract, not during your submission.

1. Ask for a redacted sample set. Request a redacted design document and a completed production record for an existing product. A manufacturer with a real system can produce them; one that promises to “put it together later” is describing a system that does not yet exist.
2. Walk a unit backward. Pick a lot number and ask them to reconstruct it—component lots, process records, inspection results. Traceability that works in front of you works in an audit.
3. Test the change process. Ask how an engineering change order moves through their system, who signs off, and how revision control keeps the documentation package consistent afterward.
4. Confirm the test-lab relationships. Ask which third-party labs they coordinate with and to see a recent test report they handed to a customer.
5. Match the scope to your market. Confirm their quality-system scope and compliance experience cover your device type and target markets—CE, FCC, RoHS, PSE as applicable—and that their production records meet the expectations of the US quality-system framework if you sell there.

If a manufacturer clears these five, its documentation and testing support is real. If it deflects on any of them, you have found out cheaply.

”We don’t do your filing”—why that is the honest position

It can feel reassuring when a manufacturer says it will “take care of the FDA.” It should do the opposite. A manufacturer that offers to make your submission is either misunderstanding the regulatory structure or misrepresenting it, and either way it is a signal to walk. The submission carries the claims, and the claims carry the liability; both belong to the brand. A manufacturer’s honest position is the narrow one: we provide the documentation and testing support your filing rests on—design records, component data, test reports, production records, and change management—and we build to the safety and EMC standards your markets require so the evidence comes back clean. We do not make the submission, and we are not described as holding any approval or clearance. That is not a limitation. It is the correct division of labor, and a manufacturer that states it plainly is telling you it understands the system it operates in.

How we support submissions

Gooten Innolife is a Taichung-based OEM/ODM manufacturer founded in 1996, holding ISO 13485:2016 and ISO 9001:2015 certification, with production, R&D, and quality assurance co-located at a single site. We provide documentation and testing support that feeds a brand’s regulatory work: design documentation, component and materials data, test records, and coordination with third-party test labs, all produced inside the quality system rather than assembled after the fact. We have compliance experience across CE, FCC, RoHS, and PSE. We do not make regulatory submissions—those belong to the brand and its regulatory team—and we build to the safety and EMC standards your target markets require so the test results support your filing.

The evidence for this way of working is longevity: our longest active engagement has run more than 18 years across four product generations of a home-use device program, the kind of continuity that a documentation-heavy category rewards.

Next step

If you are vetting a contract manufacturer’s documentation capability, put us through the five checks above. Contact our engineers, send the technical detail, and hold our answers against your own regulatory team’s standard. That is the honest way to find out whether the evidence we produce fits the submission you own.