A QA director at a mid-market supplement manufacturer was describing her team’s actual workload. Not a project. Not a peak. The annual baseline. She did not say it with frustration. She said it the way someone describes the weather.
“It’s pretty manual,” she said. She was not describing the exception. She was describing the industry.
Nobody plans for QA to become document control. It just happens.
Sit across from a QA leader at almost any mid-market food, beverage, or supplement manufacturer right now and the conversation is the same in three minutes. They will tell you about a backlog. They will tell you about an audit they’re behind on. And then, eventually, they will tell you about the file folder.
One QA team we spoke to last week stores roughly 2,500 active supplier documents in SharePoint. Someone has to manually open each one to extract the expiration date and put it in a tracker. They discover expirations by reading documents.
Another holds every incoming raw material in quarantine for 24 to 48 hours so a person can manually match the COA lot number to the inbound truckload before releasing it to production. At 400-plus SKUs, the release queue is a daily traffic jam. “We’re holding production for paperwork,” the QA director said.
A third operator described the document inflow at a high-volume pet food manufacturer with brutal honesty: nine of their suppliers operate their own portals, so a QA person logs into each portal, downloads the documents, copies them to a hard drive, and re-uploads them to the company SharePoint. He called it “moving paper from one shelf to another, every week, by hand.”
QA didn’t choose to be the document control department. They became it because the documents have to live somewhere — and they’re the team that gets the FDA letter when the documents can’t be found.
What it actually costs
This stops being a paperwork problem and starts being a P&L problem the moment you do the math.
Headcount. At minimum, the operators we’re describing burn half a QA FTE on document chasing. The bigger ones burn two to three. At a fully loaded QA cost of roughly $120K, that’s $60K to $360K of payroll per year that does not produce a single audit, root-cause analysis, or recall improvement.
Production delays. When QA holds a load 24 to 48 hours waiting on a COA match, the warehouse is not the cost. The downstream production schedule is.
Missed launches. A bakery operator we spoke to is going to miss a major retailer launch date because R&D couldn’t finalize a clean-label reformulation, which meant procurement couldn’t issue the RFP, which meant QA couldn’t qualify the new supplier. Three teams, blocked in sequence, on a single missing input.
Tariff acceleration. Three of last week’s calls described scrambling to abandon European suppliers on 15–50% cost increases. Every supplier swap is a fresh stack of forty documents. One operator put it plainly: “Every time we switch a supplier we lose two weeks of QA capacity to onboarding paperwork. We’re switching suppliers every month right now.”
Sales blocks. Walmart, Kroger, and Albertsons are already writing FSMA 204 traceability clauses into supplier contracts — ahead of the 2028 enforcement deadline. The documentation pile is no longer a back-office problem. It now blocks shelf placement.
The fix isn’t a better folder.
The QA-as-librarian problem isn’t a tooling problem and it isn’t a hiring problem. You can’t out-hire it — there aren’t enough qualified QA professionals to throw bodies at this, and even if there were, you’d be paying skilled people to do unskilled work in the most regulated link of your supply chain.
It is a coordination problem. Three teams — procurement, QA, R&D — talk to the same suppliers from three separate inboxes with no shared record. When something goes missing, QA inherits the cleanup. The right question is not “how do we make our QA team more efficient at chasing documents?” The right question is “why does QA still own the documents at all, when the people requesting them sit in procurement and R&D?”
The companies that redistribute that load to the workflow itself — pulling cert and COA data out of the email threads where the work already happens, not adding another portal QA has to remember to check — will look structurally more profitable than their peers in the next two years. Nobody outside the operation will quite be able to explain why. That’s how the coordination tax works. It’s invisible until somebody else stops paying it.
Related
Waystation pulls supplier documents out of your inboxes automatically — no portal for QA to check, no spreadsheet to maintain.