Voluntary self-identification questions: should you answer?

Short answer: answer them. The four questions at the bottom of the form - race and ethnicity, gender, veteran status, disability - are stored apart from the rest of your application, and in at least one major applicant tracking system they sit behind a permission that most people at the company do not have. Declining is fine too. What is not true is the thing most people assume, which is that declining leaves the box empty.

It does not. "Decline to self-identify" is a value, it is counted, and it goes into the same report as every other answer. So the choice is not between answering and staying invisible. It is between four answers you picked and four answers you picked by not picking.

What each of the four questions is actually checking

These questions are not there because someone in recruiting was curious. Each one exists to feed a counting obligation that landed on the employer years before you opened the tab.

Two things in that table are worth pulling out. The EEO-1 counts employees, not applicants - it is a snapshot of who works there, filed annually, and the deadline to submit and certify the 2024 report was June 24, 2025. And the thresholds are real cutoffs, but there are two of them: a private employer files at 100 employees and not at 90, while a federal contractor files at 50 and not at 49. If you are applying to a twelve-person contractor as an Electrician, the self-ID block on their careers page is there because the job board template put it there, not because anyone will report it.

The parallel collections use the same cutoff. Local referral unions with 100 or more members file the EEO-3. State and local governments with 100 or more employees file the EEO-4. Public elementary and secondary school systems with 100 or more employees file the EEO-5. None of them is running on schedule. The EEOC's own collections page currently lists the 2024 EEO-3 and EEO-5 collections as delayed, the 2024 EEO-1 as closed with 2025 updates pending, and the EEO-4 last collected for 2023. The obligation behind the question on your screen is a filing the employer may not actually be making this year.

Who actually sees your answer

This is the question people mean when they ask whether they should answer, so here is the mechanism from the one vendor that publishes it plainly.

Greenhouse calls its version the EEOC questionnaire - "a set of federally-approved questions about race, gender, veteran status, and disability status." Its documentation is unusually direct about what happens next. Candidate responses are anonymized. The report they feed shows the total number of applicants and hires per demographic, and it is "only accessible by users with Site Admin level permissions" who additionally hold a permission called Can see EEOC and demographic reports. Greenhouse states flatly that "it is not possible to associate responses to EEOC questions with individual candidate applications."

Read that last sentence with the hiring manager in mind. The person deciding whether to phone-screen a Registered Nurse is, in a Greenhouse-run process, not a Site Admin, does not hold that permission, and could not tie a disability answer to a name if they did.

It also helps to know what the report they cannot see actually contains. Greenhouse describes it as the total number of applicants and the total number of hires per demographic. Two columns of counts, one row per category. There is no per-candidate view to open, so whoever eventually reads it is looking at a count beside a category label - a different object entirely from a list of names with attributes attached.

That makes the self-identification block the safest set of questions on the whole application, and it is the one people most reliably leave blank. The desired-salary field is a negotiating position. The sponsorship question routes you to a knockout rule. The self-ID block is the only part of the form documented as being walled off from the people making the decision - and it is the part candidates treat as the risky one.

The honest limit on that claim: it is one vendor's documentation of one product. Workday, iCIMS, Ashby and the rest each have their own configuration, and a small employer running applications through a shared inbox has no wall at all. Nothing I opened tells you which system is behind the form you are looking at, and there is no public dataset comparing outcomes for candidates who answered against candidates who declined.

Does answering improve your odds?

No. Nothing in the EEOC or OFCCP material describes these answers reaching a screening decision, and nothing in the vendor documentation provides a path for them to. Anyone selling you a strategy for this block is selling you a strategy for a field the decision-maker cannot read.

The one place a blank does get filled in for you

Here is the part that changes how you should think about "prefer not to say", and it is not on the application - it is after you are hired.

The EEOC publishes suggested wording for employers collecting race and ethnicity from their own workforce. Its questionnaire contains this line:

"If you choose not to self-identify your race/ethnicity at this time, the federal government requires this employer to determine this information by visual survey and/or other available information."

The same questionnaire says the data "will be kept confidential" and that "submission of this information is voluntary and refusal to provide it will not subject you to any adverse treatment." Both are true at once, and the combination is the whole point: your refusal cannot be held against you, and it also does not produce a blank. A Store Manager who skips the race question on day one still ends up in a category on the EEO-1 - someone in HR picks it by looking.

At the application stage there is no visual survey; nobody is guessing at your race from a resume for reporting purposes. But if the reason you decline on the form is that you would rather nobody record it, understand that the record gets made either way once you are on payroll, and that the version you write is the accurate one.

The disability question, and what the numbers around it do and do not say

The disability item is the one people agonise over, usually with a version of "if I tick yes, will I be quietly dropped?" The counting logic behind the question is the opposite: the form exists so that employers can show they are hiring people who tick yes.

Labor force measures by disability status, 2025 annual averages

The gap the Section 503 counting requirement was built to make visible. These are population-wide figures, not outcomes for people who answered a self-ID question.

	Persons with a disability	Persons without a disability
Unemployment rate	8.3%	4.1%
Employment-population ratio	22.8%	65.2%
Usually worked part time	About 30%	About 17%

Those are BLS annual averages for 2025, released March 3, 2026. The unemployment rate for people with a disability rose by 0.8 percentage point over the year, against a 0.3 point rise for everyone else.

Now the caveat that matters more than the figures. None of this tells you what happens to your application when you tick yes. It is population data about who is working, not candidate data about who got called back, and no such candidate dataset is published by anyone. Treat the gap as the reason the question exists, not as evidence about your outcome.

There is one practical consequence of the counting logic worth naming. Because the answer is aggregated into a total rather than attached to your candidate record, a yes on that item is only ever useful to the employer in bulk - and it cannot be held against you inside a system that never stored the link between the answer and the person. That is not a moral argument for answering. It is the reason the mechanism has the shape it has.

The veteran item has a similar shape. In its 2025 annual figures, released April 28, 2026, BLS counted 17.3 million veterans - about 7 percent of the civilian noninstitutional population age 18 and over - with an unemployment rate of 3.5 percent, below the 4.2 percent rate for nonveterans. As of August 2025, 50 percent of Gulf War-era II veterans reported a service-connected disability, against 34 percent of all veterans. A Software Engineer leaving the service will often be answering yes to both the veteran and the disability question, and those are two separate records serving two separate obligations.

The forms are changing under you, right now

If you have filled in a lot of applications this year and thought the block looked different from one to the next, you are not imagining it.

The EEOC's July 21, 2026 proposal to rescind the EEO-1 through EEO-6 reports

$275MAnnual cost to employers the EEOC cites

$4MAnnual cost to the EEOC to administer the collection

30 daysComment period from Federal Register publication

On July 21, 2026 the EEOC announced a proposed rule to rescind the requirement to file annual reports summarising aggregate race and sex data, covering the EEO-1 through EEO-6 collections, along with the related recordkeeping rules. The Commission put the current collection's cost at almost $275 million a year on employers and almost $4 million on itself, gave 30 days for comment from Federal Register publication, and held a public hearing on August 11, 2026.

Separately, on August 21, 2026 the Department of Labor published a final rule modifying the Section 503 regulations. The OFCCP's own page says that "as a result of this rule, the self-identification form will be discontinued, effective September 21, 2026."

A proposal is not a rule, and these two are at different stages. The EEOC's rescission is still a proposal - the comment window and the hearing have both passed, and no page I can open says a final rule has issued or what a court would do with one. The Section 503 change is finished and carries a date. Neither changes what you should type. A question that is on the form in front of you is on the form, and a rule that removes it next month removes it for the employer, not for your application. Practically: a Warehouse Associate who filled in the disability item on a contractor's form in June may find it simply gone from the same form in October, and the race and gender questions may follow - while that same contractor keeps three years of outreach records under the recordkeeping obligation the Section 503 FAQs still describe at 41 CFR 60-741.44(f)(4).

If the form gives you no "prefer not to say"

It should. Every version I have seen ships with one: Greenhouse lists "Decline to Self Identify" for race and gender and "I don't wish to answer" for veteran status and disability, and counts each as its own row. If a form genuinely forces a substantive answer, it is a badly configured form, and the fix is not to invent an answer - leave the whole block if the system lets you submit, and if it will not, this is the record you are creating:

Race/ethnicity: Decline to Self Identify Gender: Decline to Self Identify Veteran status: I don't wish to answer Disability: I don't wish to answer

That is a complete, valid application record. A Controller who submits exactly that has not flagged anything, has not been filtered, and has answered four questions.

The one thing to get right

Fill the block in truthfully, once, and stop thinking about it. It is walled off from the people reading your resume in the systems that document their behaviour, it feeds a count and not a decision, and the alternative - leaving it - is not the neutral act it feels like, because the decline is stored as an answer and, after you are hired, gets supplied for you by observation.

Then spend the attention you just freed up on the questions that do route you somewhere: desired salary, sponsorship, notice period, the free-text box asking why this company. Those get read by a person.

If retyping the same block into every form is what makes you skip it, HeroApply answers the screening questions from your resume so the four you actually have to decide are the only ones left.