The Anatomy of a Good Certificate of Analysis

A Certificate of Analysis is the document your customers see most often — and frequently the only output of your lab they’ll ever read. A sloppy COA undermines months of careful bench work. A clear, well-designed COA earns trust on first glance.

Here’s what a good one looks like.

The non-negotiables

Every COA, regardless of industry, should contain:

• Sample identity — a unique ID, customer-supplied name, lot/batch number, and receipt date.
• Specifications — the limits each test was evaluated against, in the same units as the result.
• Results — numeric value, unit, method reference, and a clear pass/fail indicator.
• Method references — citations to the SOP, USP/EP/AOAC method, or internal procedure used.
• Analyst & reviewer signatures — both the person who performed the test and the person who released the data.
• Issue date and a unique COA number — so revisions can be tracked.

Anything else is decoration. Decoration is fine; just make sure the essentials aren’t crowded out.

What to leave off

Equally important: things that don’t belong on a COA.

• Raw instrument printouts. Keep them in your records — don’t paste them into the customer-facing report.
• Internal commentary (“re-tested because Maria thought it looked weird”). That belongs in the audit log.
• Marketing language. A COA is a data document, not a sales sheet.
• Specs the customer didn’t ask for. Reporting against unrequested limits creates legal exposure if you fail one.

Pass/fail must be unambiguous

The single most common COA failure we see is ambiguous result presentation: a number shown without its spec, or a spec shown without units, or a “Conforms” tag with no explanation of what it conforms to.

Pair every result with its limit, on the same line, with the same units. If a result is out of specification, say so plainly — don’t bury it. For the full OOS side of this, see Handling Out-of-Spec Results Without Losing Your Weekend.

Revisions

If you reissue a COA, it must be obvious:

• Increment a revision number (Rev 02).
• Show the supersedes date.
• Briefly state the reason for revision in a footer or appendix.

Customers will tolerate a corrected COA. They will not tolerate a silently corrected COA discovered later in an audit.

Templating saves you

If your COA is generated from a Word doc that someone hand-fills each time, you have three problems waiting to happen: copy/paste errors, inconsistent formatting, and version drift between analysts.

A LIMS-generated COA pulls directly from validated data, applies a single approved template, and produces an identical document every time. The analyst’s job becomes review and release — not formatting. If you’re new to LIMS, What Is a LIMS, and Does Your Lab Actually Need One? covers when it makes sense to make the switch.

That’s how Aliquora handles COAs by default. See how Aliquora generates COAs.