WorkflowQuality Control Laboratory

Certificate of Analysis (CoA) Generation

CoA generation that pours one approved result set into each certificate a batch must receive, rounds every value by that specification's own rule, and blocks any line that does not meet the revision in force before the QA head signs.

See one batch's three certificates drawn line by line ↓
Watch with transcript →
The problem

The impurity result that meets one market and fails the other

A drug substance batch is tested once and then needs a certificate for each client specification it ships against: one per market the client sells in, a copy for the client's tablet maker, sometimes another for a filing. Each specification has its own revision, effective date, limits and rounding rule. The coordinator copies results from LIMS into a template per client and rounds by hand, and QA checks the copy against the specification binder.

The costly errors are quiet. Nothing re-reads the allocation when a market's limit is tightened after the batch was promised to it. A template prints conforms where the specification asks for a number, or a dash where no test was run. A tablet maker's own incoming limit is tighter than the client's specification. Each one is found by the receiving reviewer, on receipt.

Built forQC release coordinatorsPlant QA headsQA specification stewardsProduction planners

The Problem Today

A batch tested once needs a certificate for each client specification, and each one rounds, reports and limits differently.

Two
decimals for impurity results below 1.0% (ICH Q3A) published

Copied and rounded by hand

  • Templates
  • Binders
  • LIMS prints
  • Emails
  • Revisions after allocationA limit tightened after the batch was allocated goes unseen
  • Rejected on receiptThe client's reviewer or tablet maker finds the mismatch first

The Solution

  1. One result set, each specificationApproved results poured into each client's certificate line by line
  2. Printed by each certificate's ruleEach value reported the way its own specification asks
  3. A not-met line stops its certificateA result over one market's limit blocks that certificate and no other
  4. The client chooses the marketAsked in fixed fields; the QA head approves what was measured

Built-in controls

  • A not-met line can never print as conforms
  • No one approves a certificate they drafted
  • Nothing issues before disposition

What You Get

A client's quality unit can lean on each certificate, because every line cites its result, its limit and the revision in force.

  • Clients hear before receiptWhere a batch can go, asked before their own reviewer finds it
  • A new market is one more entryEach new specification joins the register, not a new template
  • Revisions apply on their dateOpen certificates and allocations follow each change
Features

CoA generation for one batch, three certificates and three rulebooks

One drug substance batch whose impurity result meets one market's specification and fails another's, followed from the agents' run to the approved certificate.

demoEvery batch, result, client and person shown is sample data.

  1. 01Certificate fan

    Customer specific certificates of analysis drafted from one result set

    • Each certificate drawn as it prints. The coordinator sees what each client receives, each line with its limit, result and verdict, before anything is sent.
    • Revision picked by effective date. The specification in force on the day comes from the register, so a revision taken after allocation is not missed.
    • Each agent's step and certainty on view. Seven agents show what they did and how sure they are, so the coordinator opens the flagged ones first.
  2. 02Not met

    A not-met line blocks the certificate and can never print as conforms

    • The result, limit and revision on one line. The QA head reads why a certificate stopped without opening a binder or the LIMS record.
    • Missing results requested from the lab. Where a result is missing, the QC lab gets a test request instead of a blank line on paper.
  3. 03Client's reviewer

    A challenger that reads each certificate as the client's incoming reviewer

    • The receiving site's own limits. A tablet maker's incoming particle size limit, tighter than the client's specification, is raised before a shipment comes back.
    • Its own team's slips caught. A water result rounded by the old revision's table is fixed and checked again before anyone signs.
    • Points only the client can settle. What the client must decide goes into the question to the client rather than into a guess.
  4. 04Market conflict

    Out of specification result raised against one market's specification

    • QA raises it after reading the results. QA signs the raise only after opening the result set, and each certificate printing that value then waits.
    • One question to the client, in fixed fields. The client learns where its batch can go, with record values only, before its own reviewer finds the mismatch.
  5. 05Issue gate

    Certificate of analysis approval held while an OOS on its result is open

    • The open OOS heads the issue list. A result still under the lab's Phase I check cannot reach an approved certificate for any market.
    • Its rules printed beside it. Each certificate shows the rounding and reporting rules it follows, with their sources, for the client's auditor.
  6. 06Client portal

    The client decides where its batch goes, in fixed answer fields

    • Reallocate or hold, send or not. The answer changes the case through fields and an attached instruction, not an email thread someone must retype.
    • Comments routed to a person, unread. Any comment the client types lands with a person at the CDMO; the agents neither read it nor act on it.
  7. 07Withdraw

    Market certificate withdrawn by the coordinator, signed with its reason

    • Agents propose, people withdraw. The allocation agent suggests the withdrawal after the answer; the QC release coordinator signs it from their own view.
    • The OOS stays on record. Withdrawing one market's certificate leaves the result on file against that market's specification.
  8. 08Phase I

    Phase I lab check signed by the QC laboratory head before the OOS can close

    • Data review opened first. The QC lab head signs only after opening the sequence review and the impurity calculation behind the value.
    • A suspected lab error keeps it blocked. That choice leaves each certificate printing the result on hold until a retest plan exists.
  9. 09Approved

    Plant QA approval first, issue only once the batch is dispositioned

    • Approval is not issue. The date of release comes from the disposition record, so no certificate leaves before QA dispositions the batch.
    • Reopening clears the approval. A reopened certificate loses its signature, and downloads carry an unsigned mark until QA signs again.

The coordinator who drafts a certificate can never approve it

Who builds, keeps and signs a plant's certificates.

QC release coordinators

Draft and check every certificate a batch must receive

  • Certificates drawn from approved results
  • Rounding done by each specification's rule
  • The client's reviewer played before sending
Plant QA heads

Approve certificates and raise an OOS against a market

  • Result, limit and revision on one line
  • Sampled bulk approval for clean certificates
  • Past send-backs proposed as rules
QA specification stewards

Keep each client specification by revision and effective date

  • Change notices read into register drafts
  • What each revision touches, before it applies
  • QA approval before any revision takes effect
Production planners

Allocate batches to client orders and markets

  • Allocations at risk flagged on their line
  • Approved rules that stop a risky allocation
  • The client's reallocation recorded once

The agents' own Market C draft printed water to the wrong decimals

Met on one market, not on the other

Impurity B at 0.12% meets NMT 0.15% on Market A and fails NMT 0.10% on Market C, tightened after the batch was allocated there.

Water rounded by the old table

The draft printed water as 0.2%; the revision in force writes its limit to two decimals, so the line now reads 0.21%.

A tablet maker's tighter limit

Particle size d90 of 64 µm against the tablet maker's own NMT 60 µm: inside the client's NMT 80 µm, still a rejection on receipt.

A certificate on a held result

A batch's methanol result is held under a lab incident, so both of its certificates are blocked and kept out of bulk approval.

demoSample data, from the working solution.

The allocation watcher drafts the question and moves no allocation

Seven agents draft and check; the quality unit and the client decide.

Result gatherer

Reads the approved result set from LIMS and its data review record.

  • Reads no unapproved result as final
  • Recalculates no lab result
Specification register keeper

Picks the revision in force for each certificate by effective date, and turns client change notices into register drafts.

  • Makes no revision effective without QA
  • Edits no client limit
Rounding clerk

Reports each result by the certificate's own rule: decimals of the limit, two decimals for impurities, solvents by name, particle size percentiles.

  • Rounds nothing before the final calculation
  • Rounds no limit
Line checker

Compares each reported value with that specification's limit and checks every listed test has a result.

  • Prints no conforms for a not-met or missing line
  • Fills no missing result
Certificate composer

Lays out each certificate with the fields ICH Q7 asks for, signature box empty.

  • Signs nothing
  • Fills no date of release before disposition
Allocation watcher

Reads order allocations against each revision and result, and drafts the client question in fixed wording.

  • Moves no allocation
  • Chooses no market
Client's reviewer

Reads each certificate as the client's incoming reviewer, the receiving site's limits and the agents' own errors included.

  • Accepts no draft from its own team unchecked
More screens

Certificates on a held result cannot even be ticked for bulk approval

Around the certificates: the queue, specifications by revision, orders, learned rules, the trail of signatures, and settings.

Approved, withdrawn and blocked, side by sideThe day's certificates with due dates and what stands before issue; clean ones are approved together after QA opens a sampled share of them.
What a revision touches, listed firstEach client specification by revision and effective date, with the allocations a tightened limit reaches and an incoming notice waiting for the steward.
An allocation the new limit no longer fitsOrders and allocations by market; the planner sees the batch that fails the revision on its own line, and only the planner records a change.
A ruling waiting to become a ruleRules learned from the QA head's past send-backs, and one proposed from this case that stops early Market C allocations once approved.
Phase I, OOS closure and approval in one trailEach opening, signature, withdrawal and agent proposal, stamped with person, time, reason and signature meaning; exportable with the evidence file.
Settings change only on the QA head's signatureBulk approval sample, due dates, the rounding default, reporting threshold, residency, retention and who signs for each plant.

demoSample data, from the working solution.

Which market a batch serves is the client's call, in fixed fields

Where the batch goesThe client chooses in fixed fields; the agents draft the question and move no allocation.
Approving a certificatePlant QA alone, once the signer has opened the certificate and its result set; never the coordinator who drafted it.
Whether a result is validThe QC lab head signs the Phase I conclusion, and plant QA closes the OOS.
When a revision takes effectLoaded by the specification steward from the client's notice, then approved by QA.
When a certificate issuesAt disposition, with the date of release taken from the disposition record.
A learned ruleProposed from a past send-back; in force from the day QA approves it.

CoA generation questions from QC and QA leads

What is CoA generation?

CoA generation builds the certificate of analysis each customer receives for a batch from its approved test results. Here agents draft each client's certificate from the approved LIMS result set, and round and check each line against that client's specification in force; plant QA alone approves.

What must a certificate of analysis contain under ICH Q7?

The name and grade, the batch number, the date of release and the retest or expiry date; each test with its acceptance limits and numerical results; the original manufacturer's name and address; and a date and signature from the quality unit.

How is a customer specific certificate of analysis different from a LIMS CoA?

LIMS approves a result against one product limit. Each client specification has its own revision, limits and rounding rule, so one water result prints with one decimal on one certificate and two on another, and one impurity result can meet one market and fail the next.

If a batch meets one market's specification and fails another's, what then?

The QA head raises an OOS against the failing specification, and every certificate printing that result waits for the lab's Phase I check. The client is asked in fixed fields where the batch goes, and the coordinator withdraws the certificate no longer needed.

How are results rounded on the certificate?

By each specification's own rule: the decimals of the limit as the USP general notices describe, impurity results below one percent to two decimals per ICH Q3A, and each residual solvent by name. Rounding happens once, after the final calculation.

When does a certificate issue?

Approval and issue are separate. Plant QA signs off the content; the certificate issues when the batch is dispositioned, and the date of release comes from the disposition record.

Can the agents change LIMS or an order allocation?

No. They read LIMS, the specification register, the document system and order allocations; none of those systems takes a write from them. Free text from the client is read by a person, never by an agent.

Bring one batch's
results and specifications.

Send one batch's approved results and the client specifications it ships against; we will draw each certificate line by line.