Key Takeaways
- Uncover hidden maintenance gaps because many acquisitions overlook critical maintenance history, equipment compatibility, and vendor relationships, leading to costly surprises post-merger.
- Identify four key blind spots that recognize and address the recurring issues of absent maintenance history, undocumented equipment incompatibilities, invisible vendor relationships, and unstandardized process standards.
- Implement a 90-day integration plan that follows a structured approach for the first three months post-acquisition to build a complete picture, identify and quantify risks, and establish a single source of truth for unified operations.
In Part 1 of this series, we revealed how maintenance blind spots cost one newly consolidated brewery—not from aging equipment or deferred repairs, but from overlooking maintenance (or lack thereof). The uncomfortable truth is that most of it was entirely preventable if the right questions had been asked before the deal closed.
Acquisition due diligence in craft brewing tends to fixate on what’s easy to see, such as brand equity, tap-handle presence, distribution territory, and production capacity.
Meanwhile, maintenance history, equipment compatibility, vendor contracts, and process documentation are treated as “if we get to it” items. By the time operations teams inherit the brewery, the costs are already embedded.
This is the gap that head brewers, directors of brewery operations, and maintenance staff are left to close—usually under pressure and without a roadmap.
The Four Blind Spots That Surface Every Time
Across multisite brewery operations, four due-diligence gaps appear repeatedly. Recognizing them early is the difference between a smooth integration and a costly one.
1. No Maintenance History, No Baseline
When a brewery’s maintenance knowledge lives in one person’s head—or in a handwritten log that hasn’t been touched in months—you have no baseline. You don’t know when critical equipment was last serviced, whether preventive-maintenance schedules were being followed, or who to call for what. Without that foundation, your team is flying blind from Day One.
As we explained in Part 1, for one brewery, a 450-hour preventive-maintenance (PM) task was skipped for one reason: no one knew it existed. Six incidents and $23,000 later, they found the gap.
2. Undocumented Equipment Incompatibilities
Breweries are built incrementally—a fermentor here, a chiller upgrade there, and a secondhand canning line from a brewery that closed two towns over. The result is a patchwork of brands, vintages, and specifications that works fine in isolation—until you’re looking for opportunities to scale and standardize.
Incompatible glycol chiller systems mean you can’t share backup capacity during downtime. Mismatched gasket and seal specifications result in duplicate spare-parts inventory that can’t be consolidated. What should be an hour-long equipment fix can stretch into days of lost production and lost revenue.
3. Invisible Vendor Relationships
Every brewery runs on a web of vendor relationships: glycol service contractors, HVAC providers, CO2 suppliers, chemical vendors, and equipment service agreements. These relationships are often informal, undocumented, and built on years of handshake deals.
When ownership changes, the agreements don’t automatically transfer. And, when agreements are renegotiated separately at each location, you lose the volume leverage that consolidation was supposed to create.
As we outlined in Part 1, fragmented vendor relationships easily cost one brewery $17,000 annually in lost volume discounts on service contracts alone. Add chemical supply, equipment servicing, and more, and that number climbs fast.
4. Assumed Process Standards
Two breweries can accomplish the same task—such as a clean-in-place (CIP) cycle, a tank inspection, a yeast pitch—in completely different ways. For example, Raleigh might run CIP for 45 minutes at 180°F (82°C) while Chapel Hill runs 90 minutes at 165°F (74°C). Both get the job done, but neither team knows what the other is doing, and nobody has documented which approach is better.
Without a structured standardization process, both methods persist indefinitely. The inefficiencies compound. And in the worst cases, inconsistent CIP procedures don’t just cost money—they create quality headaches.
Your First 90 Days: See Everything, Assume Nothing
Due-diligence gaps don’t close themselves after the deal is signed. The first 90 days post-acquisition are your window to surface what wasn’t visible before closing and begin building toward a unified operation.
Days 1–30: Build a Complete Picture
Walk every inch of the acquired facility with your maintenance lead. Document every major asset: make, model, age, last service date, and known issues. Collect all existing maintenance records—whether digital, paper, or scrawled on a whiteboard. Identify who holds institutional knowledge and capture it before they walk out the door. Catalog spare-parts inventory at both facilities and flag redundancies immediately.
The driving question: What do we actually have, and what do we actually know about it?
Days 31–60: Find the Gaps and Quantify the Risk
Compare PM schedules across both facilities. Identify critical assets with no documented service history. Map process differences—CIP cycles, chemical programs, and inspection intervals. Flag equipment incompatibilities that limit shared capacity options. Then put a number on it. Use the cost framework from Part 1 as your guide. Fragmentation has a price, and quantifying it is what turns a maintenance conversation into a business case.
The driving question: Where are we bleeding money and reliability—and how much is it actually costing us?
Days 61–90: Start Building a Single Source of Truth
Begin centralizing asset documentation in a single shared system accessible to both facilities. Draft a unified PM schedule for critical assets. Start standardizing your most-used spare parts across locations. Initiate vendor consolidation conversations where contract timing allows. Define roles clearly—who owns maintenance decisions at each site, and how do they coordinate?
The driving question: What does “one team, two locations” actually look like in practice?
Bringing It to Life: Lessons from the Brewery
The framework above is only as valuable as the real-world experience behind it. That’s why we’re taking this conversation directly to the people living it.
Join us for an upcoming webinar featuring Highland Brewing Co.’s director of brewery operations and production maintenance team as they share firsthand how Highland has navigated scaling complexity, built operational consistency, and used asset-management tools to scale and sustain success.
This is a maintenance discussion among practitioners, for practitioners. If you’re a head brewer, director of operations, or part of a maintenance team managing multiple facilities, this one is built for you.