Blog
Sixty Years of Federal Affirmative Action Orders, From 1961 to 2025
Contractor affirmative action was built by executive order, never by statute, and an executive order ended it. Eight dated entries show how.
Here is a trivia question that would stump most law students. Which Congress voted to require federal contractors to adopt racial goals and timetables? The answer is none of them. The most far-reaching racial policy in the modern federal government was written in the executive branch, enforced by a Labor Department office, defended in court on procurement law, and finally ended by the same instrument that started it: a presidential order. Sixty-four years separate the first order from the last, and the whole story fits on one page of dates.
This post is a timeline. It gives eight dated entries, each with a line on why the entry mattered, and then it draws the argument the dates support. The argument is not that the people who wrote these orders were villains. Most of them thought they were finishing the work of Reconstruction, and they were right to want it finished. The argument is about method and meaning: a policy that grew by order instead of by statute drifted far from the text that was supposed to justify it, and the drift is the reason it was so easy to end.
Definitions before dates
Three terms get used loosely, so let us pin them down.
Affirmative action in its first sense means outreach: advertising openings widely, recruiting where you had not recruited, and ending the habit of hiring through the same closed circle of friends. Almost nobody objects to that. In its second sense it means preference: giving weight to a person's race, sex or ethnicity in a decision about hiring, contracting or admission. That is the sense people fight about, and it is the sense that the courts examined under the Equal Protection Clause and the Civil Rights Act.
Executive order is a directive from the President to the executive branch. It has the force of law only so far as it rests on a power the Constitution or a statute actually gives the President. Article II, Section 3 tells the President to "take Care that the Laws be faithfully executed." That clause is a duty to carry out laws, not a license to write them.
Federal contractor means a private firm that sells goods or services to the government. The government has a lot of leverage over such a firm, because it can say: meet our conditions or lose the contract. Every order in this timeline used that leverage.
The eight dated entries
1961: Executive Order 10925, where the phrase begins
On March 6, 1961, President Kennedy signed Executive Order 10925. It created the President's Committee on Equal Employment Opportunity and told government contractors to take "affirmative action" to ensure that applicants were hired, and employees treated, without regard to race, creed, color or national origin. This is the first appearance of the phrase in a federal order, and it is worth reading what it asked for. The order was framed as a ban on discrimination plus a duty to make sure nondiscrimination was real. Its remedy was the threat of cancelled contracts.
Why it mattered. The order established the tool that would be used for the next six decades: the contract as a lever. It also fixed a phrase in the language whose meaning would drift. In 1961, "affirmative action" sat next to the words "without regard to." Hold that thought, because the later entries are a story about how the phrase came to mean something close to the opposite of the words beside it.
1964: the Civil Rights Act, and what it said about preferences
On July 2, 1964, President Johnson signed the Civil Rights Act of 1964, after roughly sixty days of Senate debate, most of it a filibuster. Two titles matter here. Title VI says that no person shall, on the ground of race, color or national origin, be excluded from participation in, denied the benefits of, or subjected to discrimination under any program receiving federal financial assistance. Title VII makes it unlawful for an employer to discriminate against any individual because of race, color, religion, sex or national origin.
Title VII also contains a sentence that supporters of the bill wrote for a reason. Section 703(j) says that nothing in the title requires an employer to grant preferential treatment to any individual or group because of an imbalance between the number of people of a given race in its workforce and the number in the community or the available workforce. Senators who managed the bill in the Senate also put into the record an interpretive memorandum saying that Title VII did not require an employer to maintain a racial balance. The people who passed the Act said, in so many words, that they were not passing quotas.
Why it mattered. It is the one statute in this timeline, and it points the other way. Congress had a national debate, the most intense of the century, and it chose a rule of nondiscrimination. Everything later in the timeline has to be read against that choice.
1965: Executive Order 11246, the machine is built
On September 24, 1965, President Johnson signed Executive Order 11246. It required federal contractors to take affirmative action in employment and, in the original text, to pledge not to discriminate because of race, color, religion or national origin. It placed enforcement with the Secretary of Labor. Two years later Executive Order 11375 added sex to the list of protected categories. The enforcement office that grew out of it became known as the Office of Federal Contract Compliance Programs, a Labor Department agency.
The legal footing was the President's statutory authority over federal procurement, not an act of Congress about racial hiring. That distinction is the hinge of this whole story. An order resting on procurement law can be defended as a way to run the government's purchasing efficiently. It is harder to defend as a mandate for racial proportionality across the national economy.
Why it mattered. Order 11246 created a permanent bureaucracy with the power to audit a firm's workforce, demand statistical analysis and require written plans. For six decades a contractor's lawyers lived with that paperwork. The order was never voted on, never reauthorized, and never subjected to the discipline of a congressional budget fight over its purpose.
1969: the Philadelphia Plan, when "affirmative action" turned numerical
The next step came from a Republican administration, which is a fact conservatives should face honestly. In 1969 the Nixon administration, with Labor Secretary George Shultz and Assistant Secretary Arthur Fletcher driving it, revived a Philadelphia-area plan for the building trades. Federal construction contractors had to submit hiring goals and timetables for minority workers in specified trades. The argument was practical: the craft unions that supplied the labor were closed to black workers, and federal money was paying for the construction.
The plan was attacked on the ground that it violated Title VII and Section 703(j). The Comptroller General said it did. The Attorney General said it did not, drawing a line between a government's conditions on its own contract and an employer's liability under Title VII. In 1971 the Third Circuit sided with the administration in Contractors Association of Eastern Pennsylvania v. Secretary of Labor, and the Supreme Court declined to hear the case.
Why it mattered. The Philadelphia Plan is where "goals and timetables" entered American law. The old language said "without regard to." The new language counted by race. The court that upheld it rested on the procurement power, which is precisely what a lawyer would argue if the plan could not stand on the Civil Rights Act. Every later contractor program took the Philadelphia Plan as its template.
1978: Bakke, the Court splits the baby
On June 28, 1978, the Supreme Court decided Regents of the University of California v. Bakke. Allan Bakke, a white applicant, had been rejected twice by the medical school at the University of California, Davis, which set aside sixteen of one hundred seats for minority applicants. The Court produced a fractured result. Four justices would have upheld the program. Four would have struck it down under Title VI without reaching the Constitution. Justice Powell, alone, wrote the controlling opinion: a fixed quota was invalid, but a university could treat race as one factor among many in pursuit of the educational benefits of a diverse student body.
Justice Blackmun wrote separately that "in order to get beyond racism, we must first take account of race." That sentence is the strongest compact statement of the pro-preference view, and it deserves to be stated fairly. The reply, which Justice Powell's own logic suggests, is that the Constitution protects persons, not groups, and that taking account of race is exactly the thing the Equal Protection Clause forbids.
Why it mattered. Bakke established that a diversity rationale could justify race-conscious admissions, and that rationale spread from universities to employers and contractors. It also set a trap. A rule that allows race as a "plus" but forbids a "quota" invites institutions to design programs that look like the first while performing like the second.
1995: Adarand, strict scrutiny for federal preferences
On June 12, 1995, the Court decided Adarand Constructors, Inc. v. Peña, a case from the world of federal highway contracts, where a program gave a financial incentive to prime contractors who hired subcontractors owned by "socially and economically disadvantaged" individuals. Justice O'Connor's opinion held that all racial classifications by federal, state or local government must face strict scrutiny. The federal government is held to the same demanding standard as the states.
Before Adarand, the Court had applied a gentler test to the federal government. After it, a federal preference had to serve a compelling interest and be narrowly tailored to that interest. The decision did not end federal programs. It did send a warning that the permission slip was temporary, and in 2003, in Grutter v. Bollinger, Justice O'Connor wrote that she expected the use of racial preferences in admissions would no longer be necessary in twenty-five years.
Why it mattered. Adarand closed the gap between what the Constitution demanded of states and what the national government required of itself. It also meant the contractor rules rested on a narrower base: any program that used racial classifications now had to be justified under strict scrutiny, one record at a time.
2023: Students for Fair Admissions, the Court takes the sentence at its word
On June 29, 2023, the Court decided Students for Fair Admissions v. Harvard (with the companion case against the University of North Carolina). Chief Justice Roberts, writing for the majority, held that the admissions programs of both universities violated the Equal Protection Clause. The Court found that the diversity goals the schools offered were not measurable, that the programs used race as a negative for some applicants, that they relied on stereotypes, and that they had no logical end point.
The Court noted that Title VI reaches the same conduct as the Equal Protection Clause, and Justice Gorsuch's concurrence pressed the textual point that Title VI's "no person" language makes no allowance for racial preferences, which a conservative should welcome, because it is the textualism we ask of judges everywhere else. For a fuller treatment, see Students for Fair Admissions Ended an Experiment That Began With Bakke in 1978.
Why it mattered. SFFA withdrew the constitutional cover from preferences in admissions, and the logic travelled. Contractors, employers and universities now had to ask whether their own programs could survive a Court that insisted on a measurable interest, an end date and no negative use of race. Many lawyers advised clients to revisit their programs.
2025: Executive Order 14173, the instrument that started it ends it
On January 21, 2025, the day after taking office for a second term, President Trump signed Executive Order 14173, titled "Ending Illegal Discrimination and Restoring Merit-Based Opportunity." It revoked Executive Order 11246. It directed federal agencies to stop promoting what it called illegal DEI, and it required federal contractors and grantees to certify that they do not operate programs that violate federal anti-discrimination law, a certification the order made material to the government's payment decisions. It gave contractors a short window to keep complying with the old regulations while the enforcement office wound down.
Whatever one thinks of the policy, the form is the point. The 1965 order was undone by a 2025 order, with no vote in Congress, because that is how it was made. The Civil Rights Act of 1964, the statute that actually passed, was untouched and remained the law of the land.
Why it mattered. It ended the contractor affirmative action regime in the same way it was created. And it handed the next administration a cautionary lesson about building policy on a pen instead of a statute.
What the dates teach
The eight entries support four conclusions. Number them if you like, because arguments should be countable.
- The statute said one thing and the orders did another. In 1964 Congress wrote a rule of nondiscrimination and added a clause disclaiming quotas. In 1969 the Philadelphia Plan counted by race. The distance between those two documents is the distance between a law and an agency's idea of what the law ought to have been.
- A policy made by order cannot claim the authority of a statute. Supporters often talk as if the Civil Rights Act itself required affirmative action. It did not, and the people who wrote it said so. When supporters wrap the orders in the prestige of the Act, they borrow a legitimacy that the text does not grant.
- Courts moved toward the text, slowly. Bakke, Adarand and SFFA are three steps in one direction. Each demanded more of the government's justification, and each narrowed the room for the preference.
- What a pen creates, a pen removes. The 2025 order is neither a scandal nor a surprise. It is the same constitutional mechanism, run in reverse. If you want a lasting policy of any kind, whether you favor preferences or oppose them, write it into a statute and win the vote.
The best case for the other side
Fairness requires the strongest version of the defense. It runs like this. The legacy of slavery and a century of legal segregation did not vanish on July 2, 1964. Contractors who had practiced exclusion for decades could not be expected to change by good intentions alone, and the government has the right to set conditions on its own purchases. The construction trades in 1969 really were closed to black workers, and a federal dollar was subsidizing that closure. Measured goals, the argument goes, are the only way to know whether outreach is working. Without numbers you can claim success forever.
That case has real force on its facts in 1969. It does not answer the questions that remain. If goals are measured only by race, they are indifferent to the individual who is passed over because of it. If the programme has no end date, it is no longer a remedy but a permanent classification. The Founders put the principle in the Declaration, "that all men are created equal," and the Fourteenth Amendment put it in the Constitution: no state shall "deny to any person within its jurisdiction the equal protection of the laws." The word is person. A remedy that is true to that word has to be tied to a wrong done to a person, proven, and limited. That is the thread the courts kept pulling.
For the conservative reader, there are two honest lessons. First, conservatives should not pretend that the era before 1964 was a level field; the story of the Philadelphia Plan begins with locked doors, and it is a mistake to wave that away. Second, conservatives should not pretend that every defender of preferences is acting in bad faith. Many are trying to answer a real injustice. The way to win is to offer a better answer: equal treatment, enforced vigorously, with discrimination punished through the ordinary law, and opportunity widened through schools, work and family. For how this played out on campuses, see How DEI Offices Grew on Campus and What Closing Them Requires, and for the argument that equal treatment was the civil rights movement's own claim, see Colorblind Law Is Not a Code Word, It Is Harlan's Dissent Made Good.
What the 2025 order did not do
A careful reader should keep the order's limits in view. It does not repeal Title VII or Title VI. It does not make discrimination lawful. It does not tell a private employer who is not a federal contractor what to do. Employment discrimination remains illegal under the 1964 Act whatever an executive order says, and lawsuits under it continue in the ordinary way. What the order withdrew was the special apparatus: the contractor-specific rules, the numerical goals and the Labor Department office whose job was to audit for them. Litigation over how far its certification requirement reaches is a matter for the courts, and a reader who wants the current status of any case should check the court's docket rather than trust a headline. For the myths that surround the debate, see Seven Myths About DEI Programs, Including That Critics Oppose Diversity.
The case in brief
- Contractor affirmative action was created by executive order in 1961 and 1965, expanded by the Philadelphia Plan in 1969, and ended by Executive Order 14173 in 2025. Congress never legislated the regime.
- The Civil Rights Act of 1964, the only statute in the story, set a rule of nondiscrimination and disclaimed quotas in Section 703(j).
- The Supreme Court narrowed the room for preferences in steps: Bakke (1978), Adarand (1995) and Students for Fair Admissions (2023).
- A policy built on a pen can be undone by a pen. Lasting law is made by statute, and the honest path for either side is to win the vote.
What you can do: read Title VI and Section 703(j) of the Civil Rights Act on Congress.gov and compare their wording with the language your employer or university uses in its own policies.