A batch release form is the last check a finished batch passes before it can be sold: someone other than the person who made it reads the batch record, confirms every check was done and within its limit, that any problem was recorded and closed, that the labels and codes are right, and that samples and lab results, where needed, are in. Then they sign it off, and only then does the batch become stock that can ship. Until it's signed, it's on hold. Releasing every batch this way, not only the ones that look wrong, is called positive release. In the example below, a batch of taro chips passes eight checks and is released the day it's made, and an earlier batch is held overnight for one underweight bag, rechecked and released the next morning. Below is what the form checks, who signs, the two batches, what a hold means, and a free template.
The short version
- Every finished batch waits on hold until it's released.
- Release means: the batch record is complete and every check is within its limit.
- Deviations recorded and closed; labels, lot and best-by right; samples taken.
- Lab results back first, for products that need them.
- Someone other than the maker signs it off, with the date.
- Any "no" means the batch stays on hold until it's dealt with.
- TaroStack keeps batches on hold until they're checked and released. More below.
What the form checks
| Check | Why |
|---|---|
| Batch record complete, initials on every step | A step without initials might not have happened |
| Recipe version matches the approved one | A batch made to an old version is a different product |
| Every check within its limit | The limits are what make the product safe and right |
| Deviations recorded and closed | A problem fixed in the moment still needs a record |
| Labels right: product, allergens, net weight | A wrong label is a recall waiting to happen |
| Lot and best-by legible and matching | The code is how the batch is traced |
| Retained samples taken | So the batch can be checked later |
| Lab results back, where needed | Some products wait for a result before they ship |
The checks come from your own batch record and SOP; how those are written is in SOP template for food manufacturing, and what a batch record holds is in what is a batch record.
Who signs
The person who releases a batch should be someone other than the person who made it: the owner, a lead, or whoever is responsible for quality. In a two-person kitchen, that's the other person. What matters is a second pair of eyes on the record before the product leaves, and a name and date on the decision.
Two batches
Windward Roots, the made-up taro business I use in these examples, releases every chip batch before it can be picked:
| TC-1016 | TC-1009 | |
|---|---|---|
| Made | October 16 | October 9 |
| Batch record complete | Yes | Yes |
| Every check within its limit | Yes: fill weights 143 to 147 g | No: one bag at 140 g, below the 142 g limit |
| Deviations closed | Yes: 4 bags scrapped, recorded | Not yet |
| Labels, lot and best-by | Yes | Yes |
| Retained samples | 2 bags | 2 bags |
| Decision | Released October 16 | Held; 50 bags rechecked, 3 topped up; released October 10 |
The underweight bag on TC-1009 meant the run around it was suspect, so the batch stayed on hold while the bags packed before and after it were weighed again. Once the three light bags were topped up and the deviation was recorded, the batch was released. How a failed check is written up is in nonconforming product form, and how suspect stock is held in general is in hold and release procedure.
Get the template
Download the batch release form. One sheet per batch: the product, lot, date, recipe version, quantity and best-by; eight checks answered Yes or No; a decision that says "Ready to release" only when every check is answered and none is No; and the sign-off. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
A release form on paper doesn't stop anything. The batch is finished at four, the store wants it at seven the next morning, and the cases go on the truck while the form waits on the clipboard. If the form later says "hold", the product is already on a shelf, and nobody can say which cases left before it was signed.
How TaroStack does it
TaroStack makes release the gate, not a form filled in afterwards.
On hold until released. A batch can sit on hold until it's checked and released. Held stock is kept out of what's available to sell, pick or ship, so a batch that hasn't been signed off can't leave by accident.
The checks, on the batch record. Batch record forms carry your own checklist fields, tick boxes, numbers, text, choices and initials, with limits, so a fill weight below 142 g is flagged when it's entered. Every batch records its recipe version and the ingredient lots used, automatically, and printable batch-record forms carry sign-off.
And the record of who released it. Every movement is a permanent record of who, when and why. Retained samples come off stock as an adjustment with the reason "sample", by lot, and scrapped bags with theirs.
| The job | Clipboard | In TaroStack |
|---|---|---|
| Batch waiting for release | On a pallet, shippable | On hold, out of picking |
| A bag at 140 g | Written down, maybe | A field with a limit, flagged |
| Who released it, when | A signature, later | On the record |
| Samples and scrap | In a box | Adjustments with their reasons |
Batches, holds, batch records with your own fields and limits, and adjustments with reasons are on every plan, from $49 a month. The first 30 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.