Certificate of Analysis Template and Release Checklist

The certificate is the customer’s proof that the lot meets its specification, and buyers file it with the goods receipt note and quote its lot number in complaints. It must stand alone. Nobody phones the lab.

Customers also read the certificate against their incoming specification, which is why the lot number and the order reference matter more than any logo or border.

Header fields identify the product, grade, lot number, manufacture date, retest or expiry date, quantity shipped and the customer’s name and order reference, under a plain title. Plant address and contact line go above.

The body is a results table. Each row is one test. Appearance, specific gravity, viscosity, assay, moisture, pH and flash point are typical rows, though your specification decides the list and the order.

For every row show the specification limit, the measured result, the unit and the method code, because a viscosity figure means little without the spindle, speed and temperature. Cite ASTM, ISO or your in-house reference. Where a test is subcontracted to an outside laboratory, name that laboratory and attach its report number so the chain of evidence stays unbroken.

Report numbers as measured, to the decimal places the specification uses, and never round a result to bring it inside the limit, because that is falsification. Add a footnote when a limit comes from a customer agreement rather than your standard grade sheet, since the reader needs to know which document set the number.

Release is a decision. It needs its own record. Someone in QC confirms that every test has a result, that every result sits inside the limit and that the lot status has moved from hold to released. Check the retained sample is logged too. It proves what left the gate.

Then dispatch checks the physical load. A tanker needs its previous cargo confirmed, its wash certificate sighted, the seal number noted and the compartment chosen, while drums need every label read against the certificate.

If anything fails, the load stays. A late truck costs less than a rejected tanker sent back from the customer’s gate after hours in the queue and a sample failing at the receiving tank.

Hand typing invites transposed digits. Generate the certificate from the lot record, where the specification and the results already live, so it becomes a printout from a template. Approved signatures can be stored as an image against the quality person’s login, so a certificate prints already signed only after release has been recorded.

Some customers want a different layout or an extra test such as heavy metals, so keep one template per customer and let the lot record fill it.

Store each issued certificate as a PDF against the lot, so that when a complaint arrives eighteen months later you retrieve exactly what was sent. You never rebuild it from memory.

Take three recent shipments. Fill the template from the records you hold, marking every field you had to hunt for and every field you had to guess. Count the minutes each certificate took, from the last result to the signed page, because that figure is the cost of your current process.

Those marks show where your data is weakest, perhaps the test method, the analyst initials or the retest date that nobody ever recorded. Fix those gaps first. Then ask your customers’ receiving teams whether the layout answers the questions they put to every incoming drum or tanker, before you print it for every account.