A remote quality audit for a brewery: what we review

What a remote audit is

A quality audit asks a simple question: if something goes wrong, would you know and would you know why? We review records, observe routines on video and talk to the people who do the work. The output is a written report with findings ranked by risk and a plan for the next steps.

It is not an inspection by a regulator and it is not a certification. It is a practical review that helps a brewery improve its own system.

It is useful before a big step, such as a new tank, a new packaging line, a first export order or an expansion. Breweries also use it after a run of complaints, to find the pattern behind them.

Documents and records we ask for

We ask for:

• Process flow and recipes.
• Brew sheets and fermentation logs for a sample of batches.
• Lab results: gravity, pH, ABV, colour, bitterness if measured.
• Microbiology results, if any.
• Cleaning and sanitation schedules and records.
• Packaging checks: fill levels, seam checks for cans, carbonation.
• Complaint and return logs.
• Calibration records for thermometers, pH meters and scales.

Missing records are a finding in themselves. We say so without blame.

We also ask for a short description of who does what. In small breweries one person often brews, tests, cleans and packages. Knowing that tells us where the system is thin and where one illness or holiday could stop quality checks.

Cleaning, sanitation and hygiene

Most beer quality problems start with microbes or oxygen. We check how tanks, lines, hoses and fillers are cleaned, which chemicals and concentrations are used, contact times, temperatures and how the results are verified. A visual check is not proof of cleanliness, so we look for swab or rinse-water checks. By camera we look for dead legs, worn gaskets and unsealed drains.

Sampling is part of this. We pick a handful of recent batches at random and trace each from recipe to package, to see whether the paperwork tells a complete story. Gaps usually appear at handovers, such as a shift change or a tank transfer.

Water treatment gets a look too: what is added, how much and how it is measured.

Process control

We follow a batch from milling to package. Mash temperature and pH, boil vigour, wort cooling, pitching rate, aeration, fermentation temperature, diacetyl rest and crash cooling all affect quality. We compare what is written down with what is done. We note where the two differ. See our guide on troubleshooting beer faults over video call for how faults trace back to these steps.

Raw materials count too. We ask how malt and hops are stored, how water is treated and tested, how yeast is handled and how often it is re-used. Yeast re-used too many times without checks drifts in performance. Hops stored warm lose aroma and bitterness.

Packaging and shelf life

Oxygen pickup in packaging is a main cause of stale beer. We ask whether dissolved or package oxygen is measured, how kegs and cans are purged and how beer is stored and shipped. Warm storage speeds up staling. If you cannot measure oxygen, we suggest practical controls and a plan to start.

Beer returned from the market is a free source of information. We ask what is done with returned stock: is it tasted, dated and traced back to a batch? Without batch codes on packs, a complaint cannot be traced.

Sensory systems

We look at how your team tastes: how often, at what points and with what vocabulary. A panel that tastes every batch before release and records the result catches problems that instruments miss. We suggest a simple training routine and reference samples. Related reading is beer off flavours.

We also ask about training. Who has been shown how to taste, to clean a tank properly and to read a gravity measurement? A quality system lives in people more than in documents.

What a remote audit cannot do

We cannot take swabs, smell the cold room or feel a worn seal. We cannot confirm a microbial result without a lab. Where something needs a hands-on check we say so. A site visit can be arranged. The report ends with a short list of actions, an owner for each and the numbers to track. Next steps often include the one-page dashboard and, for some breweries, adding a non-alcoholic beer.

After the report, pick a few actions and revisit the list after a month. We are happy to join a follow-up call to check progress.

Our reports are written plainly. A busy owner should be able to read the first page and know the three most important actions.

Common questions

How long does a remote audit take?

It depends on the size of the brewery and the quality of the records. Planning, review and a feedback call are spread over some weeks.

Is a remote audit a certification?

No. It is a practical review that produces findings and a plan. It does not replace regulator inspections or formal certification.

What if my records are poor?

That is common. We start from what exists and help you build simple records.

Can you audit a very small brewery?

Yes. The method scales down. Small breweries often gain the most from a few basic checks.