A change control log is a list of the changes you've made to how you make things, each written down before it happens, with one question answered: what else does this touch? A new almond supplier looks like a purchasing decision. It can also change your allergen statement, if the new supplier's plant handles peanuts and the old one's didn't. Cutting the honey looks like a recipe tweak. It can change the nutrition panel and the shelf life. The log is where those knock-on effects are caught, by making someone list the checks and sign that they were done. Each row has what's changing and why, what it touches, the checks needed first, who approved it, and the first batch made the new way. Below is a log for a made-up granola maker with three changes in it, what to check for each kind of change, and the template.
The short version
- One row a change, raised before the change is made.
- Say what's changing, why, and what it touches.
- List the checks first: allergens, label, shelf life, cost, training.
- One person approves, and signs.
- Record the first batch or lot made the new way.
- Close the row only when every check is done.
- TaroStack keeps recipe versions and which batch used which. More below.
An example log
| No. | Raised | What is changing | What it touches | Approved | In effect from |
|---|---|---|---|---|---|
| CC-014 | Oct 20 | Almonds from a second supplier | Recipe HA-12, allergen statement, cost | Owner, Oct 27 | Batch 26306-1 |
| CC-015 | Nov 3 | Honey reduced from 6.5 lb to 6 lb a batch | Recipe HA-12, nutrition panel, shelf life | Owner, Nov 3 | Batch 26307-2 |
| CC-016 | Nov 12 | New 24 oz bag | Packaging, net weight on the label, case pack, price list | Open |
And the columns that do the work, for the first two:
| No. | Why | Checks before it went ahead | Done and verified |
|---|---|---|---|
| CC-014 | First supplier short until January | New supplier's allergen statement read: its plant also handles peanuts. Label reviewed. Cost recalculated | Yes, Nov 2 |
| CC-015 | Customer feedback: too sweet | Trial batch tasted. Nutrition panel recalculated. Two bags held for shelf life | Recipe and label updated. Shelf life check still open |
CC-014 is the row that pays for the log. The almonds were the same almonds. What changed was where they were packed, and that was on the supplier's allergen statement for anyone who read it. The check made someone read it before the first delivery was opened, and the label was reviewed before the first bag shipped.
CC-015 isn't closed, and the log says so. The recipe and the label are done. The shelf life check is waiting on two bags in a cupboard. An open row is a job with a name on it.
What to check, by kind of change
| The change | Check before it goes ahead |
|---|---|
| A new supplier for an ingredient | Its allergen statement and specification. Its lot coding. The cost |
| A different ingredient | Allergens, the ingredient list and its order, nutrition, claims such as organic or gluten-free |
| More or less of an ingredient | The ingredient order on the label, nutrition, shelf life |
| New packaging or size | Net weight on the label, the barcode, the case pack, shelf life in the new pack |
| A process change: time, temperature, equipment | Whether the product still meets your food safety plan's limits. Shelf life. Training |
| New equipment | Cleaning procedure, allergen changeover, training |
| A new product on a shared line | Allergens carried over from the other products |
The list is a starting point, not a standard. If you're audited, your audit scheme may have its own requirements for managing change: use its wording. For changes that touch a critical limit, see HACCP plan summary and HACCP validation template.
How to run it
- Raise it first. The row is written when the change is proposed. A log filled in afterward is a diary.
- Number it. CC-014 is easier to write on a batch sheet than a sentence.
- List the checks before approving. Approval means the list is right, not that the idea is good.
- Name the first batch. "In effect from Batch 26306-1" draws a line: everything before it was the old way.
- Close it when the checks are done, with a date and initials.
- Review open rows monthly.
A recipe change is also a new recipe version: see what is recipe management. A supplier change belongs on the supplier list too: see approved supplier list and new vendor form template. Reading a supplier's allergen paperwork is in supplier questionnaire template.
Get the template
Download the change control log. One sheet and a read-me: eleven columns from the change's number to done and verified, with the granola maker's three rows as examples. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The log says CC-014 took effect from batch 26306-1. That's only useful if the batch records agree. On the floor, the old almonds and the new almonds were both open for a week, and three batches used whichever sack was nearer. The log draws a clean line. The lots that went into each batch drew a different one, and no one wrote that one down.
How TaroStack does it
TaroStack records what each batch actually used, so the line is where it really fell.
Recipes have versions. The honey change is version 4, with its date, and every batch records which version it used.
A batch notes the lots it used, automatically. A batch that took almonds from the new supplier's lot says so, whichever sack was nearer.
Each delivery is a lot with its supplier, so "the first batch with the new supplier's almonds" is a search.
Batch records carry your own checklist fields, so a check a change calls for is recorded with the batch.
Every lot is traced to the customers that got it.
| The question | The log alone | In TaroStack |
|---|---|---|
| Which batch first used the new almonds | The batch someone wrote down | The first batch that took that lot |
| Which batches used recipe version 4 | From the date, roughly | Each batch's version |
| Who received those batches | Invoices | The recall report |
| Was the check done on that batch | A tick in the log | A field on the batch |
TaroStack isn't a change control system: it doesn't raise, approve or close changes. Keep the log. Recipes, versions, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
