A stack of poorly organized spreadsheets won't save you during a TTB audit. Neither will that binder of handwritten brew logs sitting on the shelf above your mill. Every brewery operating in the United States must file a Brewer's Report of Operations (BROP) and maintain daily records that account for every barrel produced, transferred, packaged, and sold. The penalties for noncompliance range from fines to license revocation, and the TTB doesn't accept "we lost track" as an excuse.
The good news? If your production software is set up correctly, your daily records practically build themselves, and generating your BROP becomes a matter of clicking a button rather than spending a weekend buried in paperwork. This guide walks you through the exact structure your daily records need, how to configure your production software to capture the right data at each stage, and how to turn that data into a clean, audit-ready Brewer's Report of Operations. Whether you're filing monthly or quarterly, the principles are the same.
For breweries already using brewery management software with built-in TTB reporting, much of this is handled automatically. But understanding the "why" behind every field matters, because when an auditor asks you to explain a discrepancy between your packaged beer and your reported losses, "the software did it" isn't a satisfying answer either.
What the TTB Actually Requires and Why Most Breweries Fall Short
Before configuring any software, you need a clear picture of what the TTB expects. The official requirements for brewery operations lay out the obligations, but reading federal regulations is about as enjoyable as cleaning a clogged heat exchanger. Let's break it down into practical terms.
The BROP (TTB Form 5130.9) is a periodic summary of your brewery's production and operations. Depending on your size and filing election, you submit it monthly, quarterly, or annually. But the report itself is just the tip of the iceberg. Underneath it sits your daily records, which are the transactional data that feeds every line of the BROP. The TTB requires you to maintain daily records of:
- Beer produced (in barrels) at the completion of fermentation
- Beer transferred between tanks, departments, or locations
- Beer packaged into kegs, cans, bottles, or any other container
- Beer removed for consumption or sale, including taproom pours
- Beer lost or destroyed, whether from dumped batches, spillage, or breakage
- Raw materials received and used, including malt, hops, adjuncts, and other ingredients
- Inventory on hand at the beginning and end of each reporting period
These records must be detailed enough to reconstruct the lifecycle of any batch. If a TTB auditor pulls batch 2024-047 and asks where those 15 barrels went, you need to show the trail: 15 barrels produced on a specific date, 14.6 barrels packaged into 124 cases of 16oz cans, 0.3 barrels of process loss, and 0.1 barrels of samples.
Where Breweries Typically Go Wrong
The most common compliance gap isn't intentional neglect. It's fragmentation. Breweries track production in one system (or on a whiteboard), packaging in another, taproom sales on their POS, and inventory in a spreadsheet that only one person understands. When BROP filing day arrives, someone has to manually reconcile all of these sources, and the numbers never quite add up on the first pass.
Process losses are another weak spot. Every brewery loses beer during transfers, filtration, centrifuging, and packaging. The TTB knows this, and they expect it. But they also expect you to document it. If your reported production minus your reported packaging and sales doesn't equal your reported losses plus your remaining inventory, you have a problem. Software that tracks volume at each stage of the brewing process, and automatically calculates the delta, eliminates this guessing game.
Finally, many breweries underestimate the importance of timestamps. Daily records means daily. If you're retroactively entering a week's worth of production data every Friday afternoon, your records technically aren't compliant. Real-time or same-day data entry, even if it's just a brewer tapping "transfer complete" on a tablet, is the standard you should aim for.
Configuring Your Production Software for TTB Compliance
Getting your software right from the start saves you hundreds of hours over the life of your brewery. This section covers the specific configurations and workflows that turn general-purpose production software into a TTB compliance engine.
Step 1: Define Your Units and Measurement Standards
The TTB reports everything in barrels (one barrel equals 31 gallons). Your brewhouse might think in hectoliters, your packaging line counts in cases, and your taproom tracks pints. Your software needs to handle all of these units while maintaining a single source of truth in barrels.
Configure your tank volumes accurately. Every brewhouse, fermenter, and brite tank should have its working capacity recorded in your system. When a brewer logs a batch into a 30-barrel fermenter and records it as full, the system should automatically calculate the volume. When that beer gets transferred to a 30-barrel brite tank and the brewer notes it's at 28 barrels, the system should flag the 2-barrel difference as a transfer loss and prompt for confirmation.
This is where inventory management becomes a compliance tool rather than just an operational convenience. Every movement of beer, from brewhouse to fermenter to brite tank to package, is both an inventory transaction and a TTB record. When your inventory system tracks these movements with timestamps, volumes, and batch associations, you're building your daily records in real time without any extra effort from your team.
Step 2: Map Your Brewing Process to TTB Categories
The BROP organizes beer into specific categories: beer produced, beer in process, beer in storage, beer packaged, and beer removed. Your software needs to map your internal workflow stages to these categories.
Here's a practical mapping that works for most breweries:
Brewing StageTTB CategoryTrigger EventMash and boilNot yet beer (materials used)Brewday startActive fermentationBeer in processYeast pitchFermentation completeBeer producedGravity target reachedTransfer to briteBeer in storageTransfer loggedCanning/keggingBeer packagedPackaging run completeShipped to distributorBeer removed for consumption/saleInvoice createdTaproom pourBeer removed for consumption/salePOS transactionDumped batchBeer lost/destroyedDump logged with reason
The critical transition is "beer produced." The TTB considers beer to be produced when fermentation is complete, not when you package it. Many breweries mistakenly report production at packaging, which creates timing discrepancies that confuse auditors. Configure your software to record production volume when a batch moves out of fermentation, and make sure that event is clearly distinguished from the packaging event.
Step 3: Establish Daily Record Entry Workflows
Your brewers, cellar workers, and packaging operators need clear workflows for data entry. The goal is to capture every volume-affecting event on the day it happens. Here's what that looks like in practice:
- Morning: Cellar team logs any overnight transfers, checks fermentation status, and marks any batches that have reached final gravity (triggering "beer produced" records)
- During packaging runs: Packaging operator records starting tank volume, finished goods count (cases, kegs), and ending tank volume. The difference between starting volume and (packaged volume + ending volume) is your packaging loss
- End of day: Shift lead reviews the day's entries, confirms all transfers are accounted for, and flags any discrepancies for investigation
For craft breweries running one to three batches per week, this might seem like overkill. It's not. Building the habit when you're small means you won't scramble to retrofit compliance processes when you scale to five or ten batches per week and suddenly the TTB is paying closer attention.
Turning Daily Records into Your Brewer's Report of Operations
If your daily records are clean and complete, generating your BROP is straightforward. The report is essentially a summary of your daily records, grouped into the categories the TTB cares about, for a specific reporting period.
Understanding the BROP Structure
The Brewer's Report of Operations (TTB Form 5130.9) has several parts, but the core sections that demand accurate production data are:
- Part I: Beer Produced. Total barrels where fermentation was completed during the reporting period. This pulls from your "fermentation complete" events.
- Part II: Beer in Process. The volume of beer that's still fermenting or conditioning at the end of the reporting period. This is your work-in-progress inventory.
- Part III: Disposition of Beer. Where your finished beer went, including taxable removals (sales), tax-exempt removals (exports, samples within limits), losses, and ending inventory.
- Part IV: Materials Used. Pounds of malt, hops, and other ingredients consumed during the reporting period.
The math must balance. Opening inventory plus production must equal dispositions plus closing inventory, adjusted for losses. If it doesn't, you either have a data entry error or an actual discrepancy that needs investigation and documentation.
Generating the Report from Your Software
With properly configured production software, the generation process looks like this:
- 1Select your reporting period. Monthly, quarterly, or annual, depending on your filing election.
- 2System aggregates daily records. All "beer produced" events sum into Part I. All in-process batches populate Part II. All packaging, sales, taproom pours, and losses populate Part III. All ingredient usage populates Part IV.
- 3Review the balance check. Your software should perform the opening + produced = dispositions + closing calculation automatically and highlight any imbalance.
- 4Investigate discrepancies. If the numbers don't balance, drill into the daily records. Common culprits include a transfer that wasn't logged, a packaging loss that wasn't recorded, or a taproom keg that was tapped but never entered into the POS.
- 5Export or file. Generate the report in the TTB's required format for submission.
The entire process, from selecting the period to having a filing-ready report, should take under an hour if your daily records are maintained consistently. Compare that to the two or three days many breweries spend manually compiling data from multiple sources.
One often-overlooked benefit of software-generated BROPs is the audit trail. When every number on your report links back to a specific daily record, which links back to a specific batch, tank, and operator entry, you can answer any auditor's question in minutes. Understanding your true per-batch costs also becomes dramatically easier when every input and output is already tracked at the batch level.
Building an Audit-Proof System That Runs Itself
Compliance isn't a one-time setup. It's an ongoing discipline. But with the right foundation, maintaining TTB-ready records becomes part of your normal operations rather than a separate, dreaded task.
Start by establishing a monthly reconciliation routine, even if you file quarterly or annually. At the end of each month, run your BROP generation process as a dry run. Check the balance. Investigate any discrepancies while the details are still fresh. A 0.5-barrel discrepancy is easy to track down when it happened last week. It's nearly impossible to resolve six months later during your annual filing.
Train every team member who touches beer on the importance of timely, accurate data entry. This doesn't require lengthy seminars. A laminated card next to each workstation that says "Log every transfer. Record every loss. Do it today, not tomorrow" goes a long way. Make it clear that this isn't bureaucratic overhead. It's what keeps the brewery's license intact.
Set up automated alerts in your software for common compliance risks:
- Batch in fermenter for more than 30 days without a status update
- Packaging run where recorded output is less than 95% of starting tank volume (suggesting unrecorded loss)
- End-of-day with no daily records entered (indicating missed entries)
- Inventory count variance exceeding 1% of total stock
These alerts catch problems before they compound into reporting nightmares. A single missed transfer entry is a quick fix. Thirty missed entries discovered at filing time is a crisis.
Document your processes. The TTB doesn't prescribe exactly how you keep your records, but they do require that your system be consistent and auditable. Write a one-page standard operating procedure that describes your daily record workflow, your monthly reconciliation process, and your BROP generation steps. If an auditor asks "how does your system work," you hand them that document.
Finally, keep your software updated and your data backed up. Cloud-based brewery management software handles both of these automatically, but if you're running anything locally, make sure you have a backup strategy. The TTB requires you to retain records for at least three years (and six years for some records). Losing data to a hard drive failure is not a valid excuse for incomplete filings.
The best TTB compliance system is one your team actually uses every day. If data entry feels like extra work, it won't happen consistently. If it's built into the natural flow of brewing, transferring, and packaging, it becomes invisible, and your records stay clean.
The breweries that breeze through TTB audits aren't the ones with the fanciest software or the biggest compliance teams. They're the ones where every brewer, cellar worker, and packaging operator understands that logging a transfer takes 30 seconds and saves the business from a world of pain. Set up your system right, build the habits, and your Brewer's Report of Operations will practically write itself.
