Guide
Bright Tank Not Carbonating? Diagnose an Overnight Flat Batch
A practical overnight diagnostic for a bright tank that is still flat: confirm dissolved CO₂ and product temperature, then check the gas path, stone, and logs.
A bright tank that is still flat in the morning calls for investigation, not one large adjustment. Work in order: confirm what is in the liquid, confirm product temperature, then follow the gas from supply to stone. Only then should the log tell you where the overnight run lost its way.
Start with a measured answer, not the gauge
A tank-pressure reading is a process condition, not a direct measurement of dissolved CO₂. The American Society of Brewing Chemists’ Beer-13 method works with a representative sample, temperature, and established headspace gas pressures; it also describes an instrumental volume-expansion approach. Sampling and method belong in the diagnosis, not after it.[1]
Take a representative sample using your calibrated, validated QA method and normal sampling procedure. Record the measured dissolved CO₂, product temperature at sampling, tank pressure, and time. Compare those facts with the batch specification and a known-good batch, not a quick taste. A controller display, a tank gauge, or a temperature probe may be useful process information, but none alone proves the dissolved-CO₂ result.
Verify the product temperature and the calculation basis
Temperature changes the equilibrium. NIST reference data for CO₂ in water show that, at a given pressure, warmer liquid holds less dissolved CO₂; at a given temperature, a higher CO₂ pressure supports more.[2] Beverage composition affects the exact relationship, so use your approved product specification and validated method rather than borrowing a generic chart or target.
If the product was warmer than expected, or if its temperature rose overnight, the same process conditions may no longer hold the intended carbonation. Check the actual product-temperature reading against your normal verified reference, including the sensor and thermowell arrangement. Then confirm that the temperature used in the carbonation calculation is the temperature of the product, not the room or jacket reading.
Do not chase the result with blind pressure changes. Once the measurement and temperature are trustworthy, use the tank, stone, and controller manufacturers’ instructions together with your site SOP. Keep every check within the rating of the vessel and its fittings, with relief protection in service.
Follow the gas path before blaming the stone
When the sample confirms low dissolved CO₂, trace the route from supply to tank. Confirm that CO₂ is available at the source and that valves, connections, check valves, controls, and stone hose are in the intended operating state. Use approved leak-check and isolation procedures; a small restriction or a connection in the wrong position can look like slow tank carbonation.
The key question is whether gas reached the liquid through the intended path for the whole run. A stable headspace reading does not establish that the stone circuit delivered gas, and it does not substitute for a dissolved-CO₂ check. Note any interruption, change in supply condition, unusual pressure behaviour, or control alarm. Those details make the next decision much clearer than a single end-of-shift gauge reading.
Give the carbonation stone its own inspection
A carbonation stone is where the gas path becomes liquid contact. If a familiar batch now takes longer under comparable conditions, inspect the stone circuit, its connections, and maintenance history. Manufacturer stone-care guidance identifies declining flow at the same pressure or a longer run as signs to check stone condition; blocked pores can undermine carbonation.[3]
Do not improvise a cleaning chemical, concentration, or pressure test. Isolate and depressurize equipment according to the site SOP before service, then use the stone and tank manufacturers’ approved cleaning and sanitation procedure. Record what was found and what maintenance occurred. This keeps one dirty or damaged component from becoming a recurring mystery.
Let the overnight log point to the first departure
Pull the sequence from the batch log: transfer or fill time, product-temperature trend, actual tank-pressure trend, gas-supply status, control events, and measured dissolved CO₂. Start with the first value that departed from the known-good pattern. A temperature change points to cooling or measurement; a gas interruption points upstream; a normal gas path with a changed flow response makes the stone worth closer attention.
This is also the useful place to compare like with like. A different product, fill level, transfer condition, or stone-service history can change the story. The goal is not to find one universal regulator setting. It is to make the next batch’s temperature, gas contact, and verification repeatable.
Where the recurring weak point is manual monitoring, FizzWizz is one option to evaluate. The manufacturer says it reads product temperature and tank pressure, calculates a finish pressure for the selected carbonation level, adds CO₂ through a carbonation stone, and holds that pressure. It can help manage process conditions, but it does not replace a representative, calibrated dissolved-CO₂ check. If that workflow fits a documented need, review it alongside your tank configuration and QA plan.[4]
The practical morning handoff is short: measure the liquid, verify the actual product temperature, trace the gas path, inspect the stone, and preserve the timeline. That routine turns “flat by morning” from a vague alarm into a solvable batch record.