Statute vs. Regulation vs. Ordinance: What Is the Difference

The American legal system produces binding rules through three distinct mechanisms — statutes, regulations, and ordinances — each originating from a different branch or level of government and carrying its own scope of authority. Confusing these categories leads to misidentification of the governing rule in any given situation, which in turn affects how disputes are resolved, how violations are prosecuted, and which body holds enforcement power. This page defines each category with precision, explains the processes that create and enforce them, and maps the boundaries that determine which type of rule applies in common legal situations. Background on the broader sources of US law provides useful context for placing these three categories within the full hierarchy of American law.

Definition and Scope

Statute refers to a written law enacted by a legislative body — Congress at the federal level, or a state legislature at the state level. Statutes are codified into official compilations: federal statutes appear in the United States Code (U.S.C.), maintained by the Office of the Law Revision Counsel, while state statutes appear in each state's own statutory code. A statute represents the direct exercise of the people's legislative power through elected representatives, making it the primary and most authoritative form of enacted law below the Constitution. The process by which federal statutes are created is governed by Article I of the U.S. Constitution and elaborated in the procedural rules of each chamber; a detailed breakdown appears at How Federal Laws Are Made.

Regulation (also called a rule or administrative rule) is a binding legal standard issued by an executive branch agency acting under authority delegated by a statute. At the federal level, agencies such as the Environmental Protection Agency (EPA), the Food and Drug Administration (FDA), and the Occupational Safety and Health Administration (OSHA) publish proposed and final rules in the Federal Register and codify them in the Code of Federal Regulations (C.F.R.), maintained by the Government Publishing Office. A regulation cannot exceed the scope of the statutory authority that authorized it — if it does, courts may strike it down under the Administrative Procedure Act (APA), 5 U.S.C. § 551 et seq. The broader framework of agency rulemaking is covered at Administrative Law and Regulatory Agencies.

Ordinance is a law enacted by a local legislative body — a city council, county board of supervisors, or similar municipal authority. Ordinances govern matters within the territorial jurisdiction of the local government, typically including zoning, building codes, noise limits, parking rules, and local business licensing. A municipality's power to enact ordinances derives from authority granted by the state — either through a state constitution, a home rule charter, or a state enabling statute — which means ordinances occupy the lowest rung of the formal legal hierarchy and must not conflict with state statutes or federal law.

How It Works

Each category follows a distinct creation process with defined procedural requirements.

Statute creation — federal level:

1. A bill is introduced in the House of Representatives or the Senate.
2. The bill is referred to the relevant committee for review, hearings, and markup.
3. The full chamber debates and votes; if passed, the bill moves to the other chamber.
4. Both chambers must pass identical language; differences are resolved in conference.
5. The enrolled bill is presented to the President for signature or veto (U.S. Const. art. I, § 7).
6. Upon enactment, the statute is assigned a Public Law number and later codified in the U.S.C.

Regulation creation — federal level (APA notice-and-comment):

1. An authorizing statute grants the agency rulemaking authority.
2. The agency publishes a Notice of Proposed Rulemaking (NPRM) in the Federal Register, opening a public comment period of typically 30 to 60 days.
3. The agency reviews comments, may revise the draft, and publishes a Final Rule.
4. The Final Rule takes effect no earlier than 30 days after publication (APA, 5 U.S.C. § 553), with exceptions for good cause.
5. The rule is codified in the C.F.R. under the appropriate title.

Ordinance creation — local level:

1. A council member, mayor, or administrative body proposes the ordinance.
2. The local legislative body holds public hearings, often required by state law.
3. The body votes; passage requirements vary by jurisdiction (simple majority is typical).
4. The ordinance is signed by the mayor or equivalent executive, then published in a local legal journal or official municipal code.

Common Scenarios

Workplace safety rules: OSHA's hazard communication standard at 29 C.F.R. § 1910.1200 is a regulation, not a statute. The authorizing statute is the Occupational Safety and Health Act of 1970 (29 U.S.C. § 651 et seq.). If a city requires additional contractor registration within city limits, that requirement is an ordinance.

Drug approval: The Federal Food, Drug, and Cosmetic Act (21 U.S.C. § 301 et seq.) is a statute establishing FDA's authority. FDA's specific drug approval pathway requirements — Good Manufacturing Practice standards — appear in regulations at 21 C.F.R. Parts 210–211.

Zoning conflicts: A property owner facing conflicting commands from a municipal zoning ordinance and a state land-use statute must follow the state statute, because state law preempts local ordinances under the Supremacy principle applicable within each state's legal hierarchy. Federal law, in turn, preempts conflicting state statutes under the Supremacy Clause of the U.S. Constitution (art. VI, cl. 2). Questions about how jurisdictional lines are drawn appear at Federal vs. State Jurisdiction.

Environmental enforcement: The Clean Air Act (42 U.S.C. § 7401 et seq.) is a statute. The National Ambient Air Quality Standards (NAAQS) — setting specific parts-per-million thresholds for pollutants like ozone and particulate matter — are regulations codified at 40 C.F.R. Part 50, published by EPA.

Decision Boundaries

Determining which category applies to a given rule requires answering four questions in sequence.

1. What body issued the rule?
- Legislature (Congress or state assembly) → likely a statute
- Executive agency (EPA, FDA, state department of health, etc.) → likely a regulation
- City council, county board, or municipal authority → likely an ordinance

2. What is the source of authority for the rule?
Regulations require a specific statutory delegation. If no authorizing statute exists or the rule exceeds that statute's scope, the regulation lacks legal foundation and is subject to challenge under the APA or equivalent state administrative procedure act. Ordinances require enabling authority from state law.

3. Where is the rule codified?
- U.S.C. or state statutory code → statute
- C.F.R. or state administrative code (e.g., California Code of Regulations, Texas Administrative Code) → regulation
- Municipal code (e.g., New York City Administrative Code, Chicago Municipal Code) → ordinance

4. What happens when rules conflict?
The hierarchy is fixed: the U.S. Constitution supersedes all other sources; federal statutes supersede conflicting state statutes and local ordinances under the Supremacy Clause; federal regulations, when validly issued, carry the force of federal law; state statutes supersede local ordinances within that state. This hierarchy is central to understanding the US Constitution and the Legal System.

One boundary that generates frequent litigation involves the distinction between a statute and a regulation when an agency interprets its own authorizing statute broadly. Following the U.S. Supreme Court's 2024 decision in Loper Bright Enterprises v. Raimondo, 603 U.S. ___ (2024), federal courts no longer automatically defer to agencies' interpretations of ambiguous statutes under the former Chevron framework, meaning the line between a statute's text and an agency's regulatory interpretation now receives independent judicial scrutiny.

A separate but related boundary involves the distinction between a regulation and a guidance document. Agencies regularly issue guidance, policy statements, and interpretive rules that do not go through notice-and-comment rulemaking. These documents do not carry the binding force of a regulation (GAO, Federal Rulemaking, GAO-04-1029) and cannot impose enforceable legal obligations independent of an underlying regulation or statute — a distinction that matters substantially in enforcement contexts. For understanding how these distinctions intersect with procedural rights, the overview of Due Process Rights in US Law addresses how courts assess whether government action complies with constitutional constraints regardless of the rule's category.

References

• United States Code — Office of the Law Revision Counsel
• Code of Federal Regulations (eCFR) — Government Publishing Office
• Federal Register — National Archives
• [Administrative Procedure Act, 5 U.S.C. § 551 et seq. — Cornell Legal Information Institute](