Skip to content

Insights

Insights is a dashboard over your own brewing, at /insights. It has eleven panels, from your brewhouse efficiency to how often you brew.

We work out nine of them on your own device, from your own batches, without uploading or downloading anything, so they work offline and when you’re signed out. The two fermentation-device panels are different. A device sent those readings to your account instead of you typing them into this browser, so we have to fetch them, which means they need a connection and the Beerwright plan. If we can’t reach them, those two panels don’t appear and the other nine work as usual.

The brewhouse-efficiency trend works on every plan, because it’s the panel that tells you which measurement to take next. The other ten are a Beerwright feature. On other plans we draw them from sample data with a lock on them, so you can see what they’d show before deciding. We keep working out your own batches in the meantime, so your charts are ready as soon as you upgrade.

The Insights page on a Beerwright account: eleven panels over your own batches, some drawn as charts and some saying how many more batches they need before they can be.The Insights page on a Beerwright account: eleven panels over your own batches, some drawn as charts and some saying how many more batches they need before they can be.

Every batch keeps its own copy of the recipe you brewed it from, as it was that day. Insights uses that copy instead of the current recipe, so editing a recipe next week won’t move a point for last week’s brew.

If a measurement is missing, we leave the batch out of that panel. We never use a prediction in place of a reading, because a trend made from your own estimates wouldn’t tell you anything. The one exception is the beer map, which plots your recipes as designed and is labeled that way.

A batch with no brew day has no date. It still counts in the styles summary and appears on the beer map, but we leave it out of every chart with a time axis.

Until you’ve logged enough batches for a panel, it shows one sentence telling you which reading would fill it in.

How much of the malt’s available sugar actually reached your fermenter, brew by brew. We work it out from what you measured instead of taking it from your equipment profile, so it shows what your system actually did.

Needs 2 batches with an original gravity and a volume into the fermenter.

Apparent attenuation per brew, with the published band for the yeast you actually used drawn behind each point. If a point is above the band, your yeast did better than the packet says. If it’s below, something stalled.

We draw the band for each batch separately, because beers on different strains have different bands.

Needs 2 batches with an original gravity and a final gravity.

Predicted OG along the bottom, measured OG up the side, and a dashed diagonal where batches hit their prediction exactly. Points above the line are brews that came in stronger than the recipe predicted, and points below came in weaker. If most of your points sit on one side, it’s time to recalibrate your equipment profile, because we base the predictions on its mash efficiency and its losses. We record brewhouse efficiency so you can see how each brew day went, but we don’t use it in the predictions.

Both axes use your gravity units, so a Plato brewer gets a Plato chart.

Needs 3 batches with a measured original gravity.

What fraction of the wort that went into the fermenter came back out as packaged beer. This is where you can see what trub, dry-hop absorption and transfer losses actually cost you.

Needs 2 batches with a fermenter volume and a packaged volume.

Every batch you’ve scored on a tasting sheet, plotted against a brew-day measurement. You choose which one goes along the bottom, from brewhouse efficiency, attenuation, yield or original gravity, and the score stays up the side, so you can see whether the brews you rated highest have anything in common.

Above the chart you’ll see how many of your tasted batches have a score, your average out of 50, and your best beer by name.

Needs 3 scored batches.

Brews per month, with the liters beside them. The bar shows the number of brews, because this panel is about how often you brew, so a 40 L brew day counts once. We keep empty months on the chart, so you can see a quiet winter.

The volume of each batch is its packaged volume if it was packaged, otherwise what went into the fermenter, otherwise what the recipe planned. Months relying on the last of those are marked ≈.

Needs 1 batch with a brew day.

Every BJCP category you have made, most-brewed first, with the date you last brewed one. We group by category, so an American IPA, a hazy and a double all count as IPAs. Recipes with no style get their own bar so they’re still counted.

Needs 1 batch.

Every batch as a dot, with ABV along the bottom and IBU up the side, in the color of the beer. It shows what you actually like to brew, and it’s the quickest way to notice if everything you make sits in the same corner.

This is the one panel that falls back to the recipe’s predicted ABV when you did not measure one, because its subject is the recipes as designed. The panel says how many of its points are predictions.

Needs 3 batches.

What a liter of beer cost you to brew, brew by brew, from what each batch’s ingredients cost when you brewed it. Later price changes don’t move an old point. We leave out batches priced in another currency instead of converting them at a rate you didn’t choose.

Needs 2 batches with priced ingredients.

Apparent attenuation day by day, averaged across batches with a hydrometer in them, for your three most-brewed strains. It shows you whether a strain you think of as slow is slow every time, or was only slow once.

Needs 1 fermentation with a hydrometer in it, and a connection.

How long each strain takes to get there: first reading to the day the curve went flat, averaged per strain, with the number of batches behind each figure. We don’t count a fermentation that was still falling when the readings stopped, because we can’t tell when it finished.

Needs 2 fermentations with a hydrometer in them, and a connection.

Four readings fill in most of the panels above. The rest come from a tasting sheet, from the prices on your ingredients, or from a device in the fermenter.

Reading Unlocks
Original gravity Efficiency, attenuation, targets, a measured ABV on the map
Final gravity Attenuation, and a measured ABV on the map
Volume into the fermenter Efficiency, yield
Packaged volume Yield, and measured liters on the cadence chart

All four are on the batch page, under Measurements, and each takes no longer than pulling a sample.

Insights shows you what your system did. The Equipment page lets you act on it. Each profile there has a Measured on this rig section. For mash efficiency, brewhouse efficiency and boil-off rate, it shows the value set on the profile, the value your batches actually measured, and the gap between them. A Use measured button beside each one copies that single figure into the profile.

The measured column is the median of every batch brewed on that profile. One stuck mash or one boil that got away can produce a reading tens of percentage points off, and an average would pull the suggestion with it. The median isn’t affected by one bad batch, so four brews near 70 % and one bad day at 20 % still suggest 70 %.

  • We never change your profile for you. Changing a profile changes the predicted gravity of every recipe on it, so each button is one explicit change, undoable with ⌘Z.
  • Each button changes one field. Take the boil-off rate and leave the efficiency alone if that is what you meant.
  • We can only measure these three figures. We can’t work out deadspaces and absorption rates from a brew day, so they have no row.
  • Built-in profiles are read-only. You can see their figures, but you need to duplicate the profile first to record your own numbers.
  • We leave out archived batches, and we match each batch to the rig you actually brewed it on, even if its recipe uses a different profile today.

The same suggestion also appears on a batch page once two measured batches agree, which is where you’re most likely to notice the gap first. It stays on the Equipment tab after that.

  • No date filters. The page shows your whole history, always.
  • No curve for one beer. The two device panels average across batches by strain. To watch a single fermentation as it happens, open its batch page; see Fermentation devices.
  • No sharing. There is no way to export a panel as an image, and nothing on this page is published anywhere.

Something wrong on this page? Tell us.