The pre-offer version usually shows two boxes, because the sample form at Appendix B uses two: I IDENTIFY AS ONE OR MORE OF THE CLASSIFICATIONS OF PROTECTED VETERAN LISTED ABOVE, or I AM NOT A PROTECTED VETERAN. Appendix B is a model, not mandated wording, so a third box such as “I don’t wish to answer” is equally lawful. What no invitation is required to ask is which classification you belong to.

Both invitations come from 41 CFR 60-300.42. Answering is voluntary for you. Asking is not optional for an employer with 50 or more employees and a covered contract, the group that section reaches; a twelve-person contractor may lawfully never ask. The rule is under revision: OFCCP proposed amendments at 90 FR 28485, comments closed September 17, 2025, and no final rule had issued as of July 21, 2026. Nothing in that proposal touches the self-identification invitation.

What counts as a protected veteran?

Four categories, defined at 41 CFR 60-300.2. Meeting any one is enough. Three turn on service history alone; the disabled-veteran definition has two prongs, a VA compensation entitlement or a discharge caused by a service-connected disability.

The regulation’s umbrella sentence:

“Protected veteran means … a veteran who may be classified as a ‘disabled veteran,’ ‘recently separated veteran,’ ‘active duty wartime or campaign badge veteran,’ or an ‘Armed Forces service medal veteran,’ as defined by this section.” (41 CFR 60-300.2(q))

Underneath all four sits a broader baseline: a “veteran” here served in the active military, naval, or air service and “was discharged or released therefrom under conditions other than dishonorable” (60-300.2(ee)). Other than dishonorable is a wider door than honorable, and that word is where the confusion with federal veterans’ preference begins. Your clearance status runs on a separate clock.

Why does every contractor application ask this?

Because a federal contract clause makes the employer ask, count, and report. The authority is VEVRAA at 38 U.S.C. 4212, whose most consequential sentence for a job seeker is about where the posting goes.

“each such contractor for each such contract shall immediately list all of its employment openings with the appropriate employment service delivery system … except that the contractor may exclude openings for executive and senior management positions and positions which are to be filled from within the contractor’s organization and positions lasting three days or less; (B) each such employment service delivery system shall give such qualified covered veterans priority in referral to such employment openings” (38 U.S.C. 4212(a)(2))

The question and the listing duty are two halves of one machine. The employer pushes openings into the public workforce system, that system refers covered veterans first, and the self-identification data measures whether it worked. OFCCP names the applicant-side benefit in its VEVRAA FAQ: “By self-identifying, you could potentially become a priority referral for job openings.” The employer’s view is the mandatory job listing.

Two thresholds do different jobs here, and confusing them is the expensive mistake. Coverage of the whole part is set at 41 CFR 60-300.4(a)(1): “Contracts and subcontracts of $100,000 or more are covered by this part.” No employee count appears there, and none appears in the statute. A 30-employee contractor on a covered prime contract owes the equal opportunity clause, the listing of every opening, and the flow-down to its own $100,000 subcontracts. The 50-employee test in 60-300.40(a) governs one subpart only: the written affirmative action program, due within 120 days of contract start, together with the self-identification invitation, the hiring benchmark and the applicant data collection. The figure binding an award signed today is $200,000, after the FAR Council raised acquisition-related thresholds for inflation effective October 1, 2025, up from $150,000; FAR 22.1303 still carries it (FAC 2026-01, March 13, 2026). The wider frame: the OFCCP compliance picture.

Does checking the box improve your odds of being hired?

Not inside the employer’s selection process, on any source we could find. The one concrete benefit a primary source names is priority referral through the public workforce system, which operates before the employer screens you. The equal opportunity clause says listing openings “does not require the hiring of any particular job applicants or from any particular group of job applicants.” On benchmarks, 41 CFR 60-300.45 is blunter: “Quotas are expressly forbidden.” Neither answers the question, and no regulation we read says self-identifying helps or hurts a candidacy. One provision does touch the employer’s own hiring decisions: under 41 CFR 60-300.44(f)(2)(ii)(F) a contractor “should consider applicants who are known protected veterans for all available positions for which they may be qualified” when the one applied for is gone. That sits on an explicitly illustrative menu: a practice to adopt, not a right.

Contractors that must write an affirmative action program, again the 50-or-more group, also set an annual benchmark: the national percentage of veterans in the civilian labor force published by OFCCP, or a self-computed figure from five listed factors. Smaller covered contractors set none. We print no current percentage: OFCCP’s benchmark page loads normally, but the number lives inside a database application that renders only in a browser, so it could not be read on July 21, 2026.

What your answer does is enter a count. Under 41 CFR 60-300.44(k), the contractor documents annually and keeps for three years five figures: applicants “who self-identified as protected veterans pursuant to 60-300.42(a), or who are otherwise known as protected veterans”; total job openings and jobs filled; total applicants; protected veterans hired; and total hired. Read the first one slowly. It is not a count of checkboxes: an applicant the contractor otherwise knows to be a protected veteran belongs in that number whether or not they ticked anything. The count feeds a required annual evaluation of whether veteran outreach worked, and none of it is a thumb on a hiring manager’s scale.

What happens to the answer after you give it?

It enters a confidential record, an annual count, and one aggregate line on a federal form. As a rule it does not reach the hiring manager.

41 CFR 60-300.42(c) makes the invitation carry four guarantees: the request is voluntary, the answer stays confidential, refusing brings no adverse treatment, and the data will not be used in a manner inconsistent with the Act.

The post-offer invitation has a window closed at both ends. 60-300.42(b) says it “shall be made at any time after the offer of employment but before the applicant begins his or her job duties.” An employer that folds it into week-one onboarding has missed the window on every hire. Once a year the aggregate goes to the Department of Labor on the VETS-4212 report, due no later than September 30.

That report counts total protected veterans without breaking them out by category, which is precisely why the post-offer invitation does not have to ask the category either. OFCCP says so: because the report takes the data in aggregate, “contractors are not required to invite self-identification by category in order to comply with VEVRAA’s post-offer invitation requirement.” Asking by category is permitted, not required; a form that only asks yes or no is compliant.

Is a protected veteran the same as a veterans’ preference eligible?

No. Veterans’ preference is a federal civil service mechanism under 5 U.S.C. 2108; protected veteran status is a contractor obligation under VEVRAA. A contractor job is not a federal job, even inside a federal building.

Preference under 5 U.S.C. 2108 attaches to specific service windows and requires discharge “under honorable conditions,” stricter than VEVRAA’s other-than-dishonorable. It operates arithmetically: OPM’s Vet Guide describes five points added to a passing examination score, with 10-point preference requiring Standard Form 15. Nothing in the contractor world adds points to anything.

OPM’s guide names qualifying campaigns for preference: El Salvador, Lebanon, Grenada, Panama, Southwest Asia, Somalia and Haiti. That is OPM’s preference list, not the VEVRAA test, which points to badges authorized under laws administered by the Department of Defense and carries none of preference’s service-length or honorable-discharge conditions. Holding one is not by itself an answer. Which employer you are applying to: contract jobs versus federal jobs.

Does declining the question keep you out of the data?

It removes you from one counting mechanism, not from the employer’s knowledge and not from the protections. Two provisions say so directly.

A contractor’s knowledge of veteran status “may be obtained in a variety of ways,” including the invitation, voluntary disclosure by employees, or the contractor’s actual knowledge. And 41 CFR 60-300.42(f) closes the loop: nothing in the rules “relieves the contractor of its obligation to take affirmative action with respect to those applicants or employees who are known to the contractor to be protected veterans.” A discharge date inside the last three years, printed beside the clearance line near the top of a resume, states the recently separated test on its face. That is our reading of how far actual knowledge reaches, not a line in the regulation.

Where an employer does ask by category after an offer, the sample form carries a middle setting almost nobody uses. Alongside the four category boxes and the flat “I am NOT a protected veteran,” Appendix B offers: “I am a protected veteran, but I choose not to self-identify the classifications to which I belong.” That confirms status without disclosing a disability or a deployment history. On an aggregate-only form it will not appear, because there are no categories to decline.

For employers: does posting the req on a private board discharge the listing duty?

By itself, no. This is the most misread part of VEVRAA, and it cuts against our commercial interest, so we state it in the regulation’s terms rather than ours.

The equal opportunity clause at 41 CFR 60-300.5(a) makes the state workforce agency job bank or the local employment service delivery system the channel that satisfies the requirement. A privately run job service satisfies the obligation “if the privately run job service or exchange provides the information to the appropriate employment service delivery system.” ClearedJobs.NET is a private board. Posting a cleared req with us reaches clearance holders; it is not the compliance channel. The ESDS listing is, and a contractor treating a niche board as a substitute has a finding waiting for it. Listing with a veterans’ job bank appears at 60-300.44(f)(2)(ii)(G) as something a contractor “should consider”: sourcing advice, not a mandate.

Three carve-outs matter for cleared work, and they are statutory before they are regulatory: the passage quoted above excludes executive and senior management positions, positions filled from within, and positions lasting three days or less. Openings occurring and filled outside the fifty states, DC and the listed U.S. territories fall outside the listing provisions, which is why OCONUS work often never reaches a state system. For fully remote reqs, OFCCP has said there is no fixed place where the job occurs, so it may be listed anywhere qualified candidates might be found; name a duty station and it must be listed there. The mechanics: what a contractor must list, and where. The trade-offs: where to post cleared jobs.

Frequently Asked Questions

Do I stop being a protected veteran after three years?

Only the recently separated category expires. Its definition runs for the three-year period beginning on your discharge or release from active duty. The other three definitions in 41 CFR 60-300.2 carry no time limit at all.

What if I check yes before the offer and skip the form afterward?

OFCCP addresses this in its VEVRAA FAQ: an applicant who self-identifies as a protected veteran pre-offer but not post-offer may still be identified as a protected veteran for compliance purposes. The first answer is not discarded because the second went unanswered.

Can the hiring manager see my answer?

60-300.42(e) tells the contractor to keep all self-identification information confidential. The section itself lists no exceptions; the sample form at Appendix B names three: supervisors and managers on work restrictions and accommodations, first aid and safety personnel where a condition might require emergency treatment, and OFCCP or ADA enforcement officials. Ordinary use in a selection decision is on nobody’s list.

What can I do if a contractor ignores these rules?

Under 38 U.S.C. 4212(b), a veteran who believes a federal contractor has failed or refused to comply “may file a complaint with the Secretary of Labor, who shall promptly investigate such complaint and take appropriate action” under the contract and applicable law.

The precision is the point

Two boundaries before anyone acts on this. Whether you are “entitled to compensation … under laws administered by the Secretary of Veterans Affairs” is the VA’s determination, not the employer’s and not ours; check your rating decision before you tick DISABLED VETERAN. Whether a listing practice satisfies 60-300.5(a) in a given state is a question for OFCCP or your own counsel, not a job board.

Inside those limits, “I’d rather not say” is a weaker answer than it looks. It does not hide you: an employer may learn your status from your resume or your own words, its obligations attach either way, and the 60-300.44(k) count picks up veterans the contractor otherwise knows, so the row can be filled in without you. What a blank box forfeits is the one benefit a primary source names, OFCCP’s statement that self-identifying “could potentially” make you a priority referral through the public workforce system. The question is a measurement instrument wearing the costume of a preference. Read the four definitions, decide which describe you, and answer the one you can defend on the text, the discipline that also runs through finding the employers who sponsor clearances.