GRAS Self-Determination vs FDA Notification

12 November 2026

A food ingredient maker does not have to tell the Food and Drug Administration when it concludes that a substance is generally recognized as safe. FDA's GRAS notification procedure is voluntary, and the agency's own program page describes it that way. The choice between relying on an internal conclusion and filing a notice is therefore a business and risk decision, and it is better made with a clear view of what each route involves.

What GRAS means for food ingredient manufacturers

The starting point is a default rule. According to FDA's GRAS guidance, a substance added to food is subject to premarket approval unless it is generally recognized, among qualified experts, to be safe under the conditions of its intended use. GRAS is the exception to that default. A manufacturer that fits within it can market the ingredient without going through premarket approval.

Two phrases in that definition carry most of the weight. "Qualified experts" means the judgment has to rest on more than the company's own enthusiasm for its product. "Conditions of its intended use" means the conclusion is tied to a specific use, not to the substance in the abstract. An ingredient that is GRAS in one application is not automatically GRAS in another, and a manufacturer that widens its customers' uses has to ask the question again.

The regulatory pathway built around this exception was formalized by FDA in a final rule issued on August 17, 2016. That rule set out the GRAS notification procedure, under which a company submits its conclusion to the agency for review. The procedure sits alongside the underlying standard and does not replace it. A company can reach the same GRAS conclusion with or without notifying FDA, and what differs is whether the agency has been told about it and has responded.

When a company can rely on self-determination

The legal basis for a company's own GRAS conclusion is the standard itself. FDA's guidance on GRAS panels says the notification procedure is based on a person's conclusion that a substance is GRAS under the conditions of its intended use. In other words, the conclusion comes first, and notification is a way of presenting it to the agency. The regulation reflects this: any person may notify FDA that a substance is not subject to premarket approval if that person concludes the substance is GRAS under its intended use.

Because notification is voluntary, a manufacturer may stop at the conclusion and never submit anything. That is lawful only if the conclusion would hold up as an actual GRAS determination, which brings the qualified-experts requirement back in. The company needs a safety conclusion that rests on information qualified experts would accept for the stated use. A weak internal file does not become acceptable because no one at the agency has seen it.

In practice, the most common mistake is treating self-determination as the lighter option. The substantive burden is the same whether or not a notice is filed: the substance must be safe under the conditions of its intended use, and the support must be there. What the company skips by not notifying is the submission and the agency's response, not the work of establishing safety. A manufacturer that would struggle to assemble the documentation described in the next section should be cautious about assuming it can defend a self-determined conclusion.

Self-determination is also tied to the use the company has defined. If the intended use is narrow and well described, the conclusion is easier to articulate and to defend. If a company expects the ingredient to move into new food categories or higher levels of use, the original conclusion may not carry over, and the company would need to revisit it for each new use.

What FDA expects in a GRAS notice

A GRAS notice is a submission that informs FDA of a view that a substance is not subject to premarket approval, based on a conclusion that the substance is GRAS under the conditions of its intended use. The regulation gives that submission a defined structure. Even a company that never intends to file can use the structure as a benchmark for its own file, since it shows the questions the agency expects a safety conclusion to answer.

The following elements are the core of the format and the technical content:

• The notice must include seven parts, and if a part does not apply to the substance, the notice must say why instead of leaving it out silently.
• Part 3 must provide dietary exposure estimates for the notified substance.
• Those exposure estimates must cover exposure from the intended use and from all sources in the diet.
• Part 6 must explain why the data support a conclusion that the substance is safe under its intended use.
• Part 6 must also address any information that is inconsistent with that safety conclusion.

Two of these requirements deserve emphasis. The exposure estimate is not limited to the new use the company is proposing. It extends to all dietary sources, so a company cannot count only the amount its own product contributes and treat the rest of the diet as someone else's concern. An ingredient already present in other foods adds to the total, and the estimate has to reflect that.

The Part 6 requirement is the one that most often separates a persuasive file from a thin one. It calls for a narrative explaining why the data support safety, not a stack of studies handed over without comment. It also requires the notifier to deal with contrary information directly. A notice that presents only favorable data invites the obvious question of what was left out, while one that confronts the unfavorable findings and explains why they do not change the conclusion is more credible on its face.

How FDA reviews a submitted notice

Once a notice is in, the timeline is set by regulation. Under 21 CFR 170.265, FDA will respond within 180 days of filing a GRAS notice. The regulation also allows the agency to extend that timeframe by 90 days on an as-needed basis, which makes the outer limit 270 days from filing when an extension is used. The text of 21 CFR 170.265 on the eCFR sets out both periods.

Two practical points follow from that language. First, the clock runs from filing, so a company planning a product launch should treat the 180 days as a minimum planning horizon and not as a guarantee of the date it will hear back. Second, the extension is discretionary and tied to need, so a company cannot assume it will not be used. Anyone building a launch schedule around a notice should leave room for the longer period.

The review period also affects how a company prepares. Because the notice has to carry the safety argument on its own, gaps in the exposure estimate or an unaddressed inconsistency in the data are problems best fixed before submission. The regulation does not describe the notice as an opening bid to be refined later. Treating the file as complete when it goes in is the safer assumption.

Practical compliance implications for ingredient makers

For a manufacturer, the framework reduces to a few operational choices. The first is whether the ingredient's safety conclusion is strong enough to stand on its own. The second is whether the company wants FDA to have seen and responded to that conclusion, given a 180-day review that may stretch by 90 days. The third is who will vouch for the science, since the standard is recognition among qualified experts. FDA's GRAS notification program page confirms the procedure is voluntary and gives the background on the 2016 rule.

Companies that use outside expert panels should remember how FDA's panel guidance frames things: the notification procedure rests on the notifier's own conclusion. A panel can inform that conclusion, but responsibility for it stays with the company. The same is true when no panel is involved. Someone inside the company has to own the determination, know the intended use it covers, and be able to explain it.

Documentation discipline matters on every route. Writing the safety file in the shape the regulation prescribes, with an exposure estimate that counts all dietary sources and a narrative that meets contrary data head-on, makes the file usable whether it stays in a drawer or goes to the agency. If the company later decides to notify, most of the work is already done. If it decides not to, it still holds a record it can produce when a customer, a retailer, or a regulator asks how it concluded the ingredient was GRAS.

The takeaway for ingredient makers is to decide the route before the file is written, not after. Define the intended use precisely, build the exposure and safety analysis to the standard the notice format demands, and then weigh the voluntary notification against the timeline and the commercial need for FDA's response.