The Protecting Motherhood Act bars federal agencies from using the term “birthing person” or any variation of it in official documents and requires agencies to use listed sex-specific terms — for example, “woman,” “mother,” “pregnant woman,” or “pregnant female.” The statute supplies statutory definitions for “female,” “woman,” “pregnant female,” and “mother,” tying “female” to a biological condition “at conception.” The prohibition applies to regulations, guidance, forms, and communications and takes effect 30 days after enactment.
This is a narrow, textual intervention with outsized reach: it sets a binding lexical standard across the federal government and alters how agencies describe pregnancy and parenthood in policy, clinical guidance, benefit forms, and federal data systems. Agencies will need to update materials, reconcile the statutory definitions with medical practice and nondiscrimination policies, and decide how to treat transgender, nonbinary, and intersex people who are pregnant or parents — issues the bill's text does not resolve.
At a Glance
What It Does
The bill prohibits agencies (as defined by 5 U.S.C. 551) from using “birthing person” or variations in any official document and requires use of specified sexed terms when referring to people who are pregnant, giving birth, or parenting. It supplies statutory definitions — notably defining “female” based on the sex that produces the large reproductive cell “at conception.” The rule becomes effective 30 days after enactment.
Who It Affects
All federal agencies and their communications teams, program offices that issue forms or guidance (for example HHS, CMS, VA, DoD, and OCR), contractors who prepare agency materials, health-care providers and hospitals that interact with federal forms or funding, and researchers and statisticians who use federal data on pregnancy and birth.
Why It Matters
By fixing legally mandated terminology and biological definitions, the bill changes how the federal government labels sex and pregnancy across policy and data systems. That can force operational changes in forms, clinical guidance, and reporting, create tension with existing nondiscrimination and patient‑care practices, and expose agencies to compliance questions and potential litigation over scope and impact.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The Protecting Motherhood Act is short and literal: it tells federal agencies what words they may and may not use when talking about pregnancy and parenthood. Instead of allowing neutral or gender‑inclusive language such as “birthing person,” the statute directs agencies to use a specific list of sexed terms and gives definitions for those terms.
Because the prohibition covers “any official document” — explicitly including regulations, guidance, forms, and communications — the change reaches broadly across agency outputs.
The definitions are central and unusual in their precision. “Female” is defined by reference to the sex that produces the large reproductive cell and tied to that status “at conception.” The law then builds other definitions — “pregnant female” and “pregnant woman” — from that starting point. Those choices create a legal baseline that may diverge from how clinicians, state programs, and civil‑rights guidance treat sex and gender in practice.Operationally, agencies will need to inventory documents, update templates and forms, revise web content, and reissue or rescind guidance that uses proscribed language.
That work is not limited to health agencies: benefits offices, demographic data collection, emergency-response materials, and education and employment guidance referencing pregnancy could all require edits. Vendors and contractors who manage agency content will be asked to implement these changes on short notice because the statute becomes effective 30 days after enactment.The bill does not include enforcement mechanisms, penalties, or an exception process; it simply states the prohibition and the required terms.
That silence leaves open practical questions about monitoring and compliance (who audits agency language?), interaction with existing nondiscrimination statutes and agency policies that recognize gender identity, and how to handle cases where sex and gender diverge in clinical or administrative contexts. The statutory definitions will be the reference point for those disputes, but the text does not say how agencies should reconcile conflicts with medical guidance, state law, or previously issued federal rulemaking.
The Five Things You Need to Know
The bill bars any federal agency from using the phrase “birthing person” or any variation of it in regulations, guidance, forms, or communications.
It requires agencies to use one of the specified sexed terms — “female,” “mother,” “pregnant female,” “pregnant woman,” or “woman” — when referring to a female who is pregnant, giving birth, or a parent.
“Female” is defined in statute as a person who, at conception, belongs to the sex that produces the large reproductive cell; that conception‑anchored definition underpins the other defined terms.
The statutory definition of “agency” incorporates the federal definition in 5 U.S.C. 551, so the prohibition applies across executive departments and independent agencies.
The rule takes effect 30 days after enactment, giving agencies a short window to locate and revise all affected documents and communications.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — 'Protecting Motherhood Act'
This one‑line section supplies the Act's popular name and has no operational effect beyond labeling the statute. Short titles matter in practice because agency internal trackers, litigation captions, and secondary guidance will reference the Act by this name when directing compliance work.
Prohibition on using 'birthing person' in official documents
Subsection (a) imposes a textual ban: agencies may not use the term “birthing person” or any variation in any official document and gives examples — regulation, guidance, form, or communication. The broad phrasing sweeps in public‑facing materials, internal memos that are later quoted publicly, email templates, and rulemaking notices; agencies will need to interpret where internal administrative language becomes an “official document.”
Required terminology — specified sex‑based words
Subsection (b) supplies a closed list of acceptable words agencies must use when referring to pregnant people or parents: “female,” “mother,” “pregnant female,” “pregnant woman,” or “woman.” That list is mandatory rather than advisory, so agencies cannot substitute other sexed or gender‑neutral language without statutory amendment. The practical implication is that every form field label, outreach notice, and clinical guidance document that previously used inclusive phrasing will need review and likely revision.
Definitions — how the statute defines sex and parental terms
Subsection (c) defines key terms, starting with the statutory adoption of the definition of “agency” from 5 U.S.C. 551. The rest of the subsection defines “female,” “mother,” “pregnant female,” “pregnant woman,” and “woman,” with “female” tied to production of the large reproductive cell and anchored to status “at conception.” These precise definitions create a legally binding taxonomy that agencies must use, potentially overriding softer internal style guides or prior guidance that recognized gender identity.
Effective date — 30‑day implementation window
Subsection (d) makes the statutory requirements effective 30 days after enactment. The short delay means agencies have limited time to locate instances of proscribed language and update a wide array of documents, forms, and data systems; it also increases the risk that agencies will issue interim guidance or stop‑gap measures while they perform a thorough review.
This bill is one of many.
Codify tracks hundreds of bills on Civil Rights across all five countries.
Explore Civil Rights in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Advocacy groups and lawmakers that prioritize sex‑based language: they obtain a binding federal standard that aligns agency language with their policy preferences and can use the statute to challenge agency materials that use inclusive phrasing.
- Recipients and patients who prefer sex‑specific terminology for clarity in clinical or legal contexts: the bill ensures federal documents will use terms that some clinicians and patients consider medically descriptive.
- Data users who rely on long‑standing sex categories: researchers and statisticians working with historical datasets may find consistency preserved where the statute prevents language shifts that could complicate longitudinal comparisons.
Who Bears the Cost
- Federal agencies and program offices: they must inventory and revise regulations, guidance, forms, web content, and outreach materials on a short timeline, creating administrative and budgetary burdens.
- Contractors and vendors that produce agency materials and EHR vendors: they will need to update templates and software used by multiple agencies and clients, incurring implementation costs.
- Transgender, nonbinary, and intersex people and advocacy organizations: the mandated terminology and rigid definitions risk exclusion from language that reflects their identities and medical care needs, potentially degrading access or increasing stigma in federally funded programs.
- Healthcare providers and hospitals engaged with federal programs: providers who have incorporated gender‑inclusive language into patient intake, consent forms, or EHRs will face pressure to reconcile federal forms with clinical practices and state law.
- Statistical and public‑health offices: analysts will need to decide how to map inclusive or identity‑based responses into the statute's sexed categories, which may complicate reporting on maternal health disparities and program eligibility.
Key Issues
The Core Tension
The central dilemma is between imposing a uniform, sex‑based legal vocabulary to preserve certain biological categories and the practical need to serve and document the experiences of people whose gender identity or medical circumstances do not fit that vocabulary — a choice that reduces semantic ambiguity but creates administrative, clinical, and civil‑rights tensions with no easy resolution.
The bill resolves a question about federal nomenclature by statute, but it leaves open how agencies should reconcile that textual rule with medical practice and nondiscrimination frameworks. Defining “female” by reference to the sex that produces the large reproductive cell “at conception” is precise in wording but blunt in effect: it does not address people whose legal sex markers, gender identity, or clinical status differ from that conception‑anchored label.
Agencies will face immediate operational choices about whether to treat the statute as absolute, to create carve‑outs for clinical contexts, or to attempt nuanced guidance that preserves the statutory wording while acknowledging exceptions — none of which the text directs.
Implementation also raises administrative‑law and practical issues. The statute imposes a government‑wide vocabulary without specifying enforcement, auditing, or remedies, so compliance is likely to be handled through internal counsel, agency policy memos, and program offices.
That decentralized approach risks uneven application across agencies and programs. The short 30‑day effective period aggravates costs: updating regulations, reprinting forms, and changing EHR fields across federated systems is time‑consuming and may require procurement actions and contractor renegotiations.
Finally, the definitions may create conflicts with state laws and professional medical standards, exposing agencies to litigation or requiring intergovernmental coordination that the bill does not contemplate.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.