30-min call with RobBook a proof-of-concept call
Job 02 · QA and lab

// Co-packers · Certificates of analysis

A certificate of analysis for every lot, checked against that customer's spec first.

Every lot leaves a trail: line checks, your lab's results, an outside lab's micro report, sometimes a hold. Then QA writes the COA the customer wants, with its tests, its units and its limits. In a free AI proof of concept, AI drafts those certificates on copies of 20 to 30 lots you already released. Your reviewer, the person who knows your lot paperwork best, sets each draft beside the COA your team actually signed.

Book a proof-of-concept call30 minutes with Rob
Released lots
20 to 30
Lots it releases
None
Certificates it signs
None

// The one job

A lot's results come in. A draft COA goes to QA.

The same base product can ship to three brands under three specs: different moisture or Brix ranges, different micro limits, a different method named for the same test, and a different certificate layout each time. For every lot, someone in QA pulls the results together, checks each one against that brand's limits, notes anything retested or held, and types the certificate.

For the test, AI reads copies of the lab and production records and the customer specs for lots you already released, and drafts each COA in that customer's layout: every value from a record, every limit from the brand's spec, and the source named beside each line. A missing test, a result outside a limit, a method that differs from the one the spec names, or a lot still waiting on a result goes to your reviewer as a question. No lot is released, and no certificate is signed or sent.

Lot resultsLab and line records
Lot code
Production date
Outside lab report
Hold status
TestResultMethod
Illustration, not a real lot
Checked against
the brand's spec
Customer COADraft for QA
Customer item
Spec revision
Lot code
For signature
TestLimitResult
Illustration, not a real certificate

// What makes it hard

Why a lot's certificate is more than its lab report

Your test procedure and the brand's spec have to line up. Where product testing is one of your verification activities under FDA's preventive controls rule, the written procedure has to name the organism or analyte, say how samples are identified and tied to specific lots, set the number of samples and how often they are taken, name the test and its analytical method, name the laboratory, and include the corrective action procedure. A brand's spec often adds its own list of tests and methods. The draft lines the two up: each test the brand asks for, the record that answers it, and the method actually used, and it marks any requested test your procedure doesn't cover for that product.

Some lots wait on results before they can ship. Costco's published supplier addendum asks suppliers of high-risk ready-to-eat items, and of some that are not ready to eat, to run a finished goods test and hold program on a science-based sampling plan and to keep every lot under their control until satisfactory results come back. The same applies to any lot tested for pathogens because a buyer asked, a spec requires it or a regulation does. When a food-contact surface is tested for pathogens, every lot run over that surface since the last validated sanitation stays under the supplier's control until results are in. The draft shows each lot's hold status and any result still open, and never prepares a certificate for a lot whose results are not in.

A positive is a corrective action, not a line on a certificate. FDA's rule expects written corrective action procedures for a pathogen or indicator organism that product testing finds in a ready-to-eat food, and those procedures must keep affected food out of commerce unless it can be shown not to be adulterated. Records under the rule hold the actual values observed, with the plant, the date, the initials or signature of the person who did the work and, where it fits, the product and the lot code, which the rule defines as the plant's own code for a period of production. So the draft carries the recorded value wherever the record has one, ties it to your lot code and the brand's item, and passes anything out of limit to QA in the record's own words.

The product decides which tests count and how often. For an acidified food whose finished equilibrium pH is above 4.0, FDA's rule calls for a potentiometric measurement, meaning a pH meter, and its processing records are kept for three years from the date of manufacture. A bottling plant analyzes a representative sample of each type of bottled water for total coliform at least once a week, following up for E. coli when coliforms turn up, and runs chemical, physical and radiological analyses at least once a year. A weekly or yearly result can stand behind a lot's certificate only as what it is, so the draft labels every value with the date and sample it came from.

What your reviewer watches. Usually the QA manager or the lab lead who signs certificates today. They check that each draft names the right brand item, spec revision and lot code; that every value matches its record and every limit matches that brand's spec, in the same units; that no held lot or open result reached a certificate; and that each out-of-limit, retested or reworked result went to a person instead of onto the page.

// What you send

Lots your QA team already released

Copies only
No lab system login
01

20 to 30 released lots

Lots already shipped, each with its production record, line checks, your lab's results and any outside lab reports. Include a lot that was held, retested or reworked.

02

The brands' specs behind them

Each customer's finished product spec at the revision that applied, with its tests, limits, methods and units, plus any COA template the brand requires.

03

The certificates your team signed

The COA that went out for each lot, exactly as sent. Those certificates are the answer key.

04

Copies, after the NDA

The NDA is signed before any record moves. We never log in to your lab system, your ERP or a customer portal. If records can't leave the plant, your reviewer helps us build look-alikes with the same tests and the same quirks.

// Before it starts

Agreed before the first lot is copied

The owner and your reviewer settle these in writing.

COA test termsOwner signs off
Your reviewer
Named by the owner, often the QA manager or the lab lead
Success criteria
Written down: which values, limits, units and holds must match
Lots
Picked by your reviewer, across brands and products, with at least one held lot
Release and signature
Stay with your qualified people, never the draft
Price
A range for live COA drafting, given before any lot record is shared
NDA
Signed first

// How the test is judged

The certificate you signed, beside each draft

Lot by lot
against what QA sent
On the same 20 to 30 lotsThe COA your team signedThe AI draft
Brand item, spec revision and lot code matchedFilled in on your lotsFilled in on your lots
Every value traced to a lab or production recordFilled in on your lotsFilled in on your lots
Every limit and unit taken from that brand's specFilled in on your lotsFilled in on your lots
Methods checked against the ones the spec namesFilled in on your lotsFilled in on your lots
Held lots and open results kept off the certificateFilled in on your lotsFilled in on your lots
Out-of-limit, retested and reworked results passed to QAFilled in on your lotsFilled in on your lots
Lots that needed a person before the certificateFilled in on your lotsFilled in on your lots
No marks yet. Every cell waits for lots from your own plant.Your reviewer scores both sides and makes the call.

// After a yes

About 30 days on lots as they finish

Once your reviewer says yes, each new lot's certificate is drafted the same way for about 30 days.

Every draft waits for your QA manager to review and sign it, and no lot moves on the draft's word: release stays with the people who release lots today.

The comparison continues on live lots, and nothing else is added until the month ends.

// Later, one at a time

What could follow lot certificates

Possibilities to weigh
Each priced on its own
  1. 01

    Customer specs into your plant's records

    New brands' formulas and specs drafted into your spec format, a label review list and an allergen record for QA and R&D.

    Next
  2. 02

    Customer quality questionnaires

    A brand's yearly questionnaire or audit packet answered from your own records, each answer tied to a file, for QA to finish and sign.

    Then
  3. 03

    Formula and label change notices

    Brand revisions matched to open orders, packaging on hand and the specs they touch.

    After that

// One hard limit

It never releases a lot or signs a certificate.

Every value on a draft comes from your records and every limit from the brand's spec. The test never approves a formula, a label, a specification or a lot, never decides whether a food is safe, compliant or allergen-free, never signs a certificate or a questionnaire, and never contacts a customer, a supplier or an auditor. It works only on copies of lots already released. A qualified person on your team decides and signs.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

The range comes on the call, once Rob knows how many lots you release a month, for how many brands, and how many certificate layouts your team keeps.

// Questions

Certificate of analysis questions

Does it decide whether a lot passes?
No. It sets each recorded result beside the brand's limit and shows where they disagree. Whether the lot ships, is held or is reworked stays with your QA team.
Each brand wants its own COA layout. Is that a problem?
No, that is what the test checks. Send the template or a signed example for each brand, and the draft follows it. Your reviewer compares each draft with the certificate you actually sent.
We send micro testing to an outside lab. Can it read their reports?
Yes, from copies. The draft takes the result, the method and the sample identity from the lab's report and names that report beside the value. A report that doesn't tie clearly to one of your lot codes goes to your reviewer.
Can it sign or send COAs for us?
No. The draft waits for the person who signs certificates today, and during the test it never reaches a customer or a portal. In a live run your QA manager still signs and sends every one.
What if a brand's spec names a different method than our lab uses?
The draft marks the difference and doesn't treat the result as a match. Your QA and lab people decide whether the method is acceptable or the brand needs to agree to it.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Test it on lots your team already released.

A 30-minute call with Rob: your plant and your role, the products and brands your certificates cover, and about how many lots you release a month. Lab records stay with you until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.