A small process with outsized audit risk

If you hold a covered federal contract, two laws — Section 503 of the Rehabilitation Act (individuals with disabilities) and the Vietnam Era Veterans' Readjustment Assistance Act (VEVRAA) (protected veterans) — require you to invite applicants and employees to voluntarily self-identify into those protected groups. It sounds trivial: a couple of optional questions. But the self-identification invitation is one of the most mechanical, most-audited pieces of OFCCP compliance, and small contractors lose findings on it constantly — not because they discriminated, but because they used the wrong form, asked at the wrong time, or stored the answers in the wrong place.

This piece is a practical walkthrough of the mechanics. It's not legal advice, and the thresholds for which contractors are covered (and at what dollar and headcount levels the full affirmative-action obligations kick in) are worth confirming for your specific contracts. If you're newer to the broader regime, start with the EEO-1 and OFCCP reporting refresher and treat this as the deep dive on the self-ID piece.

You must use the prescribed language — don't write your own

This is the single most important rule, and the one most often broken. The invitations are not yours to phrase:

  • Disability self-identification uses the OFCCP's official form (CC-305). The text, the format, and the regulatory information on it are prescribed. You copy it; you don't paraphrase it, redesign it, or "improve" it. OFCCP periodically revises the form and the version it carries an expiration date — using an expired version is itself a finding.
  • Veteran self-identification language is also prescribed by regulation. You invite applicants to identify as a protected veteran using compliant language, separate from the disability invitation.

Writing your own friendlier wording feels harmless and is a reliable way to fail an audit. Use the templates exactly.

The timing: pre-offer, post-offer, and a periodic re-survey

The invitations happen at specific, distinct moments — and conflating them is a classic error:

  • At the applicant stage (pre-offer). Invite applicants to self-identify as a protected veteran and as an individual with a disability when they apply. This is voluntary and must be kept separate from the hiring decision.
  • At the post-offer / pre-start stage. Invite again after an offer is extended but before the person starts. (The disability invitation is required both pre-offer and post-offer.)
  • Periodically as an employee — at least every five years for disability, with a reminder in the interim that employees may update their status at any time. People's circumstances change; a one-time question at hire doesn't satisfy the ongoing obligation.

The reason for inviting at multiple points is that self-identification is voluntary — many people decline at application and are more comfortable later. The re-survey is how you build the utilization data the affirmative-action obligations are measured against.

Voluntary means voluntary — and confidential means confidential

Two guardrails you cannot get wrong:

  • It is always voluntary. You may not require anyone to answer, penalize a refusal, or treat "I decline to identify" as anything other than a complete, acceptable response. The invitation must say so.
  • The responses are confidential medical/diversity information, stored separately. Self-ID data — especially disability status — must be kept apart from the regular personnel file, treated as confidential, and used only for the permitted analysis. The decision-makers in a hiring or promotion call should not be looking at an individual's self-ID answers. Mixing self-ID responses into the file a hiring manager reads is both a confidentiality breach and a discrimination-claim handed to the other side.

Where small contractors actually slip

In practice the findings cluster around a few avoidable mistakes:

  • Inviting at hire and never again — missing the periodic re-survey obligation.
  • An expired or home-grown CC-305 instead of the current official form.
  • Storing self-ID answers in the main personnel record rather than a separate, confidential location.
  • No documentation that the invitation was made. You need to be able to show the invitation went out at each required stage, not just that you "always do it." Make the invitation a tracked, dated step in your application and onboarding flow, and keep the records on the same clock as your other recruiting records retention.

The bottom line

Self-identification is easy to comply with and easy to fail. Use the prescribed forms exactly, invite at the applicant stage and again post-offer, re-survey employees on schedule, keep every "decline" as a valid answer, store the responses confidentially and apart from the personnel file, and document that each invitation actually went out. None of it requires judgment calls — it requires process discipline, which is precisely why an auditor expects it to be clean. Treat the self-ID invitation as a tracked step in your hiring workflow rather than a form someone remembers to send, and it stops being a finding waiting to happen.