Fixing a persistent off-flavour with a troubleshooting visit

Why some faults keep coming back

Most breweries can fix a fault once. They taste butterscotch, give the next batch a longer diacetyl rest and move on. When the fault returns a month later, the team tries something else. After a few rounds people start to accept it as part of the house character.

Faults that keep coming back usually have one of three explanations. The first fix treated a symptom. The cause is intermittent, such as a valve that does not always close. Or there are two causes overlapping and fixing one hides the other for a while. All three call for the same approach: stop guessing and follow the beer.

Name the fault precisely

The visit starts at the tasting bench. Taste the beer from the tap, from a fresh package and straight from the tank, with the brewing team. Agree on what the fault actually is. Butter and butterscotch point to diacetyl. Green apple is acetaldehyde. Cooked sweetcorn is DMS. Plastic or medicinal points to chlorophenols or wild yeast. Sour and cloudy suggests infection. If the team uses different words for the same thing, nothing that follows will be reliable.

Our guide to beer off-flavours lists the common faults and their usual causes. Spiked samples help a team agree on vocabulary before the visit starts.

Sample along the process

Once the fault has a name, find where it first appears. Taste and smell at each stage: wort from the kettle, wort at pitching, beer at the end of primary fermentation, after conditioning, after filtration or transfer, in the keg or package and at the tap. The point where the fault first shows up is where to look hardest.

For diacetyl, a forced test is useful. Heat a sealed sample to around 60 °C for 10 to 20 minutes, cool it and smell it next to an unheated sample. If the heated one shows butter and the cold one does not, the precursor is still present and the beer left fermentation too early. If only the tap sample shows it, look at dirty draught lines before you look at yeast.

Keep samples from each stage in sealed, labelled containers in the cold room. If tasting is inconclusive on the day, the team can come back to them with fresh palates, or send them for lab analysis.

Read the records alongside the beer

Pull the brew logs and fermentation records for the last several batches, good and bad. Line them up. Look for what the faulty batches share: the same yeast generation, the same fermenter, the same brewer, a hotter week, a change of malt lot, a shortened schedule before a busy weekend. Patterns appear quickly on paper that nobody sees while living through one brew at a time.

This is the core of root cause analysis: ask why the fault happened, then why that cause happened, until you reach something you can change and check. A fault blamed on yeast that turns out to come from a glycol valve sticking open on one tank is a typical outcome.

Check the equipment, not only the recipe

• Strip and inspect valves, gaskets and sample ports on the suspect tanks. Old gaskets harbour bacteria where CIP cannot reach.
• Check the probe on the fermenter against a reference thermometer.
• Check CIP chemical strength, temperature and contact time against your SOP.
• Test brewing water for chlorine or chloramine if the fault is medicinal. Municipal supplies in India change treatment through the year.
• Clean or replace draught lines if the fault is only in the taproom.

Fix one thing and prove it

Change one variable at a time and brew again. If you change the yeast, the schedule and the cleaning routine in the same week, the fault may go away and you will not know why. Taste the next batch against a retained sample of the faulty one, ideally blind, so the team does not taste what it hopes to taste.

Write the fix into the SOP and add the check that would catch the fault early. The visit is finished when the team knows what to watch, not when one batch tastes right.

Keep a fault log from then on: date, beer, tank, the fault named and where in the process it was first noticed. After a few months the log becomes the most useful troubleshooting tool the brewery owns, because it shows patterns that no single tasting can.