Executive Order vs Law: What Separates a Presidential Order From a Statute

An executive order is a directive the President issues to federal agencies. A law is a statute that Congress passes and the President signs, or that becomes law over a veto. An executive order can carry the force of federal law, but it cannot create a new law, and Congress can repeal or override it. The two differ in where they come from, how strong they are and what paper trail they leave behind.

The Short Answer

People use the two words interchangeably because both bind the federal government, but they are different instruments. A statute starts as a bill, passes both chambers and becomes law when the President signs it or lets it take effect, or when Congress overrides a veto. An executive order starts with the President and needs no vote in Congress at all. The Congressional Research Service describes an order as having the force of law unless a later statute, treaty or order repeals it or a court invalidates it, and it cannot be used to make new law. Only Congress can do that. The CRS's introduction to executive orders sets out the same distinction.

Where Each One Gets Its Authority

A President's power to issue an order rests on one of two sources: the Constitution, mainly Article II, or a delegation of power from a statute. That is why an executive order is only as strong as the authority behind it. If an order tells an agency to do something a statute forbids, it has no legal effect, unless the President can justify it as an exercise of his own independent constitutional power. A statute has a different basis. Article I gives Congress the power to legislate, and the President's role is to sign, veto or let the bill become law.

The practical consequence is simple. A statute can be created from nothing, provided it clears both chambers and survives a veto. An order can only direct what the government already has power to do. When a President wants a policy that no existing statute authorises, an executive order cannot supply that authority on its own, and the policy needs a bill.

Legal Force: Where Orders Sit Under Statutes

Orders carry real weight, but they sit below statutes. A later statute overrides an earlier order that conflicts with it. Congress can also nullify an order that was issued under power it had delegated to the President, or ratify one by passing a law that adopts it. Federal courts can review an order's legality in the same way they review a statute, and a court can strike one down. The CRS report on issuance, modification and revocation covers how orders are amended and withdrawn, which is a separate process from passing a law.

The reverse is not true. An order cannot repeal a statute, and the President cannot use an order to rewrite the bill that a previous Congress enacted. That asymmetry is the single most useful thing to remember when you see a headline about a presidential action.

A Worked Example: Tracing a Real Statute

Bill100 pulls its bill records from Congress.gov, and the same record is available from our public API. The record for H.R. 1 in the 119th Congress, requested at `/api/v1/bills/119-hr-1`, shows the citation as H.R. 1, the status as enacted, and the progress as 5 of 6 steps. Its latest action reads "Became Public Law No: 119-21," dated 4 July 2025. That single line carries the whole difference between a bill and an order: the statute has a bill number that tracked its path through Congress, then a public law number once the President acted.

Public law numbers are assigned by the Office of the Federal Register, part of the National Archives, in the order laws are enacted within each Congress. So "Public Law 119-21" is the 21st law of the 119th Congress. The NARA list of current public laws shows the public law number, bill number, approval date and Statutes at Large citation for each one in the current session.

An executive order does not pass through that process. It has no bill number, no committee referral and no vote tally. It is numbered as a presidential document and published in the Federal Register. If the thing you're looking at has a bill number, a committee history or a public law number, it is a statute. If it has a presidential document number and a Federal Register citation, it is an order.

How to Tell Them Apart in the Record

Three signals settle most cases. First, a bill number such as H.R. 1 or S. 5321 means the item is or was a bill, and a public law number means it was enacted. Second, a presidential document number and a Federal Register citation mean the item is an order. Third, a presidential memorandum is a different kind of action again. Memoranda are not treated as executive orders, and the Federal Register publishes them only when the President determines they have general applicability and legal effect. Check the source before you rely on the label in a headline.

Why the Difference Matters for Tracking

If you follow legislation, the question is usually whether a proposal will become binding. A bill can take months or years to reach a final vote, and most never do. An executive order can take effect the day it is signed, which is why orders often show up in the news before any bill on the same subject has moved. Bill100 follows bills, so it will show a statute's path from introduction to enactment. A presidential order sits outside that record, and for an order you should go to the Federal Register. Our guide to how a bill becomes a law explains the path a statute takes, and what is a bill covers the instrument itself.

The two also interact. A President can veto a bill that Congress passes, and Congress can override that veto with a two-thirds vote in each chamber. Veto override explained walks through that step. For the latest statutes that have taken effect this year, see new laws in 2026.