In many plants, a test result is written down or exported from the instrument, retyped into a spreadsheet, checked against the spec by eye, and retyped again into a COA template. Each copy is a chance for a transcription error, and finished lots wait while the paperwork catches up. None of those steps adds information. They move it.

What goes on a COA

Customers differ, but most certificates carry the product name and code, the lot or batch number, manufacture and expiry or retest dates, each test with its method, the specification limits, the result with units, a pass or fail statement, and the name and date of the person who approved it. Some customers require their own format, extra tests or tighter limits than your internal spec. List those requirements per customer before you automate, because they decide which template and which limits apply.

Get results out of the instruments once

Results usually live in one of four places: instrument software that can export a file, a LIMS, a lab spreadsheet, or a paper notebook. Each can be handled:

  • Instrument exports and LIMS: read the export or the LIMS interface directly, so the number that reaches the COA is the number the instrument produced.
  • Spreadsheets: a consistently structured sheet can be read as it is. Where every analyst keeps their own layout, a simple entry screen is usually faster than fixing the sheets.
  • Paper: needs a capture step, such as a tablet form at the bench, before anything else can be automated.

Standardize test names and units across these sources early. “Moisture”, “H2O %” and “LOD” on three instruments for the same test is a common reason automatic checks fail.

One controlled source of specifications

Automatic checking is only as good as the limits it checks against. Keep spec limits in one controlled place, by product and grade, with customer-specific limits where they exist, and change them through your document control process. Agree the rounding and reporting convention before comparing results to limits. For regulated products, follow the convention your quality system or compendium specifies.

Check every result, and route the failures

When a result arrives it is compared with its limit. Passing results move on. Out-of-spec results are flagged to QA straight away, with the result, the limit and the sample details, and they follow your existing investigation procedure. In pharmaceutical manufacturing, FDA’s guidance on investigating out-of-specification test results describes what that investigation involves. Borderline cases, such as a result exactly at a limit or an incomplete set of tests, should always go to a person.

Draft the COA, then let QA decide

Once a lot has a complete set of passing results, the COA is generated from those results, in the right template for the customer. It is a draft until an authorized person approves it. The same person, or your release process, decides whether the lot is released. Automation should never release a lot or send a certificate on its own.

If you make FDA-regulated products, the records and signatures in this workflow may be electronic records under 21 CFR Part 11, and the system that holds them may need validation. Find out what that involves before you choose tools, not after.

Send it with the shipment

An approved COA attached to the lot record can travel with every shipment of that lot automatically, as part of the shipment notification. That closes the most common customer complaint about certificates: that they arrive late, or not at all.

What to measure

  • Time from test complete to lot release.
  • Transcription errors found in audits and reviews.
  • COAs corrected or reissued after sending.
  • QA minutes per COA.

Take a baseline for each before changing anything, so the effect is measured from your own records.

A short readiness checklist

  • A list of where every test result lives today.
  • Controlled spec limits per product, and per customer where they differ.
  • Agreed rounding and reporting rules.
  • COA templates and customer requirements written down.
  • A named approver and a release procedure that stays with QA.

These steps match the lab test capture and certificates of analysis workflows in our library.