Preparing a batch's production tasks

A batch's brew sheet work only becomes production tasks once someone prepares the batch. Preparing is where you decide who does each part of the brew: who mashes in, who handles fermentation, who takes on a single step such as dry hopping. You need the Assign production tasks permission to prepare a batch.

Transfers, packagings, cleaning and maintenance and batch readings don't need preparing. They become tasks on their own, and preparing a batch only lets you choose who does them for that batch.

Which batches need preparing

Go to Tasks -> Production task assignment. The card at the top, headed with how many batches need their tasks preparing, lists every batch that is in progress, or planned to start within your look-ahead window (14 days by default), and hasn't been prepared yet. It shows each batch's drink, start date and status, with these buttons:

• The eye button opens the batch.
• Prepare tasks opens the preparation grid.
• Stop asking about this batch takes the batch off the list without creating any brew sheet tasks. The batch itself is untouched, and you can still prepare it later from its Production tasks tab.
• Delete this planned batch appears only for a planned batch whose start date has already passed, which is usually a brew that never happened. It deletes the batch entirely, along with its planned packagings, and can't be undone. If you still mean to brew it, change its planned start date instead.

The card shows up to eight batches at a time and says how many more are waiting.

You can also prepare a batch from its own page: open the batch's Production tasks tab and click Prepare production tasks.

A batch can't be prepared if it has no recipe, if its recipe has no stages, or if it has no start date. The grid explains which one applies.

Using the preparation grid

The grid shows all of the batch's brew sheet work before anything is created:

• All work on this batch at the top covers everything on the batch.
• Each stage category, such as Brewing or Fermenting, has its own row, with the recipe's stages beneath it.
• Under Other batch actions, rows for Transfers, Packagings and Batch readings.
• All turns covers every turn. On a multi-turn batch, there is also a column for each turn, with its planned date, so you can give turn 2 to someone else.

Click any cell to choose who does that work. Search for a person or group, and select them. Use Clear to take someone off a cell.

The more specific cell always wins. A stage row beats its category row, a category row beats All work on this batch, and a turn column beats All turns. A cell with no one on it takes whoever owns the row above it, shown faded, so you only need to fill in the cells that differ. Where nothing on the batch covers a cell, it shows who your assignment rules would give it to, or Varies by site or day if that depends on the day or the vessel's site.

Giving a single step its own task

By default, a stage is one task. To give one step, such as a dry hop addition, its own task and owner, click the stage's show actions button (such as Show 4 actions), then click Split out beside the step and choose who does it. The step gets its own task, dated by its own trigger rather than the stage's start. Transfers and packagings work the same way: show them and choose who does each one.

Steps the recipe always shows as their own task carry a pin icon. See Showing a recipe step as its own production task.

Saving

Click Show dates to see when each piece of work is due. The footer shows how many tasks will be created, how many are unassigned, and how many each person or group will get. Click Prepare tasks to create them.

The batch's tasks appear straight away on your team's production days, and the batch leaves the card.

Changing a prepared batch

Open the batch's Production tasks tab and click Edit assignments. The same grid opens with your earlier choices, and Save changes applies any changes to the batch's tasks. Tasks that someone assigned by hand keep their owner.

The batch's Production tasks tab

When production tasks are switched on, every batch has a Production tasks tab, which opens first. Once the batch is prepared, it lists every task on the batch with its kind of work, due date, status, progress and owner. On a multi-turn batch, each task is labelled with its turn.

Before the batch is prepared, the tab explains that its brew sheet work isn't tasks yet, and offers Prepare production tasks to anyone who can prepare it. If someone chose to stop asking about the batch, the tab says who and when, and offers Prepare production tasks anyway.

Showing a recipe step as its own production task

Some steps happen partway through a stage on a day of their own, such as dry hopping or cold crashing. To make a step its own task on every batch brewed from a recipe, rather than part of its stage's task:

1. Open the recipe.
2. Click the pin button on the step's row. It turns blue when the step is shown as its own task.

You can also enable Show as its own production task when adding or editing the step. You need the Manage recipes permission. The setting can be changed on any recipe version, including confirmed ones, and batches already prepared on that version pick up the change. Calculated variables can't be shown as their own task.

A pinned step:

• is dated by its own trigger, and appears as its own entry on the production calendar and the batch schedule;
• is owned by whoever owns its stage, unless you choose someone else for it when preparing the batch;
• no longer counts towards its stage's progress, so a stage whose steps are all pinned has nothing left of its own and shows as complete;
• keeps its setting when the recipe is copied or exported to a Breww recipe file.