Brewery operations are the sequence of steps that turn grain, water, hops, and yeast into finished, packaged beer: milling and mashing, lautering, boiling, fermentation, conditioning, and packaging. Running them well means holding recipe consistency batch to batch, controlling loss at every transfer, and keeping the records that federal law and customers demand.
That definition hides the hard part. Beer is a biological product made on mechanical equipment, so two batches brewed to the same recipe can finish differently if a mash temperature drifts, a fermentation runs warm, or a transfer leaves too much beer behind. The brewers who scale without losing their flavor do it by treating the brewhouse and cellar as a measured process, not a craft they re-improvise every week. This guide walks the flow, shows where floor data tightens consistency and cuts loss, and covers the compliance records that come with making an alcoholic beverage in the United States.
For the systems view of connecting the whole floor, see what is a manufacturing operating system.
What are the main stages of brewery operations?
There are seven: milling, mashing, lautering, boiling and whirlpool, fermentation, conditioning, and packaging. Grain is cracked and mixed with hot water to convert starch to sugar, the sweet wort is separated and boiled with hops, then cooled and pitched with yeast to ferment. After conditioning, the beer is filtered, carbonated, and packaged into cans, bottles, or kegs.
Each stage hands off to the next through a transfer, and each transfer is where beer and data both leak. Wort left in the kettle, trub dropped after whirlpool, yeast and hop material pulled with the beer at the end of fermentation, and foam or heel loss at the filler all subtract from the pints you can sell. The industry tracks this as brewhouse yield and packaging loss and the difference between a tight operation and a leaky one is measured in points of loss on every batch. This is the same discipline as batch production anywhere: a repeatable recipe, executed the same way, measured the same way, every run.
Why is batch-to-batch consistency so hard in a brewery?
Because beer is fermented by living yeast on equipment that varies with the weather, the water, and the operator. Small drifts compound: a mash a couple of degrees off changes fermentability, a fermentation that runs warm throws off flavor, and a slightly different pitch rate shifts attenuation. None of it shows up until the beer is finished and, too often, already packaged.
The fix is not more talent; it is capturing the numbers that define a good batch and comparing every run against them. Original gravity, mash and knockout temperatures, pitch rate, fermentation temperature curves, final gravity, dissolved oxygen at packaging, and carbonation are the vital signs of a beer. When those live in a brewer's notebook or a cellar whiteboard, nobody can see a drift until it becomes a complaint. When they are captured as the batch runs and trended over time, an out-of-range mash or a stalling fermentation is caught while it can still be corrected. That is the plainest version of what floor data does for a brewery: it turns "the beer tasted off this week" into "batch 412 fermented three degrees warm on day two."
Where does yield loss hide, and how do you find it?
Yield loss hides in the gaps between measurements: wort left behind, beer pulled with the yeast, and product lost at the filler. You find it by measuring volume and gravity at each transfer and reconciling what went in against what came out, batch after batch, until the leaky steps stand out.
Most breweries can tell you their recipe but not their true yield, because the losses are spread across steps that nobody meters. A brewery that starts tracking volume at knockout, at the end of fermentation, and at packaging usually finds a step or two quietly eating several percent of every batch, often filler heel loss or over-aggressive yeast dumps. Those points of yield are pure margin: the ingredients, labor, and energy are already spent, so recovering the beer costs almost nothing. Attacking loss deliberately is the brewery version of lean manufacturing and it starts with honest numbers rather than a gut feel about which batches "ran short."
How do downtime and changeovers affect a brewery?
They set your real capacity. A brewhouse can only start a new batch when the last one has cleared the vessel, so cellar tank availability, clean-in-place cycles, and packaging-line stoppages decide how many batches a week you can actually run, usually far below the number the equipment could theoretically do.
Packaging is where this bites hardest. Canning and bottling lines stop constantly for small reasons: a jam, a low-can fault, a seamer adjustment, a label misfeed. Individually they are seconds; added up across a shift they are the difference between finishing the run and paying overtime. The only way to fix them is to see them, which is why breweries that get serious about output start by tracking machine downtime on the packaging line and measuring true line performance with OEE. Changeovers between products and package formats matter too, every switch from one beer or can size to the next is lost production time, and the bottling and canning line is usually the plant constraint. Cleaning cycles deserve the same scrutiny; a clean-in-place program that is timed and verified beats one that runs "until it looks done."
What records does a US brewery have to keep?
Every brewery that makes beer for sale operates under federal supervision. In the United States the Alcohol and Tobacco Tax and Trade Bureau (TTB) requires a brewer to qualify before producing, maintain a bond, and file regular reports of operations and excise tax, all traceable back to what was actually brewed, transferred, and removed.
The core operational record is the Brewer's Report of Operations (TTB Form 5130.9), which accounts for beer produced, on hand, transferred, and removed for consumption or sale. Excise tax is owed on beer removed from the brewery, so your production and removal records are not just operational hygiene, they are the basis of a federal tax return. This is where sloppy floor records become expensive: if your cellar log, packaging counts, and shipping records do not reconcile, reconstructing the truth at reporting time is slow and error-prone. Traceability of raw materials and lots also matters for recalls and for the traceability expectations that retailers increasingly place on suppliers. Good brewery software does not replace TTB discipline; it makes the numbers add up automatically because they were captured as the work happened.
How do you digitize a brewery floor without ripping anything out?
The goal is one connected record of every batch, brewhouse to package, built from the equipment and people you already have. You do not need to replace tanks, the brewhouse control system, or your accounting software. You need to capture the vital numbers at the source and put them in one place. Here is a practical sequence.
- Define the recipe targets that matter. For each beer, write down the target original gravity, mash and knockout temps, pitch rate, fermentation profile, final gravity, and packaging DO and carbonation. These become the yardstick every batch is measured against.
- Capture the numbers as the batch runs. Record gravities, temperatures, volumes, and times at each stage when they happen, not from memory at end of shift. Live capture is what makes a drift visible in time to fix it.
- Meter the transfers to find loss. Measure volume at knockout, at the end of fermentation, and at packaging, and reconcile them. The steps that don't add up are your hidden yield loss.
- Track packaging-line downtime and changeovers. Log every stoppage and every product or format switch so you can see, in numbers, where the shift really went.
- Build the compliance record as a byproduct. Tie production, transfer, and removal counts to the batch so the Brewer's Report of Operations and excise numbers assemble themselves instead of being rebuilt from scraps.
- Standardize CIP and sanitation. Make cleaning a timed, verified, recorded step. In a fermented product, sanitation is quality, not overhead.
None of that requires a rip-and-replace. It requires connecting what exists so the batch record, the yield numbers, the downtime, and the compliance data live together instead of scattered across notebooks and spreadsheets (how Harmony connects the floor).
What do the numbers and rules say?
- A US brewer must qualify with TTB before producing beer for sale, hold a bond, and account for operations, the requirements sit in 27 CFR Part 25 (TTB).
- Breweries report production, inventory, and removals on the Brewer's Report of Operations, TTB Form 5130.9 and excise tax is owed on beer removed from the brewery (TTB).
- The US had roughly 9,600 operating craft breweries in 2024 which produced about 23.1 million barrels a high-mix, competitive market where consistency and cost control decide who survives (Brewers Association).
- Beer sanitation and process control fall under FDA food-safety authority for facilities, on top of TTB's alcohol rules (FDA).
Where does an operational layer fit in a brewery?
In the gap between the tanks and the paperwork. Breweries rarely lack good recipes or skilled brewers; they lose margin to yield they can't see, consistency they can't prove, and reports they rebuild by hand. An operational layer that captures batch parameters, meters transfers, tracks packaging downtime, and assembles the compliance record as the work happens turns all of that from an after-the-fact scramble into a byproduct of brewing. It connects the equipment, cellar, and packaging line you already run, the same pattern behind any real-time operational platform, as CLS proved when it replaced paper logging with live capture (the CLS case study). For the broader picture, see what is a manufacturing operating system and the maintenance side in beverage plant maintenance.