In this guide 6 sections
Formula changes need a revision trail. A small untracked tweak, such as a changed dose of additive, shows up weeks later as an off spec batch or a complaint. A revision record names what changed, who approved it, when it took effect and which batches used it, so nothing lives in one chemist’s head.
How an untracked tweak becomes a complaint
A shift chemist sees a coating batch running thick, adds a little extra solvent to thin it, and the batch passes the viscosity check. Nobody writes it down.
Three weeks later the same product dries slowly on a customer’s line, and the customer sends photos and a retained sample to your quality team. The master formula looks untouched. Nobody can explain the drying fault.
The formula did change, but only in one person’s head, and without a trail your team spends days guessing while the customer loses patience long before the cause appears.
What a formula revision record should hold
Treat a revision as a dated, approved copy. A revision holds every ingredient with its quantity and unit, the order of addition, temperature, hold time, mixer speed and viscosity check.
It should also hold the reason for the change, the person who proposed it, the person who approved it and the first batch that will use it. The reason matters most. Months later it tells you whether to repeat the change or reverse it, long after the proposer has left or forgotten.
- Revision number and effective date
- Changed lines highlighted against the previous revision
- Reason, proposer and approver
- Trial batch result before full release
- Customers or grades affected
Link every batch to a revision
The trail only works when each batch records its revision, so the system pulls the current approved revision the moment an operator opens a batch and locks it. Nobody types quantities from memory.
Planned and actual figures sit side by side. If the actual dose of a pigment differs from the formula, that variance is saved with the batch, along with the reason given on the floor.
Now the complaint has an answer. Search the customer’s lot, read its revision and variance, then compare both against lots that went well, and the difference between them usually points at one changed line.
Handle trials, temporary changes and approvals
Not every change is permanent. A supplier’s solvent may need a temporary adjustment for one delivery, so mark it as a temporary revision with an expiry date and the solvent lot it applies to.
Trials run under a draft revision that the floor may use only with R&D sign-off, and a passed trial turns the draft into an approved, numbered revision.
Never overwrite an old revision. Regulators and large customers sometimes ask what you made three years ago, and a clean read-only archive lets you answer in minutes instead of days.
- Draft, approved and retired states
- Temporary changes with an end date
- Sign-off by R&D and QC before release
- Read-only archive of old revisions
Start with your five most complained about products
Do not rebuild every formula at once. Choose the five products with the most complaints or rework, enter their current formulas as revision one, and freeze the shared spreadsheet copies that circulate on the floor.
From today any change goes through the revision step, however small, and after a month you review how many changes were made that nobody would have recorded before.
That number is usually a surprise. It shows how much lived in memory.
Formula revision request form
A one-page form. Blocks cover product and grade, revision number, and each ingredient line changed with its old and new quantity, plus the reason for the change. The trial batch and result, signatures from R&D and QC, the effective date and the affected customers fill the remaining blocks of the form.
Open a blank worksheet to printQuestions owners ask
Is a revision trail only for regulated products?
No. Any plant that has had a complaint it could not explain benefits from a revision trail, and regulated products simply make the record compulsory.
Who should approve a formula change?
Require one person from R&D or formulation and one from quality, and for named-customer products add a commercial contact who hears before the change goes live.
What if the floor needs to adjust a batch urgently?
Allow an in-batch correction with a reason code saved on the batch record, because a one-off fix is a variance and not a new revision unless the correction repeats. Log it either way.
Can a spreadsheet hold the trail?
For a few products, yes, provided one person controls the file and nothing is ever overwritten, but as products multiply, linking batches to revisions by hand becomes unreliable.