# Requiring Steps to be Finished in Brewing Process Before Progressing to Next

**URL:** <https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712>\
**Category:** Ideas & feature requests\
**Created:** [30 June 2023 18:56 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712 "2023-06-30T18:56:36Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![christopher-tkach](https://community.breww.com/user_avatar/community.breww.com/christopher-tkach/32/1316_2.png) [@christopher-tkach](https://community.breww.com/u/christopher-tkach)\
**Post date:** [30 June 2023 18:56 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/1 "2023-06-30T18:56:37Z")

</div>

Hi Breww Team – We have just finished our first attempt at physical inventory reconciliation after using Breww for the past 6 months and its not pretty. What we have determined is that the recording of post-brew ingredient additions (Dry Hops in our case) can easily be forgotten and this is creating inventory problems.

The solution to this (and likely other inventory discrepancies) would be to require that a post brew stage be marked completed prior to being able to move the beer through to the next stage or transfer the beer to a brite tank or package it. Currently, its all too easy to complete a brew day then move that beer from fermenter to a brite tank without recording actions in post brew stages. Hence, the recording of ingredients used in the dry hop stage we have setup in our recipe. There needs to be a safety mechanism in place to remind the user that something was forgotten.

---

<div class="post-metadata">

**Author:** ![rodger-doherty](https://community.breww.com/user_avatar/community.breww.com/rodger-doherty/32/288_2.png) [@rodger-doherty](https://community.breww.com/u/rodger-doherty)\
**Post date:** [30 June 2023 20:17 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/2 "2023-06-30T20:17:16Z")

</div>

Hi Chris

I have discovered the exact same over the last couple of years. Unfortunately you cannot trust people to follow each step that they need to. It also affects cost of sale calculations.

---

<div class="post-metadata">

**Author:** ![christopher-tkach](https://community.breww.com/user_avatar/community.breww.com/christopher-tkach/32/1316_2.png) [@christopher-tkach](https://community.breww.com/u/christopher-tkach)\
**Post date:** [5 July 2023 11:57 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/3 "2023-07-05T11:57:42Z")

</div>

I can trust them to follow it, its the recording of it that is problematic.

---

<div class="post-metadata">

**Author:** ![james-heffron](https://community.breww.com/user_avatar/community.breww.com/james-heffron/32/1683_2.png) [@james-heffron](https://community.breww.com/u/james-heffron)\
**Post date:** [6 July 2023 09:05 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/4 "2023-07-06T09:05:05Z")

</div>

I totally agree. Human error needs to be avoided by way of a prompt or check box. It’s all to easy for our cellar staff to forget to remove the dry hop addition from Breww. They should be unable to move the beer to BBT without this box being ticked.

---

<div class="post-metadata">

**Author:** ![james-heffron](https://community.breww.com/user_avatar/community.breww.com/james-heffron/32/1683_2.png) [@james-heffron](https://community.breww.com/u/james-heffron)\
**Post date:** [6 July 2023 09:10 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/6 "2023-07-06T09:10:36Z")

</div>

It’s all too easy for our cellar staff to forget to update Breww after dry hopping. It has lead to some large stock discrepancies at month end and all the knock on issues from there.

Solution: A tick box that must checked before transferring to BBT or Pack or whatever the next stage is. Titled something like: ‘Confirm all FV additions have been actioned’

This already has some traction in this comments section:

> [@Requiring Steps to be Finished in Brewing Process Before Progressing to Next](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712):
>
> Hi Breww Team – We have just finished our first attempt at physical inventory reconciliation after using Breww for the past 6 months and its not pretty. What we have determined is that the recording of post-brew ingredient additions (Dry Hops in our case) can easily be forgotten and this is creating inventory problems. The solution to this (and likely other inventory discrepancies) would be to require that a post brew stage be marked completed prior to being able to move the beer through to the…

christopher-tkach summed it up in the above thread reaaly well:

“There needs to be a safety mechanism in place to remind the user that something was forgotten.”

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [12 July 2023 17:05 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/7 "2023-07-12T17:05:06Z")

</div>

Thanks for your comments on this, James. Please can I clarify; how does your feature request differ from [Requiring Steps to be Finished in Brewing Process Before Progressing to Next](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712)?

If they’re the same thing, then a single feature request with all the votes would be better than two with the votes spread. If they’re different, we need to make sure the differences are clear so that people know what they’re voting for 👍 Thank you.

---

<div class="post-metadata">

**Author:** ![alex-barlow](https://community.breww.com/user_avatar/community.breww.com/alex-barlow/32/773_2.png) [@alex-barlow](https://community.breww.com/u/alex-barlow)\
**Post date:** [30 August 2023 14:32 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/8 "2023-08-30T14:32:58Z")

</div>

Hi Luke. I think these could be the same feature, but need to ensure any additions are incorporated and accounted from stock.

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [6 September 2023 12:21 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/9 "2023-09-06T12:21:08Z")

</div>

Thanks Alex, I agree.

I’ve merged this thread into the other to keep all the votes in one place and help push it up the priority list.

If anyone else would find this useful, please vote for it using the button in the top-left 👍

---

<div class="post-metadata">

**Author:** ![rachael-bull](https://community.breww.com/letter_avatar_proxy/v4/letter/r/cab0a1/32.png) [@rachael-bull](https://community.breww.com/u/rachael-bull)\
**Post date:** [9 July 2026 10:30 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/11 "2026-07-09T10:30:46Z")

</div>

Did anything come of this? It’s something we’re struggling with and I found this thread looking for a fix!

---

<div class="post-metadata">

**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\
**Post date:** [9 July 2026 10:54 UTC](https://community.breww.com/t/requiring-steps-to-be-finished-in-brewing-process-before-progressing-to-next/2712/12 "2026-07-09T10:54:56Z")

</div>

Not yet, but it’s on the request list. Make sure to vote for it, if it’s something you’d like to see added to Breww.

For more on how we manage feature requests, please see

> [@bulb Posting ideas & feature requests for Breww blue\_heart](https://community.breww.com/t/posting-ideas-feature-requests-for-breww/22):
>
> Have an idea or request? Discuss and plan it here. As a community, we can work together to make Breww even better than the Breww team could do without your input. Everyone has 20 votes, so please vote for your favourite ideas to help the Breww team prioritise what’s important to you. We’ve been building and further developing Breww ever since it was first released for early adopters, and always with the advice and suggestions of our breweries. By using the feature requests area of the Breww Com…
