Excel vs a Mold Database: The Real Cost of the Mold Folder

Someone asks where mold 447 stands after last week's repair. The answer: a spreadsheet, last touched by the guy who's on vacation, plus a note in a text thread, plus a photo on someone's phone. Twenty minutes later the question is still open. Multiply that by every mold, every week.

The Mold Folder Status Quo

Most shops run on some version of the same system: a shared drive folder, a workbook with a tab per mold or one long sheet, a traveler PDF, and a few photos named things like IMG_2381 FINAL (2).jpg. The custodian knows where everything is. It works, mostly, because it always has.

It also costs hours nobody invoices. The question is where the break-even sits, and it is lower than most owners think.

Where Excel Genuinely Works

Credit where due. A workbook is the right tool under the right conditions:

  • Fewer than ~20 molds. The whole fleet fits on one screen. Nothing gets lost because there's nowhere to lose it.
  • One custodian. One person owns the file, enters everything, and answers every question. Data stays consistent because there's a single pair of hands.
  • Stable, low-churn assets. Molds that sit in a rack and run the same job don't generate much history. The sheet stays current with an hour a month.
  • Simple lookups. "Where is mold 12?" is one Ctrl-F away.

If that describes your shop, keep the spreadsheet. Seriously. The switch is a project, and projects need a payoff.

Where It Breaks Down

Above roughly twenty molds, or the moment the custodian retires, the cracks open:

  • No history per copy. The row says "repaired 2024." What failed, who welded it, how many shots since, and what it cost are all gone. Every similar failure restarts from zero.
  • No photos. A cell can't show the galled parting line or the worn follower. Comparing this month's damage to last year's means digging through folders.
  • No audit trail. Nobody can say who changed what, when, or why. Disputes with customers or the tool room settle on memory.
  • Single-custodian risk. When the one person who understands the tabs and formulas leaves, the file becomes archaeology. This is the same trap as any other tribal knowledge.
  • Revision chaos. MoldRegister_final_v3_JB.xlsx and MoldRegister_FINAL_2.xlsx both exist. Someone updates the wrong one and the truth forks.
  • No structure for what matters. Shot counts, PM intervals, spare parts, location, status. Free text columns can't enforce, sort, or alert on any of it.

None of this is an Excel defect. It's a structural one: a spreadsheet stores rows, not the linked history, media, and accountability a toolroom actually runs on. If you've never laid out what a proper record contains, start with what a mold database actually is.

The Cost-of-Hours Math

Here's a deliberately conservative model for a 40-mold shop. Ten minutes here, fifteen there. The numbers below are hours per month, loaded shop rate $65/hr.

TaskSpreadsheet + foldersMold database
Finding status, location, or history6.0 hrs1.0 hr
Updating records after PM and repairs3.0 hrs1.5 hrs
Re-learning prior failures (repeat diagnosis)4.0 hrs1.0 hr
Audit and customer documentation prep2.0 hrs0.5 hr
Reconciling conflicting copies1.0 hr0 hrs
Monthly total16.0 hrs ($1,040)4.0 hrs ($260)

That's $9,360 a year back in the schedule, from clerical time alone. It excludes scrap from a missed PM, the expedite fee when a repair history is blank, and the down-mold hour spent waiting on a phone call. Those are usually bigger than the clerical line. A typical tool costs more to sit idle for a day than a year of proper records, which is why the biggest number in the table is the one not shown.

When the Switch Pays for Itself

Run the checklist. Two or more yeses and the math is already on your side:

  • More than ~20 molds in the fleet, active or storage
  • More than one person touches the records, or the custodian is a single point of failure
  • Molds generate history: repairs, PM cycles, changes of location, customer moves
  • Anyone has asked "what changed on this mold?" and the answer required a meeting
  • An audit, insurance claim, or customer quality survey is on the calendar

Migration is a day, not a quarter: import the register, attach the photos you have, and let the record build itself from the next repair onward. MoldDB keeps every mold's history, photos, and status in one place that survives vacations, growth, and the day the custodian's last shift ends.

« All articles