The batch log

In a category with an adverse event reporting obligation and no rework step, the batch log is the difference between a contained incident and an unanswerable question.

One row, ten fields

Date. Product and formula version. Batch code. Batch size. The lot number of every raw material. Phase temperatures and mixing time. Cool-down additions and the temperature each went in at. Measured pH. Measured viscosity. Units produced and the fill check-weights. Who made it.

It reads long and it is one line on a prepared sheet, filled in as you go rather than afterwards.

Why it matters more here

Because there is no kill step and no rework. A problem discovered later cannot be fixed in the product, only bounded, and bounding it means knowing exactly which units share a cause.

Because raw material variation is a real failure route: different water content, trace impurities and particle size can alter pH, emulsion stability or preservative efficacy in ways that pass an incoming check. The lot numbers are how you find that afterwards.

And because MoCRA brings record keeping and adverse event reporting, so the log is an obligation as well as a practice.

The pH and viscosity columns

Worth singling out because they do double duty. They are the evidence that each batch was inside the specification the challenge test was run at, and they are the early warning of drift.

A slow pH movement across six batches is a raw material or process change announcing itself months before anything else shows, and it is invisible unless the numbers sit next to each other.

What it lets you answer

A customer has a bottle with a code on it and a question. What is in it, when was it made, which supplier lots, what was the pH, what else shares those lots, and where is the retained sample.

That question arrives rarely and without warning. Ten minutes with a good log, or an indefinite and expensive silence.

References