5 Signs You've Outgrown Your Shared Drive for MTC Management

The shared drive was set up during a period when the business was smaller, the supplier base was shorter, and one QC manager could hold the filing convention in their head. The folders are organized by year, then by supplier, then by grade — except for the folder from 2021 when someone reorganized by customer for a six-month stretch before reverting. The certs are there. Most of them. If you know where to look.

This arrangement made sense at 30 orders per month from three suppliers at one location. At 150 orders per month from twelve suppliers across three warehouses, with a new aerospace customer requiring a complete cert package on every delivery, it is not a filing system anymore — it is a liability.

The question most operations managers ask is not "should we upgrade?" but "have we actually outgrown the shared drive, or are we just being impatient with a system that works?" These five signs give you a diagnostic answer based on observable operational behavior, not opinions.

Sign 1: Cert Retrieval Takes More Than 20 Minutes Per Order

This is the most reliable operational indicator that your cert management system has become a problem. Time it on your next three orders that require a cert pull. Not the easy ones where the cert was filed yesterday and the supplier is obvious — the ones that arrived three months ago, or sourced from a broker, or split across two heats.

If the process involves opening three different folder paths before finding the right one, sending an email to the supplier asking for a resend because the original is not where it should be, calling a colleague who "might remember where it was filed," or realizing partway through that the cert you found is for the wrong heat and starting over — your retrieval time is not a workflow inefficiency. It is a system problem.

The shared drive does not have a search mechanism that understands heat numbers, PO numbers, and chemistry values as structured data. It is a file system. You can search file names and folder paths. You cannot query it the way you can query a database. When your operation was small enough that every cert arrived with a consistent naming convention from two or three suppliers and one person handled all the filing, the file system was adequate. When you have twelve suppliers with different naming conventions, three filing locations, and variable delivery formats (email PDF, supplier portal download, physical document scanned by receiving), the file system is not the right tool.

Twenty minutes of retrieval labor per order, at 150 orders per month, is 50 hours per month. That is more than a full work week of a quality technician's time spent finding documents that should be instantly accessible.

Sign 2: You've Had a Shipment Hold in the Last 6 Months Due to a Missing or Incorrect Cert

One shipment hold caused by cert issues is a data point. Two in the same year is a pattern. The shared drive is not catching deviations before they reach your customer or your dock, and the cost of each hold is large enough that the frequency of occurrence matters.

A shipment hold triggered by a cert problem — the cert is missing and cannot be located before the customer's receiving window closes, or the cert on file shows values that do not comply with the customer's specification — carries direct costs that accumulate quickly. Return freight runs $500 to $2,000 depending on the shipment. Emergency re-procurement on short notice adds 15 to 30 percent to material cost. Schedule disruption at the customer's facility may generate a claim. Your own receiving and QC team spends two to four hours managing the exception. When the full cost is added up, a single shipment hold attributable to cert management failure typically lands between $5,000 and $15,000 for a mid-size operation.

The shared drive cannot catch a deviation before the material ships because it has no mechanism for comparing cert data against specification requirements. It stores files. Whether those files contain values that comply with the PO spec is something a human has to check — if they check at all, if they know what the spec says, and if they can locate the correct cert before the truck is loaded.

If you have had one hold in the last six months, you have confirmed that your current system does not prevent this category of failure. The question is whether you want to wait for the second.

Sign 3: You Process Material from More Than 2 Locations or 3 Suppliers

The shared drive assumes a single operating environment: one filing location, one naming convention, one person responsible for cert intake. Every additional location and every additional supplier adds compounding complexity that the file system cannot accommodate structurally.

When material moves from a primary warehouse to a secondary processing location, the cert needs to follow it — or at minimum, be accessible from both points. In a shared drive setup, this requires deliberate action: copying the file, updating a reference document, or relying on people at both locations to know which folder path to check. In practice, when material is moved without an explicit cert handoff, the cert stays associated with the receiving location and the processing location has no way to access it without a phone call or email.

Multiple suppliers means multiple naming conventions, multiple document formats, and multiple delivery methods. One supplier sends PDFs named by heat number. Another sends PDFs named by their internal order number. A third uploads to a supplier portal that requires a login to access and a manual download to file. A fourth sends physical documents with the truck that get scanned at receiving and land in an email inbox as "scan_20240912_094312.pdf." Filing these consistently into a shared drive requires active effort and a documented convention that everyone follows. As soon as one person deviates from the convention — because they were busy, because the file did not fit the naming pattern, because they were new — the filing system degrades.

Three or more suppliers is the threshold where the shared drive's structural limitations become operationally significant. At twelve suppliers across three locations, those limitations are active problems on a weekly basis.

Sign 4: You Have a Customer Who Requires Cert Packages with Every Delivery

Aerospace, defense, Tier 1 automotive, nuclear, and pressure vessel customers — operating under AS9100 Rev D, NADCAP, IATF 16949, or NQA-1 quality management requirements — share a common requirement: complete, traceable mill cert packages on every delivery, organized in a format that can be audited. These customers do not accept verbal confirmation. They do not accept "we can find it if you give us a few days." They audit your cert management practices as part of their supplier qualification process.

A shared drive answer to a supplier audit is: "Our certs are filed in a shared folder organized by year and supplier. We can locate any cert if you give us the heat number or PO number." The auditor will then request three or four specific certs at random, time how long it takes you to produce them, and ask you to demonstrate how your system prevents non-conforming material from shipping without detection.

The shared drive cannot answer the prevention question. It is a passive filing system. Non-conforming material ships undetected when the cert was not reviewed before dispatch, when the cert was reviewed but the reviewer did not catch the deviation, or when the cert for the wrong heat was pulled and no one compared it to the actual material. None of these failure modes are visible in a shared drive audit because the drive does not record what was checked, when, by whom, or what the result was.

Aerospace and defense customers have pulled supplier qualification for cert management practices that cannot demonstrate systematic control. If you have one of these customers now, or are pursuing one, your cert management infrastructure needs to demonstrate process control — not just document storage.

Sign 5: Your QC Person Is the Only One Who Can Find Anything

Single-person dependency on institutional knowledge is a business risk that most operations underestimate until it materializes. When your QC manager takes two weeks of vacation, who pulls the cert for the emergency order that comes in on day three? When your quality technician leaves for a better offer, how long does it take the replacement to learn the filing system well enough to retrieve certs accurately under time pressure?

The shared drive externalizes knowledge management into the people who use it, not into the system itself. The system stores files. The knowledge — where to find a specific cert, what the naming convention means, which folder the 2022 material went into before the reorganization, which supplier portal requires which login — lives in the person who has been managing the system. When that person is unavailable, the system effectively goes offline.

This is not a hypothetical risk. Every steel service center and fabrication shop that has experienced a key QC departure knows exactly how much undocumented institutional knowledge walked out the door. The shared drive looks like it contains the information. What it does not contain is the retrieval logic — the mental model that makes the filing system navigable. That logic is in the person, not the system.

A purpose-built MTC management system stores both the certs and the structured data associated with them: heat number, PO number, grade, chemistry values, mechanical properties, customer, supplier, date received, compliance status. Anyone with access can retrieve any cert by any of those parameters in seconds, without knowing which folder it is in or remembering the naming convention from 2019.

If Three or More of These Apply

The five signs above are each individually sufficient to justify moving to a dedicated MTC management system. Three or more occurring simultaneously means you are actively absorbing costs — in retrieval labor, in shipment holds, in audit preparation, in customer relationship risk — that a modern system eliminates.

The transition from a shared drive to MTC software is not a large infrastructure project. The primary work is importing historical cert data, setting up supplier and customer profiles with their respective specification requirements, and establishing the intake workflow for new certs. Most operations reach steady-state on a new system within 30 to 60 days.

The cost of staying on the shared drive is not visible in any single line item. It is distributed across salaries, freight variances, QC overtime, and occasional customer claims. The cost of moving to a dedicated system is specific and bounded. That asymmetry — distributed invisible cost versus specific visible cost — is why most operations delay the switch longer than they should.

If your QC manager is the institutional memory for your cert filing system, your next shipment hold is a question of when, not if. The shared drive is not going to tell you when.

Frequently Asked Questions