When we transfer the wort from the brewhouse to the fermenter, that should be considered the original gravity. The system should store this information without me having to take the first reading manually. The system already has the gravity and pH after boiling, so it should use those as the initial analysis.
Well, we might liquor back after that, so the knockout gravity isn’t always the original gravity?
In more than 11 years brewing, I never added sugar after knockout. Even if this is possible, I would see as exception and you can go on the Breww and update the OG.
Adding water pre-fermentation is not an uncommon procedure, the OG will be lower than the gravity at knockout.
But, yes, you’re right , we could add another reading and mark that as OG
Exactly. When brewing high-gravity wort with the intention of diluting it, I believe the best time to set the OG is during transfer out of the brewhouse. It could be pre-filled with the measured gravity, but still allow it to be overridden if dilution is applied.
Breww will copy a reading from a recipe stage to the fermentation readings if we tell it to (when we set up the recipe). It won’t mark it as OG. Perhaps it should, if we tell it to. We’d need Breww to allow this to be changed (another reading to be OG), if required.
The “transfer” form doesn’t have anywhere to enter gravity (or does it?). Here, we usually enter knockout gravity as the first reading in a post-brewing “fermentation” stage - which is copied to fermentation readings, and this would require us to indicate it is OG, usually.
No, I didn’t mean that the numbers would come from the recipe. I meant that the recipe would provide the requested data from the brewing page. I’m not sure if this is part of the recipe template, but even if it isn’t, brewers should create a recipe that includes those readings (gravity, volume, and pH).
Thanks for the suggestion, Bruno.
There is already a setting to copy the reading to the batch readings. The screenshot below is from editing the recipe action:
This wouldn’t make it the OG in itself, which I agree with you, would be useful, but it’s probably a helpful time-saver that you can take advantage of today.
The good news is that what you’re asking for will be implemented as part of Calculated ABV on merged batches & OG on multi-turn batches and that request is very much on our radar. If you can vote for that other thread, that would be great. I’ll close this one to keep all votes in one place. Thank you.