Specifications

Your specification, reviewed or built from scratch.

Two ways in. Have a spec? Get an independent written opinion on whether it holds up, at the depth you choose. Need one? Send your product basics and we build a defensible specification, with methods fit to detect what it sets.

Why this matters nowThe #1 supplement finding

For more than a decade, the single most-cited FDA inspection finding for supplement makers has been the same one: failure to establish or verify product specifications under 21 CFR 111.70(e). It was the top Form 483 observation again in 2023 and 2024.

FDA Form 483 inspectional-observation data, FY2023 and FY2024 · 21 CFR 111.70(e), the most-cited dietary-supplement finding
What this is

Whether your specification holds up, against the rules and against what backs it.

A specification is the set of limits and methods that defines what your product is and proves it conforms. It can be raw-material, finished-product, or in-process. We judge the one you hold, or build the one you’re missing, against the compendial and regulatory requirements and against your own records. That means more than checking whether the limits and methods read correctly. It means checking whether the spec reconciles to your manufacturing record, whether your data meet it, and whether the methods can detect what the spec sets.

Specifications Opinion Letter

An independent regulatory opinion on a specification you already have: does it hold up? Start at the base, and add a record to take the opinion deeper.

What this covers
  • Raw-material / ingredient specifications
  • Finished-product specifications
  • In-process / control-plan specifications
  • Identity & purity (USP / compendial)
  • Contaminant & heavy-metal limits
  • Banned-substance screen
  • Supplier spec adequacy
  • Test-method fitness for specified limits
What you get back

A signed written opinion. File it in your quality system, hand it to an auditor or a customer, or use it to fix a gap before an inspection instead of after. Each limit and method is read against the rule and the compendial requirement, with a clear conclusion and what it would take to address it. Not a label check that never looks at the spec, not spec software that stores it without judgment, and not the consultant grading work they helped write. A fixed-price independent read that surfaces the spec that reads complete and falls apart the moment someone asks what backs it.

What a review catches

A worked specification, and what the base review alone surfaces.

This is the $950 base: the spec read on its face, before a single other record. Hover or tap a marker to read the finding. The deeper add-ons bring in the records that catch what a spec sheet alone can’t.

Constructed teaching example, disclosed as constructed. The full story lives on the case.
See the full High Desert / GMPure™ case
Constructed teaching example
HIGH DESERT BOTANICAL EXTRACTS · GMPure™
Finished-Ingredient Specification
CBD Isolate — Bulk Dietary Ingredient
SPEC HDX-SPEC-204REV 3LOT ISO-2605-14
Intended use: Dietary ingredient for dietary supplements3 · for further manufacturing use.
AttributeMethodLimit
Identity & Purity
AppearanceVisualWhite cryst.
Identity (CBD)HPLCConforms
Assay, CBDHPLC≥ 98.0%
Cannabinoid Compliance
Δ9-THCHPLC≤ 0.3%
Total THC (Δ9 + 0.877×THCa)Not specified1
Residue & Contaminants
Heavy metalsUSP <232>Conforms
Residual solvent (ethanol)Not specified2
MicrobialUSP <2021>Conforms
✓ THC-FREE · 0.0% THC4
1No total-THC limit, the line that decides what this legally is
On the spec: a Δ9-THC limit of ≤ 0.3%, and no total-THC limit at all.
Lawful hemp is decided on total THC, Δ9 plus the THCa that converts to it. A spec that limits only Δ9 leaves the attribute that separates a hemp ingredient from a marijuana article unspecified, on a product whose extraction concentrates THC.
Standard · base7 CFR 990 · 21 CFR 111.70(b)
2No residual-solvent limit on a solvent-extracted ingredient
On the spec: the process uses ethanol extraction, and the spec carries no residual-solvent limit or method.
An ethanol-extracted isolate has to control residual solvent to a USP <467> limit. The spec sets none. The safety attribute the process most obviously creates is the one the spec leaves out.
Standard · baseUSP <467> · 21 CFR 111.70(b)
3A dietary-ingredient status the records don’t establish
On the spec: intended use stated as “dietary ingredient for dietary supplements.”
There is no NDI notification or GRAS determination on file, and CBD’s eligibility as a dietary ingredient turns on §201(ff)(3)(B). The spec states the status as settled where the records leave it open, a question for counsel that the spec should flag rather than answer.
Standard · baseFD&C §201(ff)(3)(B) · §413
4“0.0% THC” with nothing behind it
On the spec: a “THC-Free / 0.0% THC” representation on the face of the sheet.
There is no total-THC release limit and no validated method to support a zero claim. A “0.0%” that rests on a method purified to read below detection is a representation the data can’t carry.
Standard · base21 CFR 111.70(b) · FTC substantiation
What the deeper add-ons add
+Does the spec match how it’s made?
Reconciling the spec against the master manufacturing record needs that document. In the case, the process concentrates THC across a train the spec never gates. The consistency check.
Standard · + manufacturing record
+Do the data support the limits, and can the method see them?
The certificate of analysis is what proves or breaks it. In the case the total-THC number was computed on the wrong basis, Δ9 only, omitting the THCa factor, using a method only verified, never validated.
Exceeding · + certificate of analysis
+Was the lot made to the spec?
The batch record answers it. In the case the extraction train ran as one step with no in-process total-THC gate, so the spec’s limits were never checked where THC concentrates.
Exceeding · + batch production record
Build your opinion
Standardthe baseline the field expects
Included
The specification, on its face$950
Judges the specification against the rules and the compendial requirements as written: the parameters, limits, identity and purity, contaminant and banned-substance limits, and whether each limit is tied to a method that can detect it. Whether the spec is complete and defensible on its face.
You send: The set of limits and methods that defines what the product is and proves it conforms: identity, purity, contaminants, and the tests for each.Also called: product spec, finished / ingredient specification, release specFull details on the Records page
Optional add-on · tap to add
Matches the product’s own documentation+ $550
A spec that doesn’t match your own records is a finding waiting to happen. We reconcile it against the upstream document that defines it, your master manufacturing record and formulation, so the number you set is the number your own paperwork supports.
You also send: The document that defines how the product is made: the formulation and process the specification has to reconcile against.Also called: MMR, master formula, master batch recordFull details on the Records page
Exceeding Standardschecked against how it’s made and tested
Optional add-on · tap to add
Supported by the product’s test data+ $900
A limit only means something if your data meet it and your method can see it. We check whether your results support the spec, independently, not on a supplier’s certificate, and whether the methods can detect what you specified. The gap between a spec on paper and a spec the product can hold.
You also send: The lot’s test results: the values used to check whether your data meet the spec and whether the method can detect what it sets.Also called: CoA, certificate of analysis, release-test resultsFull details on the Records page
Optional add-on · tap to add
Made to the specification+ $1,000
A spec is only real if the product was made to it. We check the executed batch record against the spec’s parameters. The difference between a number on the spec sheet and a number the line and the lab hit.
You also send: The executed record of the lot as made: used to check whether the product was made to the specification’s parameters.Also called: BPR, executed batch record, production recordFull details on the Records page

If your spec can’t be given a clean opinion on what you send, you get a straight report on what’s missing instead, at the same fee.

Your review$950base only

Specifications Development

No defensible spec yet? Send your product basics and we build the specification from scratch. One flat fee, with limits your product can hold and methods fit to detect them.

What this covers
  • Raw-material / ingredient specifications
  • Finished-product specifications
  • In-process / control-plan specifications
  • Identity & purity (USP / compendial)
  • Contaminant & heavy-metal limits
  • Banned-substance screen
  • Test-method fitness for specified limits
What you get back

The built specification, ready to issue and test against: parameters and limits, identity and purity, contaminant and banned-substance limits, and the methods to verify each. It is set against the compendial and regulatory requirements and grounded in what your product is, not copied from a supplier sheet or a generic template. Built to be defensible on its face and backed by methods fit to detect what it sets. Where the product can’t meet a defensible spec as it stands, we tell you that plainly and give you the path to fix it, at the same fee. Never a number written to look right.

What you send

The basis we build from: what the product or ingredient is, how it’s made and used, the claims it has to support, and any formulation, supplier, or test data you already have.

What this builds

The same ingredient, with a spec that has to hold. The calls we’d make, and why.

Nothing to catch on a build. You send what it is, how it’s made, and the data you have, and the reasoning is the work. Here is the same constructed bulk CBD isolate, brought to us to build a defensible specification from scratch, and the call we’d make on each line.

Constructed teaching example, disclosed as constructed.
See the full High Desert / GMPure™ case
01We set a total-THC limit on the basis that decides legal status.
We’d specify total THC (Δ9 plus 0.877×THCa), not Δ9 alone. Total THC is the line between a hemp ingredient and a marijuana article, and we’d tie it to a method that resolves both.
7 CFR 990 · 21 CFR 111.70(b)
02We add the residual-solvent limit the process requires.
An ethanol extraction has to control residual solvent. We’d set a USP <467> ethanol limit with a method matrix-verified for the isolate, the safety attribute the process creates, specified instead of omitted.
USP <467>
03We tie every limit to a method that can detect it, and confirm identity ourselves.
A limit no method can see isn’t a limit. We’d pair each parameter with a method fit to detect what’s specified, and base identity on the firm’s own confirmation, not a grower’s certificate taken on faith.
USP <1225> · 21 CFR 111.75
!And the honest fork, up front: the spec can’t assert a status the records don’t establish.
CBD’s eligibility as a dietary ingredient turns on §201(ff)(3)(B). We wouldn’t paper “dietary ingredient” onto the sheet. We’d build the spec to what the product is and put the federal-status question on the table up front, at the same fee, rather than ship a number that asserts a legality the data can’t carry.
FD&C §201(ff)(3)(B)
Built specification$3,000flat fee
Common questions

Straight answers.

Isn’t my spec fine if it passes my own testing?

Passing your testing only proves the product met the limits you set. It doesn’t tell you a limit is missing, that a method can’t detect what you specified, or that a number was taken on a supplier’s certificate. Those are the gaps that pass your checks and fail an audit, and they’re what this reads for.

Doesn’t my spec software already handle this?

Software stores the spec; it doesn’t judge it. It will hold a limit nothing tests for and a method that can’t see the analyte without ever telling you it can’t be defended. This is an independent read of whether the spec holds, the part software can’t do.

Can’t the consultant who wrote my spec just check it?

They can, but they’d be grading their own work, and usually inside an open-ended engagement. This is a fixed-price verdict from someone who didn’t write the spec and has no testing to sell you on the back of it. That independence is the point.

How deep does the review go?

As deep as you want. The base reads the spec on its face. Add your manufacturing record and we reconcile the spec to how the product is defined. Add the certificate of analysis and the batch record and we check whether your data support the limits and whether the lot was made to them.

What if my product can’t meet a defensible spec?

You get told that plainly, at the same fee. On the review it comes as a finding; on the build it comes as the honest path to fix it. We lay out the options and you decide. We don’t write a number to look right and we don’t make the call for you.

Is this legal advice?

No. It is an independent regulatory opinion or a built work product, not legal counsel, and it creates no attorney-client relationship. If your question is whether your specification holds up against the rules and the records behind it, that is ours.

Regulatory work product, not legal advice. A deliverable is prepared from the records you submit and is not legal counsel, not a guarantee of any regulatory or customer outcome, and forms no attorney-client relationship. It is prepared for your own use; any reliance by an auditor, a customer, or another third party is at their own risk and creates no duty to them absent a separate written agreement. The review is a document review, not a GMP audit, not analytical testing, and not the disposition or release decision. The build produces the specification and specifies methods as fit for purpose; it does not validate methods in the lab, run the testing, or determine legal status. Where the records provided can’t support a defensible result, we deliver a findings report on what’s missing instead. High Desert Botanical Extracts / GMPure™ is a constructed teaching case; no real company or product is depicted.