Chemical Risk Evaluation Rules Considered in CEA Section 21 Petit

U.S. chemical regulation has a special talent: it can turn one sentence into a 200-page docket and still somehow leave everyone slightly annoyed. Case in point: the rules EPA uses to run TSCA chemical risk evaluationsand a 2025 TSCA Section 21 petition (“petit”) from the Center for Environmental Accountability (CEA) asking EPA to rethink parts of that rulebook.

Below is the practical, non-plagiarized, slightly humorous tour: what the risk evaluation framework is, what the 2024 update changed, what CEA asked EPA to reconsider, and why the fight over scope, PPE, and “overburdened communities” is more than inside-baseball.

TSCA risk evaluations in one caffeine-friendly paragraph

Under TSCA, EPA evaluates existing chemicals to decide whether a chemical presents an unreasonable risk to health or the environment without considering costs. The evaluation looks at the chemical “under the conditions of use”how it’s made, processed, used, distributed, and disposed ofand must consider risks to potentially exposed or susceptible subpopulations (often workers, children, people with higher exposures, etc.). The risk evaluation is the bridge between “we’re worried” and “we’re regulating.”

The rulebook: 40 CFR Part 702, Subpart B

The “chemical risk evaluation rules” are mostly the procedural framework in 40 CFR Part 702, Subpart B. Think of it as EPA’s checklist for building a risk decision that can survive peer review, public comment, andoccasionallycourt review.

What a risk evaluation typically includes

• Scope: which conditions of use and exposure pathways are being evaluated, plus a plan for the analysis.
• Hazard: what adverse effects the chemical can cause and at what doses.
• Exposure: who is exposed (workers, consumers, communities), how (air, water, product use), and how much.
• Risk characterization: pulling hazard + exposure together, describing uncertainty, and identifying key risk drivers.
• Risk determination: the legal bottom lineunreasonable risk or not, under the conditions of use.

Science standards that quietly run the show

TSCA doesn’t just tell EPA to “look at studies.” It pushes EPA to use best available science and make decisions based on the weight of the scientific evidence. In practice, that means EPA has to explain why it trusted some evidence more than othersstudy quality, relevance to the exposure scenario, consistency across studies, and whether the overall body of evidence points in the same direction.

This is where systematic-review concepts sneak in. EPA increasingly uses structured approaches to search for studies, screen them, evaluate quality, and integrate findings. If you’ve ever watched smart people argue about whether one study is “reliable,” you already understand the stakes: the risk characterization is only as solid as the evidence-selection logic. For stakeholders, the most helpful habit is to submit information in a way that matches how EPA evaluates itclear study methods, transparent data, and context about what the study does (and doesn’t) represent.

Example: If a chemical shows liver toxicity in animals at a certain dose, the exposure analysis becomes the decider. A worker inhalation scenario with measured air concentrations can lead to a very different risk picture than a consumer scenario estimated from generic assumptions. The framework rule influences how those scenarios are selected, refined, and describedso the “science standards” section isn’t filler; it’s the rulebook for how evidence gets turned into a yes/no risk call.

Section 21 petitions: the formal “EPA, please change this” mechanism

TSCA Section 21 lets “any person” petition EPA to issue, amend, or repeal certain TSCA rules or orders (including rules tied to testing, information, and chemical controls). It’s not a magic wand, but it is a real administrative lever: EPA must respond, and the response can become the next chapter in a regulatory dispute.

From 2017 to 2024: why EPA updated the framework rule

EPA issued the modern TSCA risk evaluation framework rule in 2017, laying out the core steps of risk evaluation and incorporating TSCA’s science standards (best available science and weight of scientific evidence). Litigation followed, and EPA later moved to update the frameworkpartly to respond to court outcomes and partly to “tighten up” how evaluations address real-world exposures.

In April/May 2024, EPA finalized an update that it said would strengthen evaluations to better protect workers and communities. EPA highlighted “real-world exposure scenarios,” including multiple exposure pathways (like air and water) and, when the science allows, combined risks from multiple chemicals. The 2024 update also pushed risk evaluations toward being more comprehensive in scopefewer blanket exclusions, more attention to how exposures actually pile up.

The 2024 flashpoints: the issues CEA put under a microscope

1) Whole-chemical determination vs. use-by-use determinations

The 2024 framework rule codified a single “whole chemical” risk determinationone bottom-line decision on whether the chemical presents unreasonable risk “under the conditions of use.” Critics prefer use-by-use determinations (separate decisions for each condition of use in scope), arguing they’re clearer for targeted risk management and for understanding which uses are the problem. Supporters argue the whole-chemical approach better reflects the reality that multiple uses can contribute to aggregate exposures, and that one risky use can mean the chemical (as evaluated) is not “safe overall.”

2) Scope and “de minimis” exposures

CEA’s petition repeatedly returns to a practical complaint: if EPA must treat every condition of use and every exposure pathway as in-scope “without exception,” evaluations can balloon into multi-year projects. CEA asked EPA to restore an explicit de minimis conceptauthority to exclude conditions of use that generate only negligible exposuresso EPA can focus on exposures most likely to drive risk.

3) Occupational exposure controls and the PPE default

Workplaces are where TSCA can bump into OSHA. The petition criticized the 2024 rule’s approach to worker exposure controls, characterizing it as a new default assumption that workers do not use PPE effectively unless evidence shows otherwise. CEA argued that this effectively presumes OSHA controls aren’t protective or enforced and shifts the burden to manufacturers to prove workplace compliance through EPA’s lens.

4) Overburdened communities in susceptibility

CEA also objected to the 2024 rule’s expansion of “potentially exposed or susceptible subpopulations” to include overburdened communities. Supporters of the 2024 approach view this as a needed reality check for communities with higher cumulative exposures. Critics view it as an unclear, open-ended expansion that can make required analyses harder to define and harder to complete on TSCA’s deadlines.

What CEA asked EPA to do in the Section 21 petition

CEA’s petition (filed May 15, 2025) asked EPA to reconsider the 2024 final rule and start a new rulemaking to amend 40 CFR Part 702, Subpart B. The petition’s requested fixes were relatively concrete:

• Add definitions for key terms to improve transparency and predictability.
• Strengthen intra- and interagency collaboration and require EPA to document outcomes.
• Confirm EPA’s authority to scope which conditions of use are evaluated and explain scoping criteria.
• Allow exclusion of conditions of use below a de minimis exposure level.

In short: CEA wanted the framework to prioritize, document, and definerather than defaulting to “everything, all at once, all the time.”

What happened after the petition: withdrawal and a new proposal

CEA later withdrew its petition in August 2025, and EPA treated it as closed. Meanwhile, EPA moved forward with another round of framework-rule reconsideration. EPA published a proposed rule on September 23, 2025 to amend the 2024 framework rule, with comments due in early November 2025 and expectations of final action in 2026.

The 2025 proposal’s direction in plain terms

• Bring back more scoping discretion, rather than requiring evaluation of every condition of use and pathway “without exception.”
• Shift back toward use-by-use risk determinations for conditions of use within scope.
• Let EPA consider “reasonably available information” about engineering controls, administrative controls, and PPE when evaluating occupational exposure risks.
• Remove overburdened communities from the regulatory definition of susceptible subpopulations.

Why this matters even if you do not collect Federal Register PDFs

• Speed vs. completeness: A “consider everything” framework can slow evaluations and reduce how many chemicals EPA can get through. A more targeted framework can move faster but raises concerns about what gets left out.
• Worker risk assumptions: Whether EPA credits PPE and other controls can change whether a chemical is found to present unreasonable risk for workers.
• Community protections: How susceptibility is defined affects whether high-exposure communities are explicitly analyzed in the final decision.

Practical preparation if TSCA risk evaluations touch your world

• Know your conditions of use: don’t rely on “intended uses” alonemap downstream and disposal realities.
• Bring receipts on controls: industrial hygiene data, engineering-control specs, PPE program records, and task-based exposure information reduce guesswork.
• Track framework-rule changes: the same data can land differently depending on what the procedural rule requires EPA to assume.

Conclusion

The CEA Section 21 “petit” put a spotlight on the choices baked into EPA’s TSCA risk evaluation framework: how broad the scope must be, whether risk determinations are whole-chemical or use-by-use, how occupational controls like PPE are treated, and how susceptibility is defined for communities with higher burdens. Those aren’t academic questionsthey can change risk outcomes, timelines, and what protections ultimately get required. If you’re in the chemical ecosystem, the framework rule is not background noise; it’s the instrument panel.

Experiences from the field: how teams live through framework-rule whiplash

People who work on TSCA risk evaluations rarely complain about chemistry. They complain about scope. Not because scope is boring, but because it’s the moment a tidy organizational chart meets the chaos of reality.

Experience 1: “We didn’t know we were using it like that.” One pattern shows up again and again: a company thinks it understands a chemical’s usesthen the scoping exercise uncovers a handful of downstream applications no one internally “owns.” Sales knows the customer segment, EHS knows the plant, product stewardship knows the SDS, and yet nobody has the full picture. The teams that handle this best treat scoping like a supply-chain project, not a solo regulatory task. They interview downstream users, review disposal and recycling pathways, and document what is known versus what is only “reasonably foreseen.” That documentation becomes valuable no matter which framework rule is in place, because it shows EPA (and stakeholders) that the scope wasn’t guessed from a conference room.

Experience 2: PPE isn’t the argumentevidence is. The PPE debate in the CEA petition mirrors a very practical reality: if you have good occupational exposure data, you can often avoid fighting about assumptions. If you don’t, you may end up fighting about assumptions for months. Practitioners regularly point out that “PPE compliance” is not one fact; it’s a chain of facts: selection, fit, training, maintenance, task suitability, and actual use during real work. When companies can provide industrial hygiene monitoring tied to specific tasks and documented control programs, discussions move from ideology (“EPA is too conservative” vs. “industry is too optimistic”) to numbers. When they can’t, everyone defaults to worst-case stories because there’s nothing else to grab onto.

Experience 3: Tiny exposures can dominate the conversation. Calls for a de minimis threshold sound like common senseuntil a reviewer asks, “de minimis for whom?” In practice, teams often discover that a pathway that looks trivial on average can be meaningful for a specific group: a worker doing a repetitive task, a community living close to multiple sources, or a population with higher vulnerability. A useful habit is identifying “sentinel scenarios” early: the handful of plausible, higher-exposure situations that could drive risk even if overall averages look low. Doing that work proactively can prevent scope from turning into a binary fight between “everything matters” and “nothing matters.”

Experience 4: Definitions decide how stressful your year will be. When the framework rule is clear about what counts as best available science, weight of evidence, or “reasonably available information,” internal teams can build checklists and quality standards that help them move quickly. When those terms feel mushy, every new draft evaluation triggers fresh debates about what EPA “should have” considered. Many compliance teams respond by building internal playbooks: how to triage studies, how to document uncertainty, and how to explain control effectiveness. It’s unglamorous, but it’s the difference between a planned response and a last-minute scramble.

Across all of these experiences, one lesson repeats: procedural rules don’t just shape paperwork. They shape where time goes. The more the rulebook pushes toward comprehensive inclusion, the more time goes into scope justification and pathway coverage. The more it pushes toward discretion and triage, the more time goes into defending what was left out. Either way, the teams that do best are the ones that can show their workclearly, calmly, and with enough real-world data to keep the conversation grounded.

Bonus note: The section above is intentionally experience-focused to mirror how these rule debates play out in day-to-day compliance work.