If you run hiring for a federal contractor, you have a compliance change on your desk this month that deserves more attention than a routine policy update. On August 21, OFCCP published a final rule in the Federal Register ending the Form CC-305 disability self-identification requirement, along with the 7% utilization goal and the related disability data analyses that have anchored Section 503 compliance programs since 2013. The change takes effect on September 21. That gives you roughly 30 days to unwind a process that has been standard practice for a decade.
I want to walk through why this is tighter than it first appears, what the actual exposure looks like, and what I would be doing this week if I sat where you sit.
The timeline is compressed, and the runway was already shaky
Here is the part that makes this more than a calendar item. CC-305’s OMB approval had already lapsed on April 30. That means contractors spent nearly four months operating in a gray zone, still running a form whose authorization had quietly expired, before this rule arrived to formalize the ending. Now you get a single month to reverse course.
So this is not a leisurely transition. It is a short window to change a workflow that likely touches your applicant tracking system, your onboarding sequence, and every hiring manager who has been trained to treat the self-ID invitation as a required step.
Why the rule exists, and why it matters for how you respond
OFCCP concluded that the self-identification requirement sat in direct tension with the Americans with Disabilities Act, which generally bars employer-initiated disability inquiries before a conditional offer. Ending the mandate resolves that conflict. That reasoning is not incidental. It is the whole reason the smart move here is different from what your instincts might tell you.
The instinct, when a required form goes away, is to find a lighter version of the same thing and keep collecting the data you have grown used to having. Resist that instinct. DOL’s stated position is that the ADA prohibits employer-initiated disability inquiries pre-offer even when they are voluntary. Swapping CC-305 for a similar question of your own design likely is not an option. This is a stop, not a substitution.
What does stay in place: your Section 503 affirmative action plans, your disability outreach obligations, and your accommodation duties all continue. Employees can still volunteer disability information when they request a reasonable accommodation. The core nondiscrimination framework is intact. What is gone is the employer-initiated invitation and the quantitative machinery attached to it.
The real exposure is not where you would expect
Let me be precise about risk, because I think the headline number people look for is the wrong number.
The rule itself does not set a specific fine for missing the deadline. Continuing to use CC-305 past September 20-21 would fall under standard Section 503 enforcement, which begins with conciliation and escalates to contract sanctions or debarment only if that process fails. That is the familiar path, and it moves slowly.
The sharper exposure is the one DOL flagged in the rule’s own reasoning. Once the mandate is gone, a pre-offer disability question sits squarely in ADA territory. That is a separate liability from anything OFCCP would impose directly, and it does not run through OFCCP’s conciliation-first process. If you keep asking the question after the requirement ends, you are no longer a contractor complying with a federal directive. You are an employer making a pre-offer disability inquiry on your own initiative, and the ADA framework treats that very differently.
That distinction is the whole game. The old form was a shield precisely because it was mandated. Strip the mandate away and the same question becomes a source of risk.
What I would do this week
Check whether your onboarding flow or applicant tracking system still serves this form. Many systems do, because the form was required for years and got wired deep into standard hiring templates. If it is still firing, that is your first fix.
Then, given the compressed timeline and the ADA angle, loop in legal counsel rather than treating this as a routine HR change. I do not say that reflexively. Most compliance updates can be handled inside the HR function. This one carries a liability shift that sits outside OFCCP’s usual enforcement lane, and the window to get it right is short. That combination is exactly when counsel earns its keep.
The contractors who handle this well will treat the next few weeks as a system audit, not a memo. Find every place the form lives, shut those pathways off cleanly, confirm your outreach and accommodation processes are untouched, and document the change. The ones who struggle will be the ones who let the form keep running quietly in an ATS nobody thought to check.
That means all of your ATSs that operate US jobs, and any extension of your ATS that allows candidates to apply for US jobs on a job board, social media site, kiosk, website form, and paper applications.
Thirty days is enough time to do this right. There is not enough time to do it late.
The takeaway for how you run hiring
Step back from the specifics for a moment. What this change really underscores is that compliance is not a set of forms. It is the sum of what your hiring systems actually do, step by step, whether or not anyone is watching them. CC-305 became risky the day it stopped being required, and the contractors who get caught out will be the ones whose systems kept doing what they were configured to do long after the reason for it disappeared.
A hiring operation is only as compliant as its least-examined workflow. When a rule changes at the pace this one did, the winners are the teams who can see clearly what their applicant tracking and onboarding systems are doing, and change it fast, without a three-month project and a prayer. The gap between a policy change on August 21 and a corrected workflow by September 20 is exactly the gap that good hiring infrastructure is built to close.
So handle CC-305 now. But use it as a prompt for the larger question too: when the next rule lands with 30 days’ notice, will you be able to find every place it touches and fix them cleanly? That readiness is not a compliance nicety. It is operational discipline, and it is what separates the contractors who treat regulatory change as a fire drill from the ones who treat it as a Tuesday.
Want to talk through how this maps to your own hiring stack? That is exactly the kind of operational detail we spend our days on at JobSync.
About The Author
