Last month I wrote about the thirty-day window OFCCP handed federal contractors to stop using Form CC-305. I framed it as a workflow problem: find the form in your applicant tracking system, shut it off, bring in counsel because of the ADA angle, and move on. If you are a federal contractor and you have not done that yet, stop reading and go do it. You have roughly one week.
That framing was correct as far as it went. But two things have come into focus since, and both tell me the workflow lens understates what is actually happening. The first is that the same rule-making that ended CC-305 also completes the rescission of the regulations behind the Internet Applicant Rule, and takes the only federal definition of a “job applicant” down with it. The second is that the ADA theory underneath all of this is not new. It has a fact pattern in case law that predates this rulemaking by more than two decades, and it reaches any pre-offer disability inquiry, regardless of how that inquiry began.
Taken together, these are not two compliance updates. They are a change in the ground you have been standing on. Let me walk through what that means for how you operate, not just how you comply.
CC-305 was a compliance form, not a medical intake form
This distinction gets lost, and losing it leads people to the wrong conclusion about why the rule exists. CC-305 asked a single question about disability status, offered “I don’t want to answer” as a valid response, and served as the OFCCP-approved mechanism for the voluntary self-identification that Section 503 has required contractors to solicit since 2013. Contractors ran it because the government told them to. It is not the same species of document as a health-history intake form asking about two dozen named conditions, and it was never adopted for the same reasons.
Hold that distinction while you read OFCCP’s stated rationale for eliminating it. The final rule does not say CC-305 data was misused. It does not say any contractor was shown to have discriminated using the form or the data. The rulemaking record contains no finding of that kind. DOL’s argument is structural: the ADA restricts the employer’s act of asking a pre-offer disability question, and DOL concluded that inviting a response, even a voluntary one with a stated opt-out, is still the employer initiating the inquiry. Commenters raised exactly this objection during the rulemaking. They argued that voluntariness and the opt-out should exempt CC-305 from the ADA’s pre-offer bar. DOL rejected the argument, but on grounds of legal conflict, not because it found evidence the form caused harm. The agency’s position is that the regulation follows from the underlying legal authority, independent of how any individual practice is performed.
That is a materially different claim from “this form was used to discriminate.” It is closer to “the form was never legally sound to require, regardless of how it worked in practice.” Those two framings lead to very different conversations with your workforce and your leadership, and only one of them is what the rule actually says. If you are explaining this internally, use the one the rule supports. It is more accurate, and it happens to be less alarming, which is the rare combination worth reaching for.
WOTC and VEVVRA also collect disability data
Two other pre-employment data points get raised in the same breath as CC-305, and they don’t resolve the same way.
Start with the Work Opportunity Tax Credit. Two of WOTC’s ten target groups turn on disability status: the service-connected disability category for veterans, and vocational rehabilitation referral more broadly. Both get collected pre-offer, on Form 8850, which by law has to be completed on or before the day an offer is made. That looks like exactly the practice OFCCP just killed CC-305 for running. It isn’t the same problem, because it doesn’t rest on the same legal theory. The instructions to Form 8850 identify those boxes as a recognized statutory exception to the ADA’s pre-offer bar, written into the law by Congress, not a discretionary reading an agency can unwind through rulemaking. WOTC’s disability question survives OFCCP’s CC-305 reasoning because it was never built on the same foundation.
What actually puts WOTC in contention right now has nothing to do with the ADA. The program’s authorization lapsed December 31, 2025, and Congress hasn’t renewed it. Certifications for 2026 hires are on hold, and if the credit returns, it will likely return retroactively, the way it has after past lapses. That’s a funding and reauthorization problem, not a disability-inquiry problem, and it’s worth keeping the two separate when you brief your team. Keep screening through the hiatus regardless of anything happening with CC-305.
VEVRAA is the cleaner case. It also requires pre-offer solicitation, but the pre-offer invitation only asks whether someone believes they’re a protected veteran, in the aggregate, without naming a category. The regulation deliberately pushes the “disabled veteran” subcategory to the post-offer invitation, where the ADA’s rules are different, since post-offer medical inquiries are broadly permitted as long as they’re required of everyone entering that job. VEVRAA’s drafters built that timing split specifically to keep disability-specific questions off the pre-offer side, two decades before CC-305 became a problem. There’s no live tension here for OFCCP to resolve, because the regulation already put that question on the ADA-permitted side of the line.
The definition of “applicant” disappears on October 26
Since 2006, federal contractors have relied on a four-part test to decide who counts as an applicant for record keeping and adverse-impact analysis. The person expressed interest through an online channel. The contractor considered them for a specific opening. Their submission showed they met the basic qualifications. And they never withdrew before an offer. That test, the Internet Applicant Rule, has been codified at 41 CFR 60-1.3 since February 2006, and its sole authority was Executive Order 11246.
EO 11246 was revoked in January 2025. OFCCP is now formally rescinding the implementing regulations built on it, and most of that rescission, including the removal of the Internet Applicant definition, takes effect October 26, 2026. The four-prong test goes with it.
Here is the part that deserves your attention. Section 503 and VEVRAA survive as standalone statutes, so your obligations to individuals with disabilities and to veterans continue, and both still require counting applicants. But neither statute defines the word on its own, and OFCCP has proposed to leave that definition blank rather than replace it. A recent piece on jobboarddoctor.com framed the four-prong test as a shield rather than a burden: it told contractors exactly whose data had to be counted, tracked, and analyzed, and it gave them a basic-qualifications carve-out to keep unqualified submissions out of the adverse-impact math.
I want to state the mechanical fact plainly, because you do not have to accept any larger argument to see it. After October 26, if you run an AI screening tool, an ATS with automated ranking, or any process that filters candidates before a human looks at them, you will no longer have a federal definition telling you which of those filtered-out people count as someone you were obligated to evaluate fairly. That is a genuinely different position from the one contractors, technology and services have operated in for twenty years.
The four-prong test was often read as a burden. It is worth reframing it as what it also was: a shield. It told you exactly whose data had to be counted, tracked, and analyzed. And it carried a basic-qualifications carve-out that kept unqualified submissions out of your adverse-impact math. That carve-out is the piece I would watch most closely, because “basic qualifications” had its own regulatory gloss. To count, they had to be advertised in advance, non-comparative, and objective. Strip that guardrail away, and a knockout question that screens out, say, an applicant in a disadvantaged ZIP code who lacks a qualification you never advertised as required starts to look less like a neutral filter and more like a decision you will have to defend. The definition did not create that exposure. It gave you a disciplined way to manage it. Removing it does not lower the risk. It removes the instrument you used to keep the risk in bounds.
Reconciling Section 503 without CC-305 data
This is where the two changes compound, and precision matters, because part of it reconciles cleanly and part of it does not.
The clean part: Section 503 no longer carries the 7 percent utilization goal or the disability data analyses that goal required, both eliminated in the same rule that ended CC-305. So there is no live requirement asking you to measure disability representation against a benchmark using data you are no longer permitted to collect. That specific contradiction is gone after September 21. Good.
The part that does not resolve so neatly: your Section 503 affirmative action plan, your outreach obligations, and your accommodation duties all continue. Many of you are mid-cycle on multi-year plans built on the assumption of continued CC-305 collection. Some of you are holding partial-year 2026 data, gathered before the form was pulled, inside an AAP framework that now has no forward-looking data stream to complete it. That orphaned data needs a decision, made with your AAP consultant or counsel, not left to drift: does it stay in the current plan year as a snapshot, get excluded going forward, or trigger a plan amendment?
There is also a retention question that catches people moving too fast. The two-year recordkeeping clock is live under Section 503 and VEVRAA, independent of the revoked order. The CC-305 responses you already collected remain subject to that clock even though you can no longer collect new ones. Purging that data early because the form is gone would be its own violation. The instinct to clean house is understandable. Resist it until the clock runs out.
And if your organization wants to keep some voluntary disability inclusion metric for internal purposes, separate from anything OFCCP requires, understand what you are taking on. You now have to build it without a mandated pre-offer form and, after October 26, without a federal definition of who your applicant denominator even is. That is a design problem, not a checkbox. Whatever you build must run entirely on post-offer or during-employment voluntary disclosure. Nothing pre-offer. Hold that line without exception, because the next section is why.
What ADA exposure actually looks like, mechanically
“ADA fine” is the wrong mental model, and the wrong model is what leads people to underestimate this. Let me give you the accurate one.
There is no regulatory fine schedule for a pre-offer disability inquiry the way there is for an OSHA violation. The enforcement path runs through the EEOC. An individual, or the EEOC on its own initiative, files a charge. The EEOC investigates, attempts conciliation, and if that fails, either sues or issues a right-to-sue letter that puts the person in federal court. A successful claim carries back pay, front pay, reinstatement, attorneys’ fees, and, where the conduct is intentional, compensatory and punitive damages. Those damages are capped by employer size under 42 U.S.C. § 1981a, running from $50,000 per person at smaller employers up to $300,000 per person at organizations with more than 500 employees.
Read that cap carefully, because the intuition it triggers is wrong. The number is per person, and the relevant people are not your employees. They are your applicants. So ask yourself the only question that matters here: how many applicants pass through your systems in a year? A hundred? A thousand? A million? The per-person figure looks modest until you multiply it by an applicant pool, and then it does not look modest at all.
Now the detail that should reshape how you think about the whole thing. Courts have held that a plaintiff does not need to prove they actually have a disability to win a claim over an unlawful pre-offer inquiry. The inquiry itself is the violation. The Tenth Circuit said this directly in Griffin v. Steeltek, holding that a job applicant need not show he is disabled to state a claim under the ADA’s pre-employment inquiry provisions. The EEOC pressed the same theory in EEOC v. Grisham Farm Products, where a company required every applicant to complete a health-history form before being considered, and the court treated the requirement itself as the violation, independent of whether any individual applicant had a covered disability or lost a job because of it.
Let me be fair about the comparison, because the difference in scale is real. CC-305 was never Grisham Farm’s health history. One is a single question with a stated opt-out. The other was a 43-item medical inventory. But the doctrine that would reach a contractor who kept a pre-offer disability question running past September 21, whether that question is CC-305 itself or a lookalike you designed to replace it, is the very doctrine DOL used to eliminate CC-305 in the first place. Voluntariness does not determine lawfulness, because the ADA regulates the employer’s act of asking. That is the theory a plaintiff or the EEOC would bring, and it is precisely the fact pattern that supports group-wide relief rather than a single grievance.
This is where the earlier point about scale becomes concrete. Grisham Farm was an EEOC action reaching a practice applied to the whole applicant pool, not one person’s complaint. Where a private plaintiff brings it instead, a uniform practice applied to every applicant is the textbook setup for a class action, because the same legal question, whether the form itself was lawful, resolves identically for everyone who filled it out. The per-person caps still apply. But they apply per class member, and across a large applicant pool they compound in a way a single charge never could.
So the honest answer to “is this individual suits or class actions” is both, and which one you are more exposed to depends on how uniformly you apply the practice. A stray disability question one hiring manager improvises in an interview is individual-charge risk. A form that goes to every applicant through your ATS is a policy. And policies are what turn into classes.
What the next thirty days ask of you, and the next ninety
Handle the CC-305 shutdown the way I described last time, and treat legal review as non-negotiable given the per-se liability theory above. But do not stop at the form. Extend the audit to the ground underneath it.
Before October 26, get clarity from counsel on how your organization will define “applicant” internally for adverse-impact and AI-screening purposes once the federal definition is gone. That is not a question to leave open. If you wait, a court or the EEOC will answer it for you, in the middle of a dispute, on terms you did not choose. Answering it yourself now, deliberately and on the record, is the far cheaper path.
The contractors who come through this well will be the ones who treat the next ninety days as a chance to rebuild their footing on purpose rather than have it rebuilt for them under pressure. The rules changed. The obligations did not disappear. What disappeared were the instruments that made those obligations manageable. Building your own, before you are forced to, is the work now.
This is the kind of operational detail we spend our days on at JobSync. If you want to think through how these changes map to your own hiring systems, that conversation is one we are always glad to have.
About The Author
