"We have a system — it's a spreadsheet." This is the most common answer when mid-size fabricators and manufacturers are asked how they track incoming mill certificates. And for most shops under 300 active heats per year, it's a defensible answer. Spreadsheets are fast to set up, everyone already knows how to use them, they cost nothing to deploy, and they can be customized to match whatever fields the quality team needs.
The problem isn't that spreadsheets are wrong for this purpose. The problem is that they feel like they're still working long after they've stopped being reliable.
What Works Below the Threshold
A well-maintained spreadsheet for MTC tracking typically includes columns for heat number, supplier, grade, PO number, cert received date, cert file path, and a few key mechanical properties. For a shop running 150–200 heats per year with one or two people maintaining the file, this works. Entries are current, the person who built it knows where everything lives, and lookups are fast enough.
The value is real in this range. The shop has traceability, the cert file path links to the actual document, and auditors can follow the chain. The limitations haven't surfaced yet because the volume hasn't stressed the system.
The Four Spreadsheet Failure Modes
No version control. The master spreadsheet lives on a shared drive. Two people open it simultaneously and make changes. The last save wins. The changes from the earlier session may or may not be captured, depending on who saved last and whether anyone noticed the conflict. In a shop where three or four people access the cert tracker, silent data loss is a regular occurrence — nobody tracks it because nobody knows what they don't know.
No heat-to-document link that survives file moves. The spreadsheet has a column for "cert file path" that points to the PDF location on the shared drive. When the file structure gets reorganized — and it always does, usually annually — every path in the spreadsheet breaks. The cert is still there. The link to it is not. Someone goes through and fixes the critical ones and leaves the rest broken. Over time, the spreadsheet lists heats but the actual certs are findable only through manual folder browsing.
No validation on data entry. The yield strength column accepts any value. A technician entering "36ksi" in one row and "36 ksi" in the next and "36,000 psi" in the third has created three different values for the same measurement. When someone tries to filter or analyze the data, the inconsistencies produce false gaps. The ASTM standard column might have "A36", "ASTM A36", "A36-19", and "A 36" all referring to the same specification. Querying for compliance becomes unreliable.
No audit trail. When an auditor asks who approved heat 44821 and when, the spreadsheet shows the current state of that row — not the history. If the yield strength value was changed after initial entry, the original value is gone. If a cert was added, the date of addition may or may not match the actual receipt date. The spreadsheet documents the current state; it doesn't document what happened.
The 500-Heat Inflection Point
Below roughly 500 active heats, a disciplined team can keep a spreadsheet functional through manual reconciliation. Above it, the maintenance burden exceeds what the team can reliably sustain alongside their other work. Data drift becomes significant. Broken links accumulate faster than they get fixed. The person who knows the spreadsheet's quirks becomes a critical single point of failure — if they leave, the system becomes partially uninterpretable.
The spreadsheet passes internal reviews because the team using it knows how to navigate its limitations. It fails external audits because auditors approach it as a system, not as a workaround maintained by tribal knowledge. The auditor looks for the audit trail that isn't there. They find the broken file paths. They find the inconsistent entries. They write findings that trace back to a document control process that was never designed for this volume.
What the Next Step Looks Like
The transition from spreadsheet to purpose-built system doesn't require a large-scale IT project. The minimum viable change is moving from a spreadsheet where each row represents a heat to a system where each cert PDF is the indexed record.
In a purpose-built system, the cert itself is the primary document. Heat number, grade, and mechanical properties are extracted from the cert and stored as searchable metadata. The audit trail is automatic — every access, every review, every approval creates a timestamped record. File paths don't break because the cert isn't a linked file; it's a stored document.
The team stops maintaining a spreadsheet and starts searching a record system. The work of cert management shifts from data entry and file management to exception handling and quality review — which is what the quality role should be doing.
What to Read Next
- When Your Mill Cert System Costs You More Than the Steel
- MTC Review Should Take Minutes, Not Days — Here's the Gap Most Fabrication Shops Miss
- This Is the MTC Lifecycle — Here's Every Handoff From Mill to End Customer