Batch 112 of your flagship IPA scored perfectly with the tasting panel. Batch 118 used the same recipe, the same malt lot, and the same crew, but it came back thin with a faint buttery note. Nobody can say exactly what changed, because nobody recorded it in a way you can compare side by side. A well-built brewery quality control checklist fixes that problem. The key is to organize it around the way beer actually moves through your building: brewhouse, fermenter, brite tank, then package.
This guide is for owners, head brewers, and operations leads who want consistency without adding a layer of bureaucracy. You'll learn how to split QC into phase-based checklists, how to write cellar SOPs that survive shift changes, and how to adjust both for non-alcoholic and low-ABV beer, where the margin for error is much thinner. If you already run scheduling and batch records in brewery management software, these checklists can become part of each batch's traceable record instead of sitting on a clipboard that gets coffee spilled on it.
Why Phase-Based QC Beats One Giant Checklist
Most breweries start with one long QC document. It usually began as a whiteboard list or a spreadsheet tab, and over the years it grew to 60 lines. Nobody reads it top to bottom, and half the checks happen days apart in different parts of the building. Brewers skip lines that don't apply to them. Cellar staff assume someone else covered the brewhouse items. When a batch goes sideways, you can't tell which step was missed or who missed it.
Phase-based checklists solve this by matching the checks to the moment the work happens. The brewer on the hot side sees only hot-side checks. The cellar team sees fermentation and conditioning checks tied to a specific tank. Packaging sees fill levels, dissolved oxygen, and seal checks. Each list is short enough to finish and specific enough to own.
There are three practical benefits for business leaders:
- Clear ownership. Every check has one phase and one responsible role. When pH is out of spec on day three, you know it's a cellar issue, not a brewhouse mystery.
- Better timing. Checks fire when the beer reaches a phase, not when someone remembers. A gravity reading taken a day late can hide a stalled fermentation.
- Comparable data. When the same checks happen at the same phase for every batch, you can line up batch 112 and batch 118 and spot the difference in minutes.
Here's how a typical split looks for a production brewery:
PhaseTypical OwnerTriggerCore ChecksBrewhouse (BH)Brewer on shiftBrew day startsMash temp, mash pH, pre-boil and original gravity, knockout temp, wort volumeFermenter (FV)Cellar leadKnockout to FVPitch temp, daily gravity and temp, pH, diacetyl check, terminal gravityBrite Tank (BT)Cellar or QATransfer to BTCarbonation, dissolved oxygen, clarity, sensory, micro platingPackagingPackaging leadPackage run startsPackage DO, fill level, seal integrity, date codes, retained samples
Picture a 15-barrel brewery running two brew shifts and one cellar shift. Under the old single-list system, the night brewer filled in mash data, then left the rest blank. The morning cellar tech saw a half-finished sheet and wasn't sure whether the fermenter had been oxygenated. After switching to phase lists, the brewhouse list closed out at knockout with a sign-off, and a fresh fermenter list opened automatically for that tank. The handoff question disappeared, because the answer was built into the structure.
Phase-based QC also scales better. When you add a new fermenter or a second brite tank, you don't rewrite the whole document. You assign the existing phase checklist to the new tank. When you introduce a new beer style, you attach the standard phase lists and add only the style-specific checks, like a dry hop addition for a hazy IPA or a lagering temperature drop for a pilsner.
One caution: phase lists only work if the phases match your real process. If you transfer directly from fermenter to package for certain beers, don't force a brite tank phase onto them. Map your actual flow first, then build the lists around it.
Takeaway: Before you write a single check, sketch your production flow for each beer style. Mark every point where the beer changes vessel or ownership. Each of those points is the start of a new checklist.
How to Build a Brewery Quality Control Checklist for Each Phase
A good checklist item has three parts: what to measure, the target range, and what to do if it's out of range. "Check mash pH" is a reminder. "Mash pH 5.2 to 5.6 at mash temperature, recheck after 10 minutes, notify head brewer if outside range" is a control. The difference is the second version tells a new hire exactly what passing looks like.
Start with your brewhouse, since every problem downstream is cheaper to catch there.
Phase 1: Brewhouse Checks
Your brewhouse list should capture everything that sets the batch's starting point. Typical items include:
- Strike water volume and temperature recorded
- Mash temperature within recipe range (for example, 65 to 67°C for a balanced ale)
- Mash pH within target range, typically 5.2 to 5.6
- Pre-boil gravity and volume recorded
- Hop additions logged with lot numbers and times
- Original gravity within recipe tolerance
- Knockout temperature matches yeast pitch target
- Wort oxygenation completed and duration logged
Lot numbers matter more than most teams realize. If a hop lot produces unusual flavors, you'll want to find every batch that used it. Tying raw materials to batches is much easier when your stock is already organized, and this guide on setting up inventory tracking systems for your brewery walks through that foundation.
Phase 2: Fermenter Checks
Fermentation is where most consistency problems show up, because it runs for days and crosses multiple shifts. Build the fermenter list as a repeating daily check plus milestone checks:
- 1At pitch: yeast generation, pitch rate, pitch temperature, and yeast lot recorded.
- 2Daily: gravity, temperature, and pH. Note any temperature controller alarms.
- 3Near terminal: a forced diacetyl test or sensory check before cooling. That buttery note in batch 118 is often diacetyl that wasn't cleaned up before crash.
- 4Terminal gravity confirmed: the same reading on two consecutive days, not one.
- 5Dry hop or additions: timing, weight, and lot numbers.
- 6Yeast harvest: viability or cell count if you repitch.
Phase 3: Brite Tank and Packaging Checks
This is your last chance to catch a problem before customers do. Focus on carbonation, oxygen, clarity, and a sensory sign-off:
- Carbonation in volumes of CO2 within spec for the style
- Dissolved oxygen in the brite tank and in finished packages. Many craft brewers aim for packaged DO well under 50 ppb, with tighter targets for hop-forward beers
- Clarity or turbidity reading, if the style calls for it
- Sensory panel pass, with at least two tasters signing
- Micro plating samples pulled and logged
- Fill levels, seal checks, and date codes verified at the start, middle, and end of each run
- Retained samples stored and labeled
Notice how each phase ends with a clear sign-off. That sign-off is the gate. A fermenter shouldn't transfer to a brite tank until the fermenter list is complete, and a brite tank shouldn't package until its list passes.
The hardest part for most teams is the data, not the list. When readings live in notebooks, nobody trends them. BrewPlanner lets you attach brewing, fermenting, and packaging task checklists to each beer style, so every new order inherits the right checks automatically. QA checkpoints like DO, pH, gravity, and sensory get logged against the batch, which means you can compare batches without hunting through paper.
Takeaway: Rewrite every vague check as measurement plus target range plus out-of-spec action. Then add a sign-off gate at the end of each phase.
Writing Cellar SOPs That Hold Up Across Shifts
Checklists tell people what to verify. Standard operating procedures tell them how to do the work that gets checked. A checklist line might say "Transfer to BT, DO pickup under target." The SOP explains how to purge the hose, how to set up the transfer, and what to do if the DO meter spikes halfway through.
Cellar work is where SOPs earn their keep. It's repetitive, it happens across shifts, and small differences in technique add up. One tech purges the brite tank for five minutes and another for two. One sanitizes the sample port before every pull and another does it once a day. Those differences show up as batch-to-batch variation that no checklist will explain.
A solid cellar SOP has a predictable structure. Here's a template you can adapt:
Keep each SOP to one task. "Cellar Operations" isn't an SOP, it's a binder. "Fermenter to Brite Tank Transfer" is something a person can actually follow on a busy Tuesday.
Shift handoffs deserve their own attention. Most cellar mistakes happen at the boundary between people, not in the middle of someone's shift. A few habits help:
- Open items carry forward. If a check is incomplete at shift end, it stays visible to the next shift as an open task, not buried in yesterday's notes.
- Notes stay with the batch. A note like "FV3 running warm, watch for diacetyl" belongs on the batch record for FV3, not in a group text.
- One escalation path. Every SOP should name who to call when something is out of spec. If the answer is "whoever's around," problems get solved inconsistently.
Adoption is the real challenge. You can write perfect SOPs and still have staff work around them if the documents feel disconnected from the actual job. Involve the people doing the work in writing the procedures, test each draft on a real shift, and revise based on what they tell you. For a deeper look at getting buy-in, this piece on building brewery SOPs and quality checklists your team will follow covers rollout and training in detail.
Review SOPs on a set rhythm, perhaps every six months, and after any major process change or quality incident. Version each one so you can see what changed and when. An SOP that still references a pump you replaced two years ago tells staff the documents don't matter.
Consider a regional brewery that kept seeing DO pickup vary widely across transfers. Their checklist caught the high readings, but the root cause was technique. After writing a single transfer SOP with a defined purge duration and three DO check points, their readings tightened, and the night shift no longer produced noticeably different results from the day shift. The checklist found the problem. The SOP fixed it.
Takeaway: Pair every critical checklist item with a one-task SOP. Name an owner, an acceptance range, and an escalation path, and make sure open items carry across shifts.
Adapting QC for Non-Alcoholic and Low-ABV Beer
Non-alcoholic and low-ABV beers look like a simple extension of your lineup. From a quality standpoint, they're a different product category. Alcohol and hop compounds help protect standard beer from spoilage. Remove most of the alcohol, leave more residual sugar, and you've created a far more welcoming environment for microbes. That changes how strict your QC needs to be.
The production method shapes your risk profile. Breweries generally make NA and low-ABV beer through limited fermentation with specialized yeast strains, arrested or interrupted fermentation, or dealcoholization of a fully fermented beer. Each method needs its own phase checks, but several controls apply across all of them.
CheckStandard BeerNA and Low-ABV BeerABV verificationConfirm near recipe targetConfirm below your legal threshold for every batch, often 0.5% ABV for NA labeling in many marketspHMonitored for consistencyMonitored as a safety control, many producers acidify to keep finished pH low, often around 4.2 or belowMicrobiological testingPeriodic platingPlating on every batch, with release held until results are inPasteurization or sterile filtrationOptional for many stylesTypically required, with validated pasteurization units or filtration integrity checksSensory focusOff-flavors, style accuracyWorty or grainy notes, sweetness balance, oxidationOxygen controlImportantEven more important, since NA beer shows staling quicklyCleaning verificationRoutineATP swabs or similar on shared lines before NA runs
A few phase-specific additions help.
Brewhouse Additions for NA Beer
Record mash schedule details closely, since many NA recipes rely on higher mash temperatures to produce less fermentable wort. Track fermentability targets, not just original gravity. If you acidify, log the acid type, dose, and resulting pH.
Fermenter and Dealcoholization Additions
For limited or arrested fermentation, the stop point is everything. Check gravity and ABV more frequently than you would for a standard beer, and define the exact gravity at which you crash or halt. For dealcoholized beer, add checks for the dealcoholization run itself: input ABV, output ABV, flavor recovery steps if you use them, and equipment cleaning between runs.
Packaging and Release Additions
This is where NA beer differs most. Build a hold-and-release step into your packaging checklist. Product doesn't ship until ABV is confirmed below threshold, micro results are clean, and pasteurization or sterile filtration records are verified. Many producers target higher pasteurization units for NA beer than for standard beer, but the right number depends on your product and process, so validate it with your lab or a qualified food safety consultant.
Labeling and alcohol thresholds vary by country and sometimes by region. Confirm the rules that apply to every market you sell into, and make the threshold an explicit pass/fail line on your checklist rather than tribal knowledge.
Picture a 10-barrel brewery adding an NA pale ale to its lineup. They reused their standard checklists for the first two batches, and the second batch started showing haze and sourness in cans after a few weeks. The fix wasn't a new recipe. It was a separate NA style configuration with per-batch plating, a pH limit, a pasteurization verification step, and a hard hold before release. Their next batches stayed stable on the shelf.
Takeaway: Treat NA and low-ABV beer as its own style with its own phase checklists. Add per-batch ABV confirmation, pH limits, micro testing, and a release hold before anything ships.
Consistent beer doesn't come from a talented brewer working harder. It comes from a system where every phase has a short checklist, every critical task has an SOP, and every batch leaves a record you can compare. Start small: map your flow, build the brewhouse list this week, and add the fermenter and brite tank lists once the first one sticks. Then layer in NA-specific controls before your first non-alcoholic batch hits the fermenter.
If you're still tracking all of this in spreadsheets, the craft brewery solution from BrewPlanner was built for small and growing teams making exactly that jump. And when you're ready to tie your QC checklists directly to scheduling, tank assignments, and batch traceability, explore BrewPlanner's brewery management software and see how your next batch can match your best one.
