I am trying to improve my recipes/brew sheets and standardise them all, as they all have subtle differences as I’ve made changes through the year.
Is there any way of ‘testing’ a recipe without starting an actual brew to check that all the calculations and reporting tags work properly before hand? (maybe a feature request?)
Also, I have a number of reporting tags attributed to some ‘readings’ to carry out calculations later in the day, but how does applying a reporting tag to a ‘check’ work?
My understanding is that a ‘check’ on a brew sheet is just a ‘tick box’? (to which you can enter some notes). But if you apply a reporting tag to it, when does it get its information/number/value from? So does having a reporting tag on a check not really work (in the same way as a ‘reading’ does)?
For example, I have Target OG as a ‘reading’ currently, with an expected value of 1.0450 - 1.0450, to which we have to type in 1.0450 every brew. But my ‘Target OG’ is the same every time for that particular beer/brew.
Hi Chris, Thanks for your comment! Currently, there isn’t a way to test a recipe without starting a batch; however, I can definitely understand how this would be useful. We do have a feature request for Recipe Preview and Testing . It would be great if you could add your vote to this!
When you apply a reporting tag to a ‘Check’, then this can be reported on in Reporting → Pre-built production & inventory reports → Recipe reporting tags records. This will report back data regarding the check, such as whether it was ‘Done’ and the time it was taken.
You’re right; currently if you would like to use a figure to calculate on, then this would have to be entered as a ‘Reading’, even if this value is ‘fixed’ on each recipe. It sounds like the Recipe-level variables for Calculated Fields, e.g. allow “Add ingredient” quantity to be the result of a calculation feature request may be close to what you need here; if you agree, then it would be great if you could add your vote to this! Let me know if you need any more help. Cheers!