Run a batch through its stages

A batch is the thing you're actually making — one run, from start to finish. You start it, log each stage as it happens (mash, ferment, spirit run, and so on), move it through its lifecycle as it progresses, and keep the record it builds along the way.

Batches live under Batches in the left-hand navigation — in the Day to day group on a hobby workspace, the Production group on a commercial one. The list and the batch page refresh every ten seconds, so state changes show up while you watch.

View your batches

1. In the navigation, choose Batches. The list shows every batch with its Code, Production type, State, and when it Started.
2. Narrow the list with the controls above the table:
   • Production type — All production types, Brewery, Winery, or Distillery.
   • State — All states, Planned, In progress, Released, or Archived.
3. Choose Load more to fetch the next page if there is one.
4. Choose a batch's row, or the View button on that row, to open it.

A new workspace shows No batches yet, pointing you to the New batch button at the top of the page.

Start a batch

1. From the Batches list, choose New batch (top right), or use Start a batch from the Home dashboard.
2. Choose the Production type for this batch. (You're only offered the production types your workspace is set up for.)
3. In Batch code, either enter your own code or leave it blank to auto-generate one. If you leave it blank, Brewstiller assigns a code for you when the batch is created.
4. For Recipe, either pick one of your recipes or leave it on Ad-hoc (no recipe) to start without one. (Only recipes that have a saved version are offered.) The field's note reads Optional — link this batch to a recipe, or start ad-hoc and add lineage later. Picking a recipe also sets the Production type to match it; change it yourself afterwards if you need to and your choice wins.
5. Optionally, set Beverage style — it starts on No style; choose a style such as American IPA, Dry Cider or Traditional Mead from the list. The field's note reads Optional — what you're making. It sets the words this batch's steps use (a mead ferments, it doesn't "ferment wine"). Picked from a recipe, this starts as the recipe's style and stays with the batch afterwards.
6. Choose Create batch. Just above the button a small note explains that new batches start out Planned — a plan on paper, not yet production — and that a batch becomes Active (and is counted in Active batches on your dashboard) when you start it. In the batch list and on the batch itself, that same state is labelled In progress once started. On success you're taken to the new batch.

Where you land depends on how you started it. A batch made from a recipe opens on the guided steps — the recipe's process laid out as a checklist to work through (see Work a batch as a checklist below). An ad-hoc batch opens on the full batch page.

Commercial plan: a commercial workspace also shows an optional Federal permit field. You can associate a covering federal (TTB) permit now, or leave it unset and add one later — a permit isn't needed to create a batch, only when you file its TTB or state forms. Hobby workspaces don't have permits and won't see this field.

If your plan's active-batch limit is full, Brewstiller tells you so instead of creating the batch — complete or archive a batch (or upgrade) to start another.

Understand the batch page

Opening a batch shows its Code and a State badge (Planned, In progress, Released, or Archived), its production type, and — if it came from one — a From recipe line linking back to the recipe and version it was made from. Below that:

• A Lifecycle card with the Batch started, Completed, Released, and Archived timestamps. "Batch started" is the batch's own start — each step card shows its own Stage started date separately, and the two can differ.

• A Lifecycle actions card for moving the batch along (below).

• A Reminders card with the batch's live reminders — see Work with a batch's reminders.

• A row of tabs — Stages, Lineage, Quality, QC tests, Tasting notes, and Changes — plus, once the batch is Released or Archived, an Outcome tab. The Stages tab is the day-to-day one; the others hold the batch's lineage graph, quality events, quality-control test results, your tasting notes, and the history of corrections made to logged stages. Outcome re-shows what you already recorded — readings, packaged output, vessels used, and your most recent tasting note — as a one-page summary of how the batch actually turned out; it invents nothing and shows nothing you haven't logged elsewhere. If any stage carries an addition recorded Not from a lot (hobby workspaces — see Record what a stage drew from), the Lineage tab says so — a line reading, for example, *"Conditioning —

  • 1 addition recorded without a lot"* — since that addition has no lot to trace back to and would otherwise just be missing from the graph. Choosing that line takes you to the stage's own Inputs list.

  If some of the sources feeding the batch (or the batches upstream of it) belong to another workspace, or no longer exist, the Lineage tab leaves them out of the Ancestors list and tells you how many — for example, "2 sources outside your workspace, or no longer available, are not shown." It is a count only: the tab never names, links or describes a hidden source, and the count is each distinct source once. A batch whose sources are all in your own workspace shows no such line. Cross-workspace lineage is not something the product creates today, so a count above zero is worth investigating. It will become an expected sight once lot transfers between workspaces ship.

Across the top of the page you'll find, depending on the batch:

• Edit details — correct the batch code or its federal permit; see Correct a batch's code or permit.
• Guided view — the step checklist, on a batch whose stages came from a recipe.
• Share what I made — appears once the batch is finished (released or archived); see Story pages.
• Back to batches.

Work a batch as a checklist

If a batch was started from a recipe, Brewstiller lays that recipe's process out as planned steps you tick off as you go. It's the same batch either way — the guided view is just a simpler way to work it on a brew day.

1. Open the batch and choose Guided view. (You'll already be here if you created the batch from a recipe.) The heading is the batch code, with its production type and Guided steps beneath it. While the batch is still Planned, this page also shows the Readiness panel — the same have/need check against your inventory described in Check what you have against the bill.
2. Under Steps, each planned step is a numbered card with a status badge — Planned, Logged, or Done.
3. On a step you're starting, choose Log this step. The Stage type is already locked to the step, and you can set a Vessel, Cooperage, and Started at, add Notes, and fill in any of the Readings (optional) — the fields depend on the stage (for a fermentation step: Gravity (SG), Gravity (°P), ABV (%), pH, Temperature (°C), Volume (L), and so on). A note under them says the step is saved first and the readings are recorded right after. There's no Operator or Bonded / tax-paid field here: starting a guided step is attributed to whoever clicks it, so on a commercial workspace an incomplete profile is caught after you save rather than blocking the button up front (see Operator on commercial workspaces below). While the batch is still Planned and hasn't been started yet, logging a step like this also shows a Start this batch too checkbox, ticked by default: logging the step also starts the batch right away, so it counts as active immediately. Untick it if you'd rather log the step without starting the batch yet — see the standing notice described below for what that looks like.
4. Some step cards offer more than the plain checklist, depending on the stage type:
   • A countdown timer, on time-boxed steps such as a mash rest, a boil, or a grain cook. Set the minutes and choose Start timer; it keeps counting down even if you navigate away. It's kept on your device only — it says so — so it won't follow you to your phone.
   • Add at this step, showing each ingredient the recipe calls for there with its own Record what you added button, so you can log the addition (which lot, how much) without leaving the checklist. Add another addition records one the recipe didn't call for.
   • Handy for this step, a link straight to the relevant calculator for what you're doing right now — a yeast starter, a gravity temperature correction, and others — see Tools.
   • The step's own reminder, if one is due for that stage, with the same controls as the Reminders card described later on this page.
5. On a step that's under way, two controls appear. One opens the same form with Ended at left blank, for adding detail without touching the step's end time — a mid-ferment gravity check, for example. It's labelled Add a reading on a stage type that takes readings, or Add a note on one that doesn't (milling, for instance). The other, End this step, finishes the step — an end time, readings, notes, all at once. That form opens with Ended at already set to right now, so Save changes is enabled the moment it opens: ending a step you're finishing this minute is one click. Change the time first if the step actually ended earlier, or choose End it now at any point to reset the field back to the current minute. Once a step has an end time recorded, Add a reading / Add a note goes away and only Edit this step remains — that form opens with the stored end time showing (not reset to now), for revising the details afterward. On a released batch, neither control appears — the step's end time, readings, and other production fields are locked once a batch is closed, and Edit this step's note replaces them: a notes-only fix for a typo, with nothing else editable. On an archived batch, no step control appears at all.
6. Something the recipe didn't plan? Under Something come up? choose Log an unplanned step — a nutrient addition, a pH correction, a topup. It joins the checklist marked (extra).
7. Choose Advanced view (top right) at any point for the full batch page — lineage, corrections, and everything else.

As you work, Brewstiller offers the next lifecycle move rather than demanding it: once every step is logged it offers Release batch — optional, you can keep the batch open as long as you like.

Starting is treated differently. If you leave a Planned batch with one or more logged steps but never start it — you unticked Start this batch too while logging (see step 3 above), or a step got logged some other way — both the guided view and the advanced view show a standing notice at the top saying how many steps are logged and offering to start it. The notice isn't dismissible and doesn't fade out — it stays until the batch is started. Your logged work is safe either way; starting only records the start time.

There are two versions of that notice, because there are two ways a Planned batch ends up with logged steps:

• You never started it. This is a genuine mismatch: the batch shows no start date in the batch list, and it isn't counted in Active batches on Home. The notice is highlighted and says the batch "has N logged stages but was never started", with a Start batch button.
• You started it and then reverted it to Planned (see Move a batch through its lifecycle). Nothing is wrong here — you made that change deliberately and recorded a reason for it — so this notice is plain rather than highlighted. It says the batch was reverted, shows when it was previously started, confirms your logged steps are untouched, and offers Start batch again for whenever you're ready to carry on. Leaving it Planned is a perfectly good answer; the only thing to know is that Home won't count it while it stays that way.

A batch with no recipe-planned stages shows No planned steps instead, with Open advanced view; you can still log steps as you go from either screen.

Beta — guided steps. The guided view is on by default during the beta but can be switched off per environment. If you don't see a Guided view button on a batch made from a recipe, it isn't turned on for you.

Write a tasting note

The Tasting notes tab is the batch's tasting log: dated notes in your own words, with an optional rating and a note of who tasted. Notes build up over batches into your own record of how a recipe evolves.

1. Open the batch and choose the Tasting notes tab, then find the Add a tasting note card.
2. Write the note in Tasting note — aroma, flavour, mouthfeel, how it compares to the last one. This is the only required field.
3. When you tasted it defaults to now. Change it to log a tasting from an earlier day — the date and time you enter is the one the note is filed under, not when you typed it.
4. Optionally choose a Rating (optional) — 1 of 5 through 5 of 5, or leave it on No rating — and fill in Who tasted it (optional), which is free text, so they don't need a Brewstiller account.
5. Choose Add tasting note.

Write as many notes on a batch as you like — it's a log, not a single verdict. Adding, editing, and deleting notes needs batch-editing permission; everyone in the workspace can read them.

Notes are listed newest tasting first, with Show older notes at the end of the page.

Each note has Edit and Delete:

• Edit opens the note with all its current values filled in. Everything in the dialog is saved as the note's new content, so clearing the rating or the taster removes it from the record — the dialog says so too.
• Delete asks you to confirm and can't be undone: the note leaves the batch's tasting log for good.

Your most recent note for a batch can also be shown to visitors on that batch's story page, if you tick Tasting notes under that page's exposed fields — see Create and publish a story page. Nothing here is public until you do.

Beta — tasting notes. This tab is new and can be switched off per environment, so if you don't see it on your batches it isn't turned on for you yet. Notes are your own producer record; the consumer-facing "leave a tasting note" surface on story pages — where a visitor writes one — is a separate feature that isn't built.

Log a stage

Stages are how you record what actually happened, step by step, on the Stages tab.

1. Open the batch and, on the Stages tab, choose Log a stage. The form heads Log this step.

2. Choose the Stage type (the choices match the batch's production type).

   If this batch has a planned step of that type that hasn't been started yet, Brewstiller logs that planned step instead of adding a separate, duplicate one — you'll see a notice above the form: "Logging the planned [stage] #N. Your draft has been replaced by the planned step's details; switching back clears it." This is what you want almost every time: it's the same step the guided checklist would have started. If you genuinely need to log a second, additional occurrence of the same stage type on this batch, choose Add another [stage] instead in that notice to go back to a plain new stage. Logging a planned step this way skips two fields you'd otherwise fill in here — Readings and, on a commercial workspace, Bonded / tax-paid — the notice says so and points at Edit to add them afterward.

3. Fill in the start details. Most are optional; on a commercial workspace Operator is required for regulated stages (see the note below):

   • Vessel (optional) — the vessel the stage runs in. Choose it from the list (search by vessel name), or leave it on No vessel.
   • Cooperage (optional) — the barrel or other cooperage the stage runs in. Choose it from the list (search by barrel identifier), or leave it on No cooperage.
   • Operator (optional) — the workspace member who started the stage. Choose them by name from the list (search by member name), or leave it on No operator. On a hobby workspace this is optional. On a commercial workspace, once you pick a regulated stage type the field is marked required (its label drops "optional" and gains a red asterisk) and the Log this step button stays disabled until you choose an operator — see Operator on commercial workspaces below. Offered here whether or not you're logging a planned step.
   • Started at (optional) — when the stage began.
   • Bonded / tax-paid — Not applicable, Bonded (in bond), or Tax-paid (determined). This matters for commercial spirits segregation. Not offered when you're logging a planned step (see step 2 above) — add it with Edit afterward.

4. Under Readings (optional), enter any that apply — mash temp, gravity, ABV, cut-point proof, gauge proof, temperature, volume, and so on. Fill in only the readings relevant to the stage. Not offered when you're logging a planned step (see step 2 above) — readings for a planned step go on when you End this step afterward.

5. Add any Notes.

6. Choose Log this step. The stage appears on the timeline, newest activity in sequence.

If something is missing or invalid, Brewstiller doesn't save the stage and shows a message telling you what went wrong. The wording comes straight from the form's checks and can read plainly rather than conversationally.

Operator on commercial workspaces

Commercial plan. This applies to the advanced Stages tab's Log a stage and Edit a stage forms — not to starting a step from the guided checklist, which has no Operator field at all (see Work a batch as a checklist above). On a commercial workspace, a regulated stage can't be recorded without an Operator. Brewstiller now tells you this up-front: as soon as you choose a regulated stage type the Operator field is marked required and the Log this step button stays disabled until you choose an operator, so you find out before you try to save rather than after. (If the requirement is only detected at save time — for example the workspace switched to commercial mid-edit — you'll see a plain message right under the Operator field asking you to choose the operator.) Regulated stages are the production, storage, processing, and release events TTB rules cover:

• For a distillery, that's effectively every stage — mash/cook, fermented wash, strip and spirit runs, maceration, filling, ageing, blending, proofing, filtering, bottling, and release.
• For a brewery or winery, it's Bottle, Release, and continuous-mixture top-ups.

Hobby workspaces have no operator-identification rule, so hobby users can leave Operator blank on any stage.

The Operator field is a searchable list of your workspace's members: click it and pick the person who ran the stage by name (start typing to filter). You no longer need to look up or paste a member id. (The Copy member ID action on the Members page is still there for other uses, but you don't need it to log a stage.)

The member you name as operator also needs a complete workspace profile — their full legal name and phone. If theirs is incomplete, Brewstiller refuses the stage with The operator's profile is incomplete. To fix it, open the Members page and choose Complete profile on that member's row, then enter their full legal name and phone (or ask an Owner or Admin, or the member themselves, to complete it — editing someone else's profile needs member-management permission), and assign them as operator. See Complete a member's profile in the Members, roles, and invites guide.

Each stage card on the timeline shows its type and sequence, its start and end times, any notes, and its Inputs and Outputs (what fed the stage and what it produced — quantities always carry their unit, and spirits show proof and proof gallons). Input and output quantities are shown in your workspace's preferred measurement units (see Settings → Measurement units); proof and proof gallons always stay in their required units.

The timeline is ordered by when the steps happened, not by the order you entered them — so if you log a step late, or backfill one you did days ago, it moves to its right place. A step you haven't started yet has no date to sort by, so it stays exactly where your recipe planned it; a batch created from a recipe, before you've logged anything, shows the plan's own order.

Edit a stage

1. On a stage card in the timeline, choose Add a reading (shown on a started stage that takes readings) or Edit; both open the same form. On the guided checklist, the same form opens from Add a reading, Add a note, End this step or Edit this step.

2. Update the Ended at time, the Readings, the Bonded / tax-paid status, or the Notes. Shortcut buttons next to Ended at fill it in for you — everything they enter is still editable afterward:

   • Same as started, for a step that took no time (a gravity check, a transfer).
   • +1 hour / +4 hours / +12 hours, for a step that ran a known stretch. These add up, so two clicks of +4 hours gives you eight — handy when you're writing up a step that finished hours ago.
   • End it now, for a step you're finishing right this minute.

   Same as started appears only while Ended at is empty, so it can never overwrite a time — one you've saved, or one you just built up with the + hours buttons. End it now follows the same rule, with one exception: on the guided checklist's End this step form, which opens with Ended at already set to right now (see Work a batch as a checklist above), End it now stays available too — there it's a reset, putting the field back to the current minute if you've since changed it. The + hours buttons stay available so you can keep adding to what's there. A step that already has a stored end time shows no shortcuts at all; clear the field and they come back.

3. If you change a compliance-relevant value (the end time or a reading), a Change reason field appears and is required — enter why you're making the change.

4. Choose Save changes.

Beta — recording a TTB gauge. For commercial workspaces set up for TTB filing, each stage card can also carry a Record gauge control for logging an official gauge against the stage. This is currently in beta and switched off by default, so you may not see it yet.

Recording or voiding a gauge also needs your own complete workspace profile — your full legal name and phone — because the gauge names you as the responsible person. If yours is incomplete, Brewstiller refuses with Your workspace profile is incomplete. and offers Open Members, where you (or an Owner or Admin) choose Complete profile on your row.

Record what a stage drew from

An input is what went into a stage — the grain you drew from a lot, the spirit you blended in from another batch. Recording inputs is what builds a batch's lineage.

1. On a stage card in the timeline, choose Record inputs. On the guided checklist every step card carries a way to record inputs: Record inputs, or — on a step whose recipe lists ingredients — Record what you added, prefilled from the recipe. Either way the card says that what you record fills the batch's Lineage tab. On the guided checklist, a blending step opens Source type already set to Another batch's output (blend): directly on Record inputs, or, on a blending step with recipe ingredients, on a blank row beside the prefilled ones.
2. Choose the Source type:
   • Ingredient lot — a lot you received into inventory.
   • Another batch's output (blend) — an output recorded on another batch's stage that still has quantity left.
   • External purchase — a one-off purchased material (see Track ingredients and inventory lots).
   • Received in bond — a confirmed incoming transfer in bond. Commercial workspaces set up for transfers in bond only.
   • Not from a lot — hobby workspaces only (see below).
3. Pick the specific source from the list that appears — Ingredient lot, Batch output, External purchase, or Received-in-bond record, depending on what you chose.
4. Enter the Quantity drawn and its Unit. Drawing from an Ingredient lot always uses that lot's own recorded unit — there's nothing to choose. The same is true of an External purchase that was recorded with a unit. An external purchase recorded with no fixed unit (one priced by the whole purchase rather than a per-unit amount) lets you choose the unit for this draw, and that list includes weight as well as volume — g, kg, lb, and oz (labelled oz (weight), so it isn't mistaken for fluid ounces) — so a sack of grain you bought as an external purchase can be drawn in the unit you actually weighed it in.
5. On spirits, add the Proof (optional).
6. Choose Record input, or Cancel to back out.

If there's nothing to draw from, Brewstiller says so and tells you what to do first — for example No active lots to draw from. Receive a lot in Inventory first., or No external purchases recorded. Record an external purchase in Inventory first.

Recording an addition with no lot behind it (hobby workspaces)

On a hobby workspace, Not from a lot lets you log an addition even when you haven't received it into inventory as a lot — honey stirred in from the kitchen cupboard, a handful of spices, a gift from another brewer. Choose it as the Source type, then fill in Ingredient (optional) (pick from your ingredient catalog) and/or Description (optional) — at least one of the two, so there's always something identifying the addition. There's no lot to pick and no Proof field on this source; the Unit is yours to choose (weight or volume), usable straight away — no need to receive a lot first. If you have no active lots for the ingredient, the form opens on Not from a lot for you, and the quantity (and, on Not from a lot, the ingredient) already filled in from the recipe stays when you change the source.

The addition still shows up in the stage's Inputs list, labelled No lot with whatever you named it, and it still counts toward the stage's total quantity. Two things it does not do: it doesn't appear on the Lineage tab's provenance graph (there's no lot to trace back to — see below), and its cost isn't counted, so the batch's cost reads as possibly incomplete.

This source isn't offered on a commercial workspace — commercial batches keep full lot traceability for every addition.

Record packaging output (brewing)

When you package a brewery batch, record how much finished beer came off the line. It's what the brewer's report counts as produced, and it's what lets a packaged volume feed anything downstream.

Where it appears: on a brewery batch, on the stage card for a Brite packaging, Keg, Can, or Bottle stage. Other production types and other stages don't offer it.

1. On the stage card, choose Record packaging output.
2. Enter the Volume packaged and choose its Unit — litres, US gallons, barrels, and the rest. It must be more than zero.
3. Optionally record the container count as well: Containers filled (optional) and Container type (Bottles, Cans, Kegs, Growlers, Crowlers, Casks, or Bag-in-box). These two go together — enter both, or leave both blank if you only know the volume. Leave Container type on Not recorded to skip it.
4. Choose Record output. You'll see Packaging output recorded. and the volume joins the stage's Outputs.

If this batch already has a packaged volume recorded on another stage, the form says so before you save. The brewer's report adds every packaging stage's volume together, so record here only if this is additional beer — not the same beer moved from a brite tank into kegs.

Recording output needs stage-editing permission.

Move a batch through its lifecycle

Use the Lifecycle actions card. Only the moves that are valid from the batch's current state are shown.

1. To advance a batch, choose the forward action offered — for example Start batch (Planned → In progress) or Release batch (In progress → Released). Forward moves take effect immediately.
2. To undo a saved state — Revert to planned or Reopen batch — Brewstiller opens a dialog asking for a Reason (reverting a lifecycle state is a compliance-relevant change). Enter a reason and choose Confirm.

If the batch is Planned but already has logged stages, the start action moves up into the standing notice near the top of the page (see Work a batch as a checklist above) rather than appearing twice — as Start batch if it was never started, or Start batch again if you reverted it. Either way the Lifecycle actions card says where the action went and keeps Archive batch.

Reverting a batch to Planned keeps its original start date as history; the batch list still shows it, and the notice at the top of the batch page repeats it as "Previously started".

If the batch's state changed elsewhere while you had the page open, Brewstiller reloads the latest state and asks you to try again.

Work with a batch's reminders

Reminders are the batch's dated nudges — a racking, a nutrient addition, a check-in. Some are set up for you when the batch starts, from the recipe's schedule; you can also add your own at any time, on any batch (see Add your own reminder). They live in the Reminders card on the batch page, and on the step cards in the guided view.

1. Open the batch and find the Reminders card.
2. Each reminder shows what it's for and when it's due, tagged Overdue, Due today, Upcoming, or Snoozed.
3. Act on it:
   • Done — you did it; the reminder closes.
   • Skip — you're not doing it; the reminder closes without being done.
   • Snooze 3d — push it out three days.
   • Remind me in… — set your own delay. Enter a number, choose the Unit (minutes, hours, or days), and choose Set. A line beneath previews the new due time. Choose Cancel to back out.

The two controls count from different starting points, on purpose:

• Snooze 3d counts from the date the reminder is already due, so it always pushes the reminder later — never earlier. Once a reminder is due or overdue it counts from now instead.
• Remind me in… counts from now, so "3 days" means three days from this moment. That is what you want mid-batch — "remind me in 90 minutes" while you're watching a step. The line beneath the field previews the exact date and time before you choose Set, so you can see where it will land.

Notifications go out when the next reminder check runs, so they can arrive a little after the due time. For a step you're watching right now, use the step timer in the guided view instead.

A batch shows No reminders on this batch when its recipe carried no schedule, or when you've completed or skipped them all. You can still add your own from that card.

Add your own reminder

A batch you started without a recipe has no schedule, so nothing is set up for it automatically — and even a recipe-backed batch will not have thought of everything. Add a reminder yourself from the same card:

1. Open the batch, find the Reminders card, and choose Add reminder.
2. Fill in What to do — the words you'll see on the reminder, in the bell, and in the email ("Punch down the cap", "Rack off the lees").
3. Pick a Category if one fits (Punch down, Rack, Top up, Taste or check, Add nutrient, Bottle). It groups the reminder; it is not what you'll read. Leave it on General reminder if none fits.
4. Set Due — the date and time, in your own time zone. There is no default: choosing the moment is the whole point, so nothing is filled in for you.
5. Choose Add reminder.

The new reminder joins the list and behaves like any other — Done, Skip, Snooze 3d and Remind me in… all work on it, and a batch reminder you added is never re-dated or removed when a recipe's schedule is applied again.

A few things worth knowing:

• You can add the same kind of reminder more than once. "Punch down twice a day" is two reminders, and adding a second Punch down does not replace the first.
• A due date in the past is allowed. The reminder is added and shows as Overdue straight away — useful when you're catching up on something you already owed. Brewstiller tells you the date is in the past before you save, so a mistyped year is easy to spot.
• Notifications still go out on the next reminder check, not at the exact minute you chose.

See what you have already handled

Choosing Done or Skip does not erase the reminder. Beneath the live list, Completed and skipped expands to show each closed reminder with what you did and when. It stays collapsed until you open it, and it does not appear on a batch where nothing has been closed yet.

Reopening a closed reminder is not available yet.

See reminders across all your batches

The Reminders entry in the sidebar, under Batches, lists every open reminder in your workspace — so you do not have to open each batch in turn to find out what needs doing.

Reminders are grouped Overdue, then Due today, then Upcoming; reminders on a batch that has been released or archived sit last, under Batch closed. Each one names the batch it belongs to and links straight to it, and carries the same Done, Skip, Snooze 3d and Remind me in… controls as the batch page — so you can clear the list without leaving it.

The page shows Nothing open when no batch has a reminder waiting. You can also add your own reminders on any batch's page.

Unread reminders and other notices also collect under the bell in the top bar — see Your dashboard. The bell shows notices the reminder check has already sent out, so a reminder that has only just come due may not be under it yet — the Reminders page is the complete list.

Correct a batch's code or permit

Prerequisite: the batch must not be archived.

1. Open the batch and choose Edit details. The Edit batch details dialog opens.
2. Change the Batch code, or the Federal permit on a commercial workspace.
3. Once you've changed something, a Reason for this change field appears. Fill it in.
4. Choose Save changes.

The dialog's fields stay read-only for a moment after it opens, while Brewstiller checks whether your workspace is under a litigation hold. If that check can't be completed, the dialog says so and offers Try again; the form stays read-only until the check succeeds. While a litigation hold is in place the fields stay read-only until the hold is released.

A batch code can be changed but never cleared — clearing it would leave the batch identified only by its internal id, so Brewstiller refuses. On a commercial workspace, a federal permit that's already set can be switched to another covering permit, but not removed.

A batch's production type and its lifecycle state aren't changed here: stages are corrected on each stage card, and the state moves through the lifecycle actions.

Archive a batch

Archiving soft-deletes a batch — it's a tombstone, never a hard delete, so the record is preserved.

1. On the Lifecycle actions card, choose Archive batch.
2. In the dialog, enter a Reason (required) — for example, Duplicate batch created in error.
3. Choose Archive batch to confirm. You're returned to the batches list; the archived batch no longer opens from a direct link.