On the Problem With Executive Orders as Policy Tools
An executive order is a written directive signed by the President that manages operations of the federal government. It has the force of law only when it rests on authority delegated by the Constitution or by statute. Adjacent instruments include presidential memoranda, proclamations, and national security directives. The problem is not that these tools exist. The problem is that they have become a substitute for legislation, and that substitution creates policy that is fast to make, slow to undo, and structurally allergic to public input.
This matters to anyone who follows federal legislative, regulatory, and budget mechanics because executive orders sit at the intersection of all three. They can redirect agency rulemaking. They can shift spending priorities within appropriated accounts. They can create compliance obligations that look like law but never passed through a committee hearing. Understanding how they work, and how they fail, is part of understanding why the federal government behaves the way it does.

The Mechanics of an Executive Order
An executive order is not mentioned by name in the Constitution. The President’s authority to issue one comes from Article II, which vests executive power in a single officer, and from the Take Care Clause, which requires the President to ensure that the laws are faithfully executed. When Congress passes a statute that gives the President discretion, an executive order can direct how that discretion is used. When the Constitution gives the President direct authority over foreign affairs or the armed forces, an executive order can operationalize that authority.
The order itself is published in the Federal Register. It receives a number, such as Executive Order 14008 or Executive Order 14110. The Office of the Federal Register assigns the number, and the order remains in effect until the President revokes it, a court enjoins it, or Congress passes a law that overrides it. There is no expiration date unless the order includes one.
This is the first structural problem. A statute requires bicameral passage and presentment. An executive order requires a signature. A statute can be amended through the same slow process that created it. An executive order can be revoked by the next President in the first week of a new administration. That speed cuts both ways. It allows rapid response to emergencies. It also allows policy whiplash that makes long-term planning nearly impossible for agencies, regulated industries, and state governments.
What an Executive Order Can and Cannot Do
An executive order cannot create new criminal law. It cannot appropriate money that Congress has not appropriated. It cannot repeal a statute. It cannot expand the President’s constitutional authority beyond what courts have recognized. What it can do is direct agencies to interpret existing statutes in particular ways, set enforcement priorities, create task forces, impose government-wide management requirements, and shape the regulatory agenda.
The line between permissible direction and impermissible lawmaking is not always clear. Courts have struggled with it for decades. The Supreme Court’s decision in Youngstown Sheet & Tube Co. v. Sawyer remains the classic framework. Justice Jackson’s concurrence divided presidential action into three categories: action authorized by Congress, action where Congress is silent, and action that conflicts with congressional will. The first category gets the most deference. The third gets the least. Most executive orders fall somewhere in the middle, and that is where the litigation happens.
The Procedural Asymmetry
Legislation is slow by design. A bill must survive introduction, committee referral, markup, floor debate, amendment, passage in two chambers, conference or reconciliation, and presentment. Each step creates a record. Each step creates an opportunity for opposition, modification, or delay. The process is frustrating, but it forces a kind of consensus-building that executive orders do not require.
An executive order can be drafted in a week. It can be signed without a hearing. It can take effect immediately or on a date certain. The public has no formal role. There is no notice-and-comment period unless the order directs an agency to conduct rulemaking, and even then, the agency is implementing a decision that has already been made at the political level.
This asymmetry explains why Presidents of both parties have turned to executive orders when Congress fails to act. It also explains why the orders are so fragile. A policy that takes a week to create can be erased in a day. The result is a federal government that lurches from one administration’s priorities to the next, with agencies spending years rewriting guidance, reallocating staff, and redoing work that was just completed.

The Regulatory Ripple Effect
Executive orders often function as the first domino in a regulatory cascade. An order directs an agency to review its rules. The agency issues a request for information. Stakeholders submit comments. The agency proposes a rule. More comments arrive. The agency finalizes the rule. Litigation follows. Years pass.
Consider the federal contracting space. An executive order on minimum wage for federal contractors can change labor costs for thousands of companies without a single vote in Congress. The order directs the Department of Labor to issue regulations. The regulations incorporate the wage rate. Contractors adjust their bids. The change is real, but it rests on the President’s procurement authority under the Federal Property and Administrative Services Act. A different President can revoke the order, and the whole cycle runs in reverse.
This is not a partisan observation. The same dynamic applies to orders on regulatory review, environmental permitting, immigration enforcement, and federal workforce policy. The tool is the same. The instability is the same. The only variable is which party holds the pen.
The Budget Connection
Executive orders can also shape federal spending without touching the appropriations process. An order that directs agencies to prioritize certain grant programs does not change the amount of money available, but it changes who gets it. An order that freezes regulatory activity can delay the implementation of programs that Congress funded. An order that reorganizes an agency can shift personnel costs within an existing appropriation.
These moves are legal, mostly. They are also opaque. The public sees the press release. The public does not see the reprogramming notices, the internal budget memos, or the staffing reallocations. By the time the Government Accountability Office issues a report, the policy has been in effect for months or years.
The Institutional Cost
The deeper problem with executive orders is what they do to the institutions that must implement them. Agencies are built for continuity. They have career staff who develop expertise over decades. They have procedures designed to ensure consistency. When policy changes by executive order every four or eight years, that continuity erodes.
Career staff learn to wait. They learn that the current policy may not survive the next election. They learn that the work they did last year may be undone next year. That is not cynicism. It is rational adaptation to an unstable environment. The result is a federal workforce that is less willing to invest in long-term projects, less willing to make difficult calls, and more likely to defer decisions until the political winds settle.
Congress bears some responsibility here. When Congress fails to legislate, it creates a vacuum. The President fills the vacuum with an executive order. Congress then criticizes the President for acting unilaterally, while doing nothing to reclaim its own authority. The cycle repeats. The institution that is supposed to make law becomes a spectator to lawmaking by directive.

What Would a Better System Look Like?
The answer is not to eliminate executive orders. They serve a legitimate purpose. The President needs the ability to direct the executive branch, respond to emergencies, and manage the federal workforce. The answer is to restore the expectation that major policy changes go through the legislative process.
That requires Congress to do its job. It requires members to accept that legislating is slow and messy and that the alternative is worse. It requires the public to understand that executive orders are not a shortcut to good government. They are a symptom of legislative failure.
There are procedural reforms that could help. Congress could require expedited review of major executive orders. It could create a fast-track process for codifying orders that have broad support. It could strengthen the Congressional Review Act to cover executive orders, not just agency rules. None of these reforms would solve the underlying problem, but they would create pressure to use the legislative process more often.
Frequently Asked Questions
Can an executive order be overturned by Congress?
Yes, but only through legislation. Congress can pass a law that overrides an executive order, but the President can veto that law. Congress can then override the veto with a two-thirds majority in both chambers. This is rare. Congress can also use its appropriations power to defund the implementation of an executive order, but that requires the same legislative process. In practice, most executive orders are overturned by the next President or by federal courts.
How many executive orders have been issued?
The American Presidency Project at the University of California, Santa Barbara maintains a comprehensive database. The total number exceeds 14,000 since George Washington. The pace has varied widely. Some Presidents issued fewer than one per year. Others issued more than 300 per year. The number alone does not tell you much. A single order can be more consequential than a hundred routine directives.
Are executive orders the same as laws?
No. A law is passed by Congress and signed by the President, or passed over the President’s veto. An executive order is a directive from the President to the executive branch. It has the force of law only to the extent that it rests on statutory or constitutional authority. Courts can and do strike down executive orders that exceed that authority. A law, by contrast, remains in effect until Congress repeals it or a court finds it unconstitutional.
Why do Presidents use executive orders so often?
Because Congress is slow, and the public demands action. When a problem is in the news, the President faces pressure to respond. Legislation can take months or years. An executive order can be signed in days. The political incentive is obvious. The institutional cost is less visible, but it is real. Every executive order that substitutes for legislation makes the next one more likely, and makes Congress less relevant to the policy process.
The Takeaway
Executive orders are a legitimate tool of presidential administration. They are also a sign of legislative dysfunction. The more they are used for major policy changes, the more the federal government operates on a four-year cycle of creation and repeal. That is not stability. It is not deliberation. It is not the system the Constitution describes.
The next time a President signs an executive order with a flourish, ask a simple question: What statute authorizes this? If the answer is unclear, the order is probably on shaky ground. If the answer is clear, the next question is harder: Why did Congress not pass a law instead? The answer to that question usually explains more about the state of American government than the order itself.
This piece is part of a continuing series on the mechanics of federal power. A companion article will examine the Congressional Review Act and its limits as a check on executive action. A separate piece will look at how presidential memoranda differ from executive orders in practice, and why the distinction matters for agencies and regulated parties.