Pedagogue Systems

← The Brief

The EEOC proposed ending the workforce report employers have filed since 1966.

Three separate actions moved: the EEOC proposal, a Colorado law passed back in June, and a federal rule that touches hiring tools. Europe's AI disclosure duty went live the same week.

By Pedagogue Systems · August 2, 2026

The EEOC proposed ending the EEO-1, and the dates are close.

Start with what the report is, because the proposal reads differently once you know. The EEO-1 is an annual filing with the Equal Employment Opportunity Commission. It applies to private employers with 100 or more employees. It also applies to federal contractors with 50 or more employees and contracts of at least $50,000. A covered employer picks one pay period in the last quarter of the year. It then counts its workforce as of that snapshot. The count is split into ten job categories, then crossed with sex and with seven race and ethnicity categories. That is the whole report. It carries no individual employee records, and no pay data today. A separate collection did gather pay and hours for 2017 and 2018 before the Commission discontinued it.

The report exists because of Title VII. Congress passed the Civil Rights Act in 1964, and section 709(c) gave the Commission authority to require employer records and reports. The first EEO-1 followed in 1966. Five sibling reports came between 1967 and 1975, covering apprenticeship programs, labor organizations, state and local governments, school districts and colleges. Two of them are already dormant. The Commission stopped collecting the EEO-2 in 1981 and the EEO-6 in 1993.

On July 21 the Commission voted 2 to 1 to propose rescinding all six, along with the related recordkeeping requirements under 29 CFR part 1602. The notice published July 23. A public hearing is set for August 11, requests to testify were due August 7, and written comments are due August 24. The Commission says the reports are inconsistent with equal employment opportunity law and potentially unconstitutional. This is a proposal and not a final rule. Filing obligations stand until a final rule issues.

Colorado has already legislated for the other outcome, and the mechanism is the part worth understanding. Colorado reporting entities file a periodic report with the Secretary of State. It is routine corporate housekeeping that keeps the entity in good standing. HB 26-1207, signed June 4, attaches workforce demographics to that filing. From July 1, 2027, a private entity doing business in Colorado with 100 or more workers has to include EEO-1 data in it. The duty only reaches firms that were federally required to file an EEO-1 as of March 1, 2026. Government entities are excluded. The statute requires that filing even if the federal government repeals the federal requirement. It pins the data to the federal form as it stood on March 1, 2026. There is no single statewide due date. Filing follows each entity's own reporting schedule, which is not identical for everyone. One question is unsettled. The statute does not say whether an employer reports Colorado employees only or its whole workforce.

A separate federal action landed the same week, on the framework that touches hiring tools. It has a longer history than the EEO-1, and the last eighteen months of that history explain the timing.

In 1971 a unanimous Supreme Court decided Griggs v. Duke Power. It held that an employment practice can violate Title VII if it disadvantages a protected group and is not job-related. That holds even where nobody intended to discriminate. That is disparate impact. Four agencies jointly adopted the Uniform Guidelines on Employee Selection Procedures in 1978: the EEOC, the Civil Service Commission, the Labor Department and the Justice Department. OPM later succeeded the Civil Service Commission. The Supreme Court narrowed the doctrine in Wards Cove Packing Co. v. Atonio in 1989, and Congress addressed it again in the Civil Rights Act of 1991. They govern selection procedures, meaning any test, interview, application form or screen used to make an employment decision. The best-known part is the four-fifths rule, and it is a rule of thumb rather than a legal test. If a procedure selects one race, sex or ethnic group at less than four-fifths the rate of the highest-selected group, enforcement agencies generally treat that as a sign of adverse impact. Smaller gaps can still count. Larger ones may not. It depends on sample size and statistical significance. Where adverse impact shows up, the employer has three routes. Drop the procedure, change it, or support keeping it with evidence that it is job-related. That is the framework the adverse-impact testing tools are built against.

The recent chain runs through two executive orders. In January 2025 one revoked Executive Order 11246, the contractor rule that carried its own EEO-1 filing requirement, and the Labor Department proposed rescinding the related regulations that July. In April 2025 a second order told every federal agency to deprioritize disparate-impact enforcement. It also told them to flag regulations imposing it for repeal or amendment. The Justice Department describes its June 9 opinion, which found the Guidelines unlawful, as supporting that order. OPM in turn cites that opinion as the legal basis for its own rule.

OPM removed references to the Guidelines from federal civil service regulations, effective July 31, with comments closing September 29. Read the scope carefully, because it is narrower than the coverage suggests. OPM stripped cross-references out of its own Title 5 rules, which govern federal personnel. It did not repeal the Guidelines. The full text stays on the books in two other places. It sits at 29 CFR part 1607, the EEOC's copy and the one that reaches private employers. It also sits at 41 CFR part 60-3, which reaches federal contractors. This rule touches neither, and it is not part of the EEO-1 proposal.

Pedagogue Systems' view. An operator with 100 or more employees now has a federal filing obligation whose future is unsettled, and a state version pinned to a form that may stop existing. The near-term work is a calendar entry and a decision about whether to comment.

Europe's dates arrived.

In July we reported that the EU had approved the package resetting its AI Act calendar, and that it still had to take effect. It has.

The calendar is the thing people get wrong, so start there. The AI Act entered into force on August 1, 2024, and its duties arrive in stages rather than all at once. Prohibited practices and the AI-literacy duty started February 2, 2025. Rules for general-purpose models started August 2, 2025. August 2, 2026 was always the date most of the remainder arrived. The omnibus moved some of that and left some of it alone. Three dates now matter, and each does something different.

July 27 is when Regulation (EU) 2026/1744 entered into force. It is an amending act rather than a standalone rulebook. Its legal effect comes through the provisions it inserts, replaces and postpones in the AI Act, so entry into force is the moment those edits became part of that law.

August 2 is when the duty we flagged in July began to apply. It sits in Article 50, the transparency article, and the omnibus left it in place. From that date, and subject to the article's exceptions, providers of AI systems that interact directly with people have to tell people they are dealing with an AI, unless that is already obvious. Deployers carry their own notice duties, covering emotion recognition, biometric categorization, deepfakes, and unreviewed AI-generated text on matters of public interest. Those duties carry carve-outs too, including certain law-enforcement uses and ordinary editing that does not change the substance of what a person wrote. Penalties run to 15 million euro or, for an undertaking, 3 percent of worldwide turnover, whichever is higher, with lighter treatment for smaller firms.

December 2, 2026 covers a narrower duty. Article 50(2) requires providers of systems that generate synthetic audio, images, video or text to mark those outputs in a machine-readable format, and to provide a way to detect that mark. This is a signal carried inside the file rather than a visible label. Systems already on the EU market at August 2 have until December 2. Systems placed after that date comply on placement. Do not confuse this with December 2, 2027, when the high-risk duties for hiring tools land.

One more provision changed, and it is older than it looks. Article 4 has applied since February 2, 2025. It used to require providers and deployers to ensure a sufficient level of AI literacy among staff. It now requires them to take measures to support its development. It binds providers and deployers inside the Act's scope, which is most firms running AI in the EU. What is new is supervision. Under Article 113 the Regulation applies from August 2, 2026, which is when the enforcement machinery reaches Article 4. One Commission page words that as August 3, but the legal text says August 2.

Pedagogue Systems' view. The literacy change reads as a relaxation and largely is one. It also moves the target. You are no longer asked to prove a competence level. You are asked to have taken measures. The Act does not prescribe a particular record, but measures you cannot describe are hard to evidence, so write down what you did and when.

What we are watching.

The EEOC hearing is August 11. Comments on it close August 24. The OPM rule takes comments until September 29. In Europe, systems sold before August 2 have until December 2 to add the marking. Anything launched since then must do it now.

About Pedagogue Systems. Pedagogue Systems builds Cassion, a governed data foundation for staffing operations. It serves shift-based, credential-heavy operators in healthcare, industrial, and aviation staffing. Every edge is a decision. It helps staffing operators keep operational records attributable and auditable before they automate decisions.

Sources.

This Brief was produced with AI assistance and adversarial review, then edited by a human before publishing. AI and people both make mistakes, so please verify anything critical independently. How we produce the Brief.

← Back to the Brief