# MoCRA Safety Substantiation: Organising the Evidence Behind a Cosmetic Product

> Organise the product identity, scientific evidence, assessment reasoning, and change history supporting cosmetic safety substantiation under MoCRA.

Canonical URL: https://cosmeticaffairs.com/regulatory/mocra-safety-substantiation-evidence/

Author: [Cosmetic Affairs Editorial](https://cosmeticaffairs.com/authors/editorial/)
Published: 2026-10-17T00:00:00-04:00
Modified: 2026-10-17T00:00:00-04:00
Collection: Regulatory Updates
Topics: Regulatory, MoCRA, Safety Assessments, Documentation

## Source record

- Jurisdiction: United States
- Issuing authority: U.S. Congress / U.S. Food and Drug Administration
- Document status: Practical guidance on an existing statutory requirement
- MoCRA enacted: 2022-12-29
- Source checked: 2026-10-17

### Original documents

- [21 U.S.C. section 364d — Safety substantiation](https://www.govinfo.gov/content/pkg/USCODE-2023-title21/html/USCODE-2023-title21-chap9-subchapVI-sec364d.htm)

- [FDA overview of MoCRA](https://www.fda.gov/cosmetics/cosmetics-laws-regulations/modernization-cosmetics-regulation-act-2022-mocra)

![A laboratory professional reviews safety evidence beside a plain moisturizer jar, retained sample, and document index.](https://cosmeticaffairs.com/regulatory/mocra-safety-substantiation-evidence/cover.png)

AI-generated illustration; not a photograph of actual laboratory work.

A useful safety substantiation file explains which product the evidence supports, why that evidence is relevant and who reviewed the conclusion. Collecting reports is a starting point. The important work is connecting them to the product being marketed and making the reasoning understandable to another qualified reviewer.

Jurisdiction: United States. Scope: cosmetic products subject to section 608(a) of the Federal Food, Drug, and Cosmetic Act. Status: practical guidance on an existing MoCRA requirement. Checked: 17 October 2026.[^1]

## Start with the responsibility and the evidence standard

Section 608 requires the responsible person to ensure, and maintain supporting records for, adequate safety substantiation.[^1] FDA describes the responsible person as the manufacturer, packer or distributor whose name appears on the product label under the applicable labelling provisions.[^2]

The statutory standard concerns evidence sufficient, in the judgement of experts qualified through scientific training and experience, to support a reasonable certainty that the product is safe. The definition addresses safety under labelled conditions of use and customary or usual use.[^1]

FDA explains that there is no prescribed set of specific tests for demonstrating the safety of every individual cosmetic product or ingredient. Relevant existing safety data can contribute, and the methods producing the supporting data need to be scientifically robust.[^2]

For a practical workflow, identify who coordinates the evidence, who performs the scientific review and who follows up missing information. Record those responsibilities at the beginning of development. This gives each question a route to resolution before the evidence is needed for a decision.

## Define the product being assessed

Open the file with a product description that a colleague can match to the commercial product. Include its internal identifier, formula version, intended use, directions, relevant user group, packaging reference and label version.

The level of detail should allow a reviewer to understand what the evidence is being asked to support. If a report concerns an earlier development sample, show the relationship between that sample and the final formula. If several product variants share evidence, record the rationale for applying it to each variant.

A useful organising question is: what would another reviewer need to know before deciding whether this document applies? That question helps identify missing information without turning every product file into the same fixed checklist of tests.

Keep the product description versioned. When it changes, the previous description should remain connected to the earlier assessment so the historical decision can still be reconstructed.

## Build an evidence index with a purpose for each document

An evidence index can make a large file easier to review. The following is a suggested structure, rather than an FDA-prescribed dossier format or universal testing package.

| Index area | What to connect | Review question |
| --- | --- | --- |
| Product identity | Formula, sample, packaging and label references | Does the evidence concern the product being marketed? |
| Ingredient information | Specifications, supplier data and relevant safety sources | Are identity, composition and use level sufficiently understood? |
| Product investigations | Relevant test reports, methods and sample details | What question did each investigation address? |
| Scientific assessment | Evidence considered, limitations and reasoning | Why is the combined evidence sufficient for this product? |
| Follow-up work | Missing information, owner and due date | What remains unresolved, and how will it be addressed? |
| Review history | Changes, reassessments and resulting decisions | What changed after the previous conclusion? |

For each document, add its identifier, date, revision, source and relationship to the product. Include a short note on its intended role. A reviewer can then distinguish a material-identification document from evidence used to address a particular safety question.

Where information is provided by an external laboratory or consultant, agree how the relevant reports and explanations will remain accessible. Make ownership of follow-up questions explicit before the project is handed over.

## Record the reasoning behind the conclusion

The assessment should explain how the evidence fits together. Ask the reviewer to identify the important assumptions, limitations and unresolved questions, and to describe why the available information supports the conclusion for the defined product and use.

Keep differences visible. For example, where a study uses a different material grade or test sample, request an explanation of its relevance. The appropriate response may be additional information, a justified comparison or further investigation. The choice should follow the scientific question.

Consider an illustrative project in which a moisturiser's formula is approved, but the team later proposes different packaging. Create a change record describing the proposed package, the evidence previously considered and the questions requiring review. The reviewer can then determine what additional information, if any, is needed.

Record the outcome and its basis. Avoid replacing the original conclusion with an unexplained new approval date. The history should show what was assessed at each stage and why the decision changed or remained valid.

## Use software to connect the work

Organise the evidence index so that test reports and supporting documents lead back to the relevant product, formula and sample. Use document categories that help a reviewer locate the evidence needed for a particular question.

When setting up that workflow, agree consistent identifiers for products, formula versions, samples and reports. Test whether a colleague can start with a marketed product and locate the relevant evidence without relying on the original project owner's memory.

Also define the meaning of each status. “Document received”, “under review” and “review completed” describe different stages. Decide who can change a status, what information supports the change and how corrections are recorded.

The software's role is to help organise and retrieve the work. The scientific assessment still needs a justified conclusion about the product. Choose review and approval responsibilities that make that distinction clear in daily use.

## Keep the record useful after launch

Create a procedure for bringing relevant new information into the assessment. Suggested triggers to consider include changes to the formula, material specifications, supplier, packaging, intended use or directions, together with new safety information and product-related feedback.

Assign someone to assess the significance of each change. Record which evidence was reconsidered, any further work requested and the resulting product decision. Give open work a visible owner and follow-up date.

Periodically try a retrieval exercise: select a product and ask a colleague to identify the current formula, the supporting assessment, the evidence it references and any unresolved actions. Investigate every broken link they encounter.

A well-organised file allows the team to explain a decision today and revisit it when the product or its supporting information changes. That continuity is the practical goal of the recordkeeping process.

## Sources

[^1]: United States Government Publishing Office. [21 U.S.C. section 364d: Safety substantiation](https://www.govinfo.gov/content/pkg/USCODE-2023-title21/html/USCODE-2023-title21-chap9-subchapVI-sec364d.htm).

[^2]: US Food and Drug Administration. [Modernization of Cosmetics Regulation Act of 2022 (MoCRA)](https://www.fda.gov/cosmetics/cosmetics-laws-regulations/modernization-cosmetics-regulation-act-2022-mocra).