FDA Documentation Support From Your Manufacturer

Who holds the submission, and who holds the evidence

There’s a misunderstanding that keeps coming up in device sourcing, and it costs brands time. Occasionally it costs them a rejected filing. It’s the belief that a contract manufacturer can “handle the FDA” for you. It can’t, 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: produce the technical evidence the submission rests on.

That distinction isn’t fine print. It’s the operating boundary of the whole relationship, and sorting it out 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 check a manufacturer’s documentation capability before it becomes 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: device classification, the regulatory pathway (for a US device that might 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’s the brand and its regulatory consultants. You can’t delegate it to a factory, because the factory doesn’t own the claims.

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

The two stacks connect at one seam: the manufacturer hands its evidence to the brand’s regulatory team, which assembles and files. Get that seam written clearly into the contract and most of the downstream friction goes away.

What “documentation and testing support” actually includes

When a manufacturer offers documentation and testing support, that phrase should break down 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. Where the manufacturer also does design work, this is the design-history evidence; for build-to-print, it’s the incoming design under revision control.
• Test reports. Results against the safety and electromagnetic-compatibility standards your target markets require (the IEC 60601 family for medical electrical equipment; EMC and hazardous-substance testing for the electronics), plus coordination with the third-party test labs that issue them.
• Production records. The batch or device records that prove each unit was built to its specification. This is 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 a change made after the submission doesn’t quietly invalidate the evidence it was based on.

Notice what’s not on that list: writing the submission, corresponding with the agency, or holding any registration or clearance. Those belong to the brand. The manufacturer pours the foundation; it doesn’t 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

Your 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 can’t produce this set on request for an existing program, you can treat that as your answer for whether it’ll produce it for yours.

The quality system underneath it all

A mature manufacturer produces this evidence routinely because its quality system is built to. ISO 13485:2016 is the medical-device quality management standard, and what it requires (design controls, traceability, records of production, corrective and preventive action) is exactly 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. For a buyer, the convergence is the useful part: a manufacturer running a genuine ISO 13485 system is already producing evidence in the shape US expectations require.

That’s why you audit the quality system, not the sales pitch. For how to verify one rather than just 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. It’s also easy to check. Do the checking before the contract, not in the middle of 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 hand them over; one that promises to “put it together later” is describing a system that doesn’t exist yet.
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 will work 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 ask 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 all five, its documentation and testing support is real. If it deflects on any of them, you’ve found out cheaply.

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

It can feel reassuring when a manufacturer says it’ll “take care of the FDA.” It should do the opposite. A manufacturer that offers to make your submission either misunderstands the regulatory structure or is misrepresenting it, and either way you should walk. The submission carries the claims, and the claims carry the liability. Both belong to the brand. The 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 don’t make the submission, and we shouldn’t be described as holding any approval or clearance. That’s not a limitation; it’s the correct division of labor. A manufacturer that says 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 at a single site. We provide the 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. Our compliance experience covers CE, FCC, RoHS, and PSE. We don’t 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, and that’s the kind of continuity a documentation-heavy category rewards.

Next step

If you’re 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’s the honest way to find out whether the evidence we produce fits the submission you own.