Cosmetic Safety Substantiation

The safety file your cosmetic has to hold — reviewed, or built.

Two ways in. Have a substantiation file? Get an independent read on whether it actually supports the safety conclusion, at the depth you choose. Don’t have one? Send your formula and label and we build it.

The trendMoCRA put it on the record

For the first time, federal law (MoCRA) requires every cosmetic to hold adequate safety substantiation on file before it’s marketed — and gives FDA the records access to ask for it. The file that used to be a formality is now the one a regulator can pull.

Pattern · MoCRA cosmetic safety-substantiation requirement

What this is

Whether your safety conclusion is proven — or just asserted.

Every cosmetic has to hold a safety substantiation on file before it goes to market, and “adequate” is a judgment, not a form. We judge the file you hold, or build the one you’re missing — reading it the way a regulator or a retailer’s reviewer would, so the safety conclusion is supported by the records, not stated over them.

Cosmetic Safety Substantiation Review

An independent read of the safety substantiation you already hold — does it actually hold up. Start at the base; add the records that test the conclusion against the real product.

What this covers

Cosmetic safety substantiation — MoCRA
Cosmetic product-safety file

What you get back

An opinion letter with a clear adequacy verdict and every finding traced to the record it came from — one you can file, hand a retailer, or use to fix a gap before a regulator, a buyer, or a complaint tests it. We read your file the way a reviewer would and test whether the safety conclusion is supported, not just asserted. The party that built your file — often whoever made the product or sold you the formula — cannot independently grade it. We can. This reviews the file you hold; it is not full label-claim compliance.

What a review catches

A worked safety file — complete, confident, and substantiating the wrong product.

A constructed example: an anti-aging crème with a full substantiation file and a clean “safe as used” conclusion. Here is what the deeper read surfaced once the file was lined up against the product actually in the jar — each catch tied to the real requirement.

Specimen drawn from the Document Control™ case — a “clean beauty” reformulation nobody re-substantiated

01The file substantiates a product they no longer sell.

Reads asA complete safety substantiation file with a clean “safe as used” conclusion.

Hiding in itIt’s written on the original formula. The product in the jar is a “clean beauty” reformulation with the whole preservative system swapped — logged as a minor change, and the file never updated.

Why it mattersA file that’s right about the wrong formula substantiates nothing. Line it up against the label and it’s a different product.

MoCRA · adequate substantiation

02Nothing proved the “clean” formula resists microbes.

Reads asSafe ingredients with supplier data — and a “preservative-conscious / clean beauty” claim on the front of the pack.

Hiding in itNo preservative-efficacy challenge (USP <51>) on the marketed formula; the re-challenge was logged “per brand” and never run.

Why it mattersA water-based crème with an unproven preservative grows microbes in use — and the front panel advertises the exact thing that was never tested.

USP <51> · preservative efficacy

03The safety conclusion was asserted, not calculated.

Reads asA confident “safe as used” determination on the actives.

Hiding in itNo Margin of Safety — no point of departure, no exposure (SED) for the actives. The conclusion rests on supplier statements and the original file.

Why it matters“Safe” with no Margin of Safety is an opinion. A reviewer asks for the number behind it, and there isn’t one.

Margin-of-Safety basis

!The retinol came in over the transom — and over the line.

Reads asAn anti-aging crème with a retinol active, supplied by the brand.

Hiding in itThe retinol is brand-furnished and uncontrolled — no incoming spec, never assayed — and at the level used it pushes both the exposure and the claims past where a cosmetic sits, none of which the file reckons with.

Why it mattersA sensitizing active with no exposure math is both a safety gap and a drug-claim gap. The substantiation waved it through when it should have caught it.

§201(i)/(g) cosmetic-vs-drug · exposure

Build your review

Standardthe baseline the field expects

Included

The file, on its face$2,000

Reads the substantiation you hold against what an adequate file has to contain — whether the safety conclusion is stated, sourced, and internally complete, and where it rests on assertion instead of evidence.

You send: Safety Substantiation FileThe safety substantiation you hold for the product — the assessment that concludes it is safe as used, with the data and reasoning behind it.Also called: cosmetic product safety report (CPSR), safety assessment, product-safety fileFull details on the Records page

Optional add-on — tap to add

It describes the product you actually ship+ $900

A file can be internally tidy and still describe a different formula than the one in the jar. We check the substantiation against the product as made and labeled — ingredients, concentrations, and intended-use assumptions — so it’s right about the right product, not a tidy file for the wrong one.

You also send: Product SpecificationThe finished product’s defining record — the formula and ingredients at their use concentrations, plus the intended-use and label assumptions the safety case rests on.Also called: product spec, finished-product specification, formula / ingredient breakdownFull details on the Records page

Exceeding Standardsthe conclusion, shown from the data

Optional add-on — tap to add

The toxicological conclusion is demonstrated+ $2,500

A safety conclusion is only as solid as the toxicology and exposure math under it. We check the hazard data and points of departure, the exposure (SED) assumptions, and the Margin of Safety calculation — so “safe as used” is a number you can defend, not a confident sentence nobody checked.

You also send: Ingredient/Product Toxicological DataThe hazard and exposure data behind the safety conclusion — points of departure (NOAEL/BMD), the systemic exposure (SED), and the Margin-of-Safety inputs for each active.Also called: tox data, hazard / POD data, exposure assessment, margin-of-safety inputsFull details on the Records page

Optional add-on — tap to add

The finished product is safe in use+ $1,500

Safe ingredients don’t prove a safe finished product. We check whether the product-level evidence the file leans on holds — is the finished product microbiologically safe in use (preservative efficacy / challenge)? The blind spot of a good formula that fails as a product.

You also send: Preservative Efficacy / Microbial Challenge TestThe finished-product microbial test showing the marketed formula resists contamination in use — the preservative-efficacy (challenge) result on the product as sold.Also called: PET, challenge test, USP <51>, preservative-efficacy testFull details on the Records page

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

Your review$2,000base only

Cosmetic Safety Substantiation File

No substantiation on file yet? Send your formula and label and we build it from scratch — one flat fee, built to the standard our own review applies.

What this covers

Cosmetic safety substantiation — MoCRA
Cosmetic product-safety file

What you get back

The built safety substantiation file, plus a work-product record showing how each conclusion was reached — not just the result. We assess the formula and finished product against the safety and exposure evidence and build the file to the standard an independent review would hold it to, every conclusion worked on a corrected basis and backed by a record that shows the reasoning. You get a file built to hold, not just to exist. And where the product can’t be substantiated as it stands, you get the honest path to fix it at the same price.

What you send

The two records we build from: your master manufacturing record — the formula as actually made; and your product label — the claims and intended use it carries.

What this builds

The same product, with no file — the calls we made, and why.

Nothing to catch on a build: you send the formula and the label, and the reasoning is the work. Here is the same constructed crème — the “clean beauty” reformulation with a brand-supplied retinol — brought to us to substantiate from scratch, and the call we made at each step.

You send the formula and the label — the starting context lives on the Document Control™ case

01We substantiated the product in the jar, not the one a prior file described.

We built the file on the reformulated formula as labeled — the marketed preservative system, the marketed claims — so the substantiation matches the product you actually ship, not an earlier version of it.

MoCRA · adequate substantiation

02We demonstrated the conclusion with a calculated Margin of Safety.

From the formula we set the point of departure and the exposure (SED) for each active and computed the Margin of Safety — “safe as used” as a number you can hand a reviewer, not a sentence.

Margin-of-Safety basis

03We named the product-level evidence the conclusion depends on.

We built the file around a finished-product preservative-efficacy challenge on the marketed formula and the finished-formula data the safety case rests on — so a “clean / preservative-conscious” claim has something under it.

USP <51> · product-level evidence

!And the honest fork, up front: a file can’t substantiate a product that isn’t safe as made.

Where the actives or the preservation can’t clear a defensible bar — a retinol level past a cosmetic exposure, a “clean” system that fails the challenge — we said so and gave the path: reformulate, or add the efficacy and finished-formula data. Not a file built to look complete over a product that isn’t.

§201(i)/(g) cosmetic-vs-drug · exposure

Built safety file$4,500one product · flat fee

Common questions

Straight answers.

Isn’t my supplier’s safety data enough?

No. Supplier data covers an ingredient in isolation, not your finished product at your concentrations and exposure. Adequate substantiation is about the product as you make and sell it — and the obligation to hold it sits with you, not the supplier.

Whoever made my product already gave me a file. Why review it?

Because the party that built it can’t independently tell you it’s good enough — and under MoCRA the obligation is yours, not theirs. An independent read tells you whether it holds before a regulator, a retailer, or a complaint is the one that tests it.

Do you run the lab testing — the challenge test or tox studies?

No. We judge the file or build it, and name the data the conclusion depends on. The preservative-efficacy challenge and any toxicology studies are lab work you run; we make sure the file rests on the right ones.

Is this the same as checking my label claims?

No. This is the safety substantiation — whether the product is safe as used and the file proves it. Full label-claim compliance is a separate question; we’ll flag where a claim outruns the safety case, but vetting every claim isn’t what this buys.

What if my product can’t be substantiated as it stands?

You get told that plainly, at the same fee. Sometimes the file isn’t the problem — the formula is. We lay out the path (reformulate, add the missing finished-product data) and you decide; we don’t write a file that signs off on a product that can’t be shown safe.

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 the safety file holds up against the requirement and the product behind it, that is ours.

Where to go from here.

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 retailer outcome, not the decision to release or sell the product, and forms no attorney-client relationship. It is a document review or build — not a GMP audit, not laboratory testing, and not full label-claim compliance or any agency filing or registration. Where the records provided can’t support a defensible result, we deliver a findings report on what’s missing instead. Document Control™ is a constructed teaching case; no real company or product is depicted.