← Back to Field Notes

August 29, 2025 · The Bloomfield Team

The 7 Most Common ERP Workarounds in Manufacturing

Every manufacturing ERP has a gap between what it was designed to do and what the operation actually needs. Those gaps are not empty. They are filled with spreadsheets, whiteboards, email chains, shared drives, sticky notes, and the personal systems that individual employees build to do their jobs. These workarounds are so universal that they have become invisible. The operation runs on them. Nobody talks about them.

A 2024 study by Panorama Consulting Group found that 73% of manufacturers use at least four workaround systems alongside their ERP. The average across all respondents was 6.3 parallel systems. Each one represents a place where the ERP fell short and a person built something to fill the gap. Each one also represents a place where data, knowledge, or workflow exists outside the system of record, invisible to anyone who was not the person who built the workaround.

Here are the seven we see most often.

1. The Scheduling Spreadsheet

The ERP has a scheduling module. The production scheduler does not use it. They maintain a spreadsheet, usually in Excel, with a custom layout that mirrors how they think about the floor: machine groups across the top, days down the side, color-coded by priority. The spreadsheet is faster to update than the ERP module, more visual, and organized around the actual decisions the scheduler makes rather than the data structure the ERP imposed.

The cost: the schedule exists in one place, accessible to one person. When the scheduler is absent, nobody can read it. When a rush order arrives after hours, the night shift has no visibility into tomorrow's priorities. Scheduling by gut feel compounds when the tool that holds the plan is a personal spreadsheet rather than a shared system.

2. The Quoting Calculator

The estimator built their own quoting spreadsheet years ago. It has tabs for material cost, machine rates, setup time, markup percentages, and customer-specific pricing adjustments. It works beautifully for the person who built it. Nobody else can fully understand it because the formulas reference cells with no labels, the logic branches are in the estimator's head, and half the inputs come from memory rather than current data.

The cost: quoting knowledge concentrates in one person, pricing logic is opaque, and the process cannot scale beyond the capacity of the individual who maintains the sheet. When that person leaves, the calculator leaves with them, or worse, stays behind as a formula-laden artifact that the next estimator does not trust enough to use.

3. The Material Tracking Email Chain

The ERP tracks material inventory. The purchasing manager tracks actual availability through a running email chain with three key suppliers. The ERP says 200 feet of 6061-T6 in 2" round bar is in stock. The purchasing manager knows that 120 feet of that is already committed to jobs on the floor that have not been issued yet, and the remaining 80 feet has a quality hold because the last batch from that supplier was out of spec on hardness.

The cost: the ERP shows a number. The reality is in someone's inbox. Any decision made based on the ERP number without checking the email chain is working with wrong information. This is one of the most common places where the ERP fails to reflect operational reality.

4. The Quality Notes Binder

The ERP stores inspection data: pass/fail, dimensions measured, NCR numbers. The quality manager keeps a binder, sometimes a notebook, with the context behind the data. Why that NCR happened. What the customer said during the call about the rejected parts. Which operator tends to have trouble with that particular dimension. What the root cause was and what was changed. The ERP has the record. The binder has the story.

The cost: the story is what prevents the problem from recurring, and it lives in a physical notebook that one person maintains. When a similar quality issue appears 18 months later, the binder is the only path to the answer, assuming the quality manager remembers it is there and can find the relevant page.

5. The Whiteboard Production Status

The foreman maintains a whiteboard on the shop floor with the current status of every active job: machine assignment, operator, expected completion, and notes. The whiteboard is updated two to three times per shift by hand. It is the most-referenced information source on the floor. The ERP's production status screen, which requires logging into a terminal and navigating three menus, is not.

The cost: the whiteboard is always slightly out of date, is not visible from the front office, cannot be accessed remotely, and contains no historical record. When a customer calls asking about a delivery date, the sales team cannot check the whiteboard. They call the foreman, who is standing in front of it.

6. The Shared Drive of Customer Specifications

Customer specs, drawings, email clarifications, and change orders accumulate in a shared network drive organized by customer folder and then by part number, except for the 30% of files that are organized differently because three different people maintain it. The ERP links to purchase orders and work orders but does not store or retrieve the actual specifications and clarifications that govern how the work gets done.

The cost: the estimator, the programmer, and the operator all need access to the spec, the revision history, and the informal clarifications that came through email. Finding the right version of the right document takes an average of 8 to 12 minutes per job. Across 200 active jobs per month, that is 26 to 40 hours of skilled labor spent navigating a filing system that was never designed for the purpose.

7. The Tribal Knowledge Network

The most pervasive workaround is not a tool at all. It is the informal network of people asking other people things the ERP should know but does not. How did we run this part last time. What is the current lead time from that supplier. Did we have problems with this material before. Is this customer's PO still active. Each question pulls an experienced person off their work to serve as a human database for someone else.

The cost: every interruption averages 14 minutes when you include the question, the search for the answer, the response, and the context switch for both people. In a 50-person shop, this happens dozens of times per day. The total time consumed by the tribal knowledge network easily exceeds 200 hours per month across the operation.

For a complete look at how ERP data can be made more useful, see our guide to ERP and AI integration.

What the Workarounds Tell You

Each of these seven workarounds exists because someone needed to do their job and the ERP did not support how they actually do it. The workarounds are not failures. They are evidence of what the operation actually needs: faster access to the right information, in the right format, at the moment it matters. The ERP provides a foundation of transactional data. The workarounds fill the gap between that foundation and the real-time, contextual, judgment-intensive work that manufacturing operations run on.

Custom AI tools can close that gap by connecting the ERP data to the workaround data, structuring both, and delivering the combined picture to the person who needs it at the point of decision. The spreadsheet that runs your shop exists because the system that should run it does not yet. Building that system is now a solvable problem, and the operations that solve it first will run on knowledge instead of workarounds.