# 🧭 Production Dashboard UI Suggestions

**URL:** <https://community.breww.com/t/production-dashboard-ui-suggestions/5914>\
**Category:** Ideas & feature requests\
**Tags:** idea-not-applicable\
**Created:** [15 May 2025 08:49 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914 "2025-05-15T08:49:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![robert-jongkees](https://community.breww.com/letter_avatar_proxy/v4/letter/r/bb73d2/32.png) [@robert-jongkees](https://community.breww.com/u/robert-jongkees)\
**Post date:** [15 May 2025 08:49 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/1 "2025-05-15T08:49:59Z")

</div>

### Goal: Streamline daily operations, reduce clicks, and improve at-a-glance monitoring of fermentation progress.

### 🛢 Vessel Dashboard Improvements

1. **Daily Fermenter Reading Status Icons**  
Add visual indicators (e.g. ✅ / ⏳) to show if the daily reading has been completed or is still pending. Ideally placed near each vessel in the “ Vessel visualisation” section for quicker visibility without extra navigation.

2. **Sortable Daily Reading List**  
In the “Daily batch readings required” section, allow sorting by **vessel name** or **vessel code** to support larger breweries with many active fermenters.  
[Sort/filter production vessels/tanks by status](https://community.breww.com/t/sort-filter-production-vessels-tanks-by-status/3970) This is similar but not completely the same.

3. **Consolidate Reading Controls**  
Move the green “+” button for entering daily readings and the associated status indicators into the **main vessel overview (“Brewing systems, vessels, and in-progress batches”)**, rather than keeping them in the separate “ Daily batch readings required” section. This helps reduce UI fragmentation and clutter.

4. **Final Gravity Indicator**  
On the vessel overview, include an icon (🏁or​:chart\_decreasing: or similar) or badge to indicate if **Final Gravity** has already been recorded for the current batch.

5. **Latest Reading Sidebar**  
Allow users to view the **most recent vessel readings (with timestamps)** in the new slide-out sidebar. This could be part of the “Vessel status” block, or a new block altogether. This would be useful when glancing across multiple vessels without opening popups.  
Similar to request: [Show last gravity & carbonation measurements in the in-progress batches table on the production dashboard](https://community.breww.com/t/show-last-gravity-carbonation-measurements-in-the-in-progress-batches-table-on-the-production-dashboard/5502)

6. **Popup Header Improvement**  
When entering a fermenter reading via the popup “+ Record batch reading” , display the **vessel name/ID in the header**. The popup currently obscures the underlying info, so it’s hard to verify which vessel you’re working on without closing it.  
So the header becomes: Add fermentation readings for batch {BATCH} {BATCH REF} in vessel {VESSEL NAME}

7. **Anchor Link for Daily Readings**  
Provide a direct anchor link to jump to the “Daily batch readings required” section — helpful for mobile/tablet and just general quick navigation and bookmarking.

* * *

### 🍺 “Batches” Page Enhancements (Dashboard\>Production\>Batches)

1. **Fermenter Number Column**  
Add a column for the **fermenter/vessel number** directly in the “Batches” table — essential context when navigating multiple batches.

2. **Customizable Table Columns**  
Let users toggle table columns on/off to create role-specific views. For instance, brewers might want to see:  
_Batch_, _Batch Ref_, _Start Date_, _Beer_, _Tags_, _Start Volume_, _End Volume_, _ABV_  
…while hiding less relevant fields like _Site_ or _Recipe Name_.  
(This could later be scaled to all tables across Breww, not just also but for Inventory, Packaged Beer, Fermentation, etc.)

* * *

These ideas are meant to **enhance usability without stripping out critical info** , by emphasizing better structure, quicker access, and more relevant details per user role. Thanks for all the continued improvements — Breww is already a fantastic tool, and these enhancements would take the production UX even further.

---

<div class="post-metadata">

**Author:** ![rvanlaak](https://community.breww.com/user_avatar/community.breww.com/rvanlaak/32/3741_2.png) [@rvanlaak](https://community.breww.com/u/rvanlaak)\
**Post date:** [26 May 2025 12:42 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/2 "2025-05-26T12:42:04Z")

</div>

This is a really nice set of enhancements, and could really save brewers a lot of time on a day to day basis.

---

<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 June 2025 11:17 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/3 "2025-06-12T11:17:42Z")

</div>

Thanks for all the suggestions, Robert.

I think these are all great ideas, so thank you for posting them, but unfortunately, we’re unable to handle feature requests threads with lots of separate ideas in them. We need one idea per thread.

I’m really sorry that I have to do this; I have to close this thread and ask you to post them individually. For more on why, please see [I’ve got lots of ideas. Shall I post one big request?](https://community.breww.com/t/posting-ideas-feature-requests-for-breww/22#ive-got-lots-of-ideas-shall-i-post-one-big-request-3) in our feature request guidelines.

Thank you for your understanding and we do appreciate your comments and suggestions.

---

<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 June 2025 11:17 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/4 "2025-06-12T11:17:58Z")

</div>



---

<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 June 2025 11:18 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/5 "2025-06-12T11:18:07Z")

</div>



---

<div class="post-metadata">

**Author:** ![robert-jongkees](https://community.breww.com/letter_avatar_proxy/v4/letter/r/bb73d2/32.png) [@robert-jongkees](https://community.breww.com/u/robert-jongkees)\
**Post date:** [13 June 2025 03:34 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/6 "2025-06-13T03:34:16Z")

</div>

These are 9 different suggestions, about 2 topics. Would you like me to split all 9 or make 2 posts?  
Since I expect the changes to be so small and easy to do, I thought that the first 8 could be joined.

---

<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:** [16 June 2025 11:17 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/7 "2025-06-16T11:17:37Z")

</div>

Thanks, Robert. This would need to be 9 requests, I’m afraid. Cheers.

---

<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:** [21 June 2025 11:17 UTC](https://community.breww.com/t/production-dashboard-ui-suggestions/5914/8 "2025-06-21T11:17:43Z")

</div>

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.
