If you hold a federal contract, you have to ask job applicants whether they are a protected veteran. Not once. Twice. There is a pre-offer ask and a post-offer ask, and they are not the same question. Get the timing or the wording wrong, and an OFCCP audit can flag it fast.

The rule lives in 41 CFR 60-300.42. It comes out of VEVRAA, the law that requires federal contractors to take affirmative action to employ and advance protected veterans. The self-identification invitation is how you collect the data that proves you are doing it.

This guide walks through what the invitation must say, when to send each one, the difference between the pre-offer and post-offer versions, and how the answers feed your VETS-4212 report and your hiring benchmark. I will keep the rule and the example side by side so you can build a form that holds up.

What is the protected veteran self-identification invitation?

It is a request you give job applicants. You ask them to tell you, on their own, if they believe they are a protected veteran. The point is to count veterans in your applicant pool and your hires. That data backs up your affirmative action program.

The word "invitation" matters. You are inviting, not requiring. An applicant can decline. Refusing to answer cannot count against them. That voluntary part is baked into the rule, and your form has to say so in plain words.

VEVRAA covers federal contractors and subcontractors at or above a dollar threshold. As of October 1, 2025, the coverage threshold for affirmative action duties sits at $200,000. The separate VETS-4212 filing threshold is $150,000. If you are under both, this article may not apply to you yet. If you are at or over them, the invitation is not optional.

What are the four categories of protected veteran?

VEVRAA does not protect every veteran. It protects four groups. Your post-offer form lists all four so the applicant can pick the ones that fit. An applicant can belong to more than one.

You do not need to memorize the fine print of each category. The applicant decides which ones apply to them. For a plain-language breakdown of all four definitions, see our guide on what is a protected veteran and the four categories. Your job is to give them a clean form and a fair chance to answer. If they want to dig into what counts, the OFCCP VEVRAA FAQs spell out each group.

When do you send the pre-offer invitation?

The pre-offer invitation goes to every applicant before you make a job offer. You can fold it into your application materials. A lot of contractors put it right in the online application flow. The rule only says it must reach the applicant before the offer.

Here is the key part people miss. The pre-offer ask is one simple question. It asks whether the applicant believes they are a protected veteran. Yes, no, or decline to answer. You do not ask them to name the category yet. That comes later.

Why split it? Before an offer, you should not be collecting detailed status that could look like it shaped your decision. One broad question keeps the pre-offer stage clean. It still lets you count protected veterans in your applicant pool, which is what the benchmark analysis needs.

When do you send the post-offer invitation?

The post-offer invitation goes out after you extend the offer but before the new hire starts the job. This is the version that lists all four categories. The person can check every box that fits.

The timing window is narrow. It has to happen after the offer and before the first day of duties. Send it too early and you risk collecting status before the offer. Send it too late and you may miss the window the rule sets. Build it into your onboarding so it fires automatically once the offer is accepted.

This second ask is where you get the detail your reports need. The pre-offer count tells you who is in the applicant pool. The post-offer answers tell you the specific makeup of who you hired. Together they let you measure how you are doing against the federal benchmark.

What must the invitation say?

The wording is not freeform. Section 60-300.42 spells out what every invitation has to convey. Miss one of these and the form can be cited as non-compliant. Both the pre-offer and post-offer versions carry the same core statements.

Those four statements are the backbone of a compliant invitation. The pre-offer form then adds the single broad question. The post-offer form adds the list of four categories. Same backbone, different ask.

Can you use your own form or must you use the OFCCP sample?

You do not have to use the government form. OFCCP publishes a sample VEVRAA self-identification form, and it also sits in Appendix B of the regulation. It is a safe default. But the rule lets you build your own as long as it carries the required statements.

If you build your own, treat the four required statements as non-negotiable. Match the language closely. A custom form that drops the confidentiality line or the voluntary line is a citation waiting to happen. When in doubt, copy the sample wording.

One more thing. OFCCP updates the sample form when the VETS-4212 report changes. So pull the current version from dol.gov each cycle rather than reusing a copy from three years back. Old wording can drift out of date.

How does the data feed VETS-4212 and the benchmark?

The self-ID answers are not paperwork for its own sake. They power two things: your annual VETS-4212 report and your veteran hiring benchmark analysis.

The VETS-4212 report goes to DOL VETS each year. It counts how many protected veterans you employed and hired, broken out by job category. The post-offer answers are the raw count that fills it in. No self-ID data means no real numbers to report.

The benchmark is the second piece. OFCCP sets a national hiring benchmark, currently 5.1% as of July 30, 2025. You compare the share of protected veterans among your hires against that target. You measure protected-veteran applicants against total applicants, and protected-veteran hires against total hires. The self-ID counts are what make that math possible.

Missing this benchmark is not an automatic violation. It is a signal to look at your outreach and recruiting. If your veteran hire rate sits below the benchmark, OFCCP wants to see what you are doing to close the gap. That is where a real veteran-sourcing pipeline matters. If you want the deeper view of how the benchmark works in an audit, see our guide on the OFCCP veteran hiring benchmark.

How long must you keep the self-ID records?

You have to hold on to the records. The retention rule is set by 41 CFR 60-300.80. The standard period is two years from the date the record was made or the action was taken. For employers with fewer than 150 employees or a contract under $150,000, the period is one year.

Keep the self-ID data separate and confidential. Store it apart from the regular application file so it does not sit in front of a hiring manager during a decision. That separation protects both the applicant and you. An auditor will ask how you store and limit access to this data.

Where do most contractors slip up?

The invitation rule is simple on paper. In practice, a few mistakes show up over and over in audits and self-reviews.

The first is collapsing the two invitations into one. Some contractors ask for the four categories before the offer. That puts detailed protected status in front of the decision. Keep the pre-offer ask broad and save the categories for after the offer.

The second is a stale form. A self-ID form copied from an old template can carry outdated category names or drop a required statement. Pull the current sample and check it against the four required statements each cycle.

The third is mixing self-ID data into the application file. If the protected-veteran answer is visible to the person making the hire, it undercuts the whole point. Store it separately and lock down access.

The fourth is no follow-through on the benchmark. Collecting the data and then ignoring the result is a missed step. The data is supposed to drive your outreach. If your hire rate is low, your sourcing plan should show how you are reaching more veterans. A guide like our recruiter checklist for screening veteran applicants can tighten the front end of that pipeline.

How does self-ID fit your wider VEVRAA duties?

The invitation is one piece of a larger set of duties. VEVRAA also asks for an affirmative action program, the right job listings with state employment services, the EO clause in subcontracts, and the annual VETS-4212 filing. The self-ID data ties several of those together.

VEVRAA is still in force in 2026. There has been federal rulemaking activity and an executive order rescission touching related programs, so the regulatory picture has some movement around it. The core VEVRAA statute and its self-ID requirement remain on the books. Confirm the current state with OFCCP at dol.gov before you change a process based on news headlines.

For the full picture of contractor duties, start with our overview of VEVRAA compliance for federal contractors. For the recruiting side that the data is meant to drive, see how to write a job description that attracts veterans and our guide to recruiting veterans for government services and contracts.

The data is only as good as the pipeline behind it

You can run a flawless self-ID process and still miss the benchmark. The form counts veterans. It does not find them. If protected veterans are not applying, your numbers stay low no matter how clean your paperwork is.

That is the part most compliance plans skip. The invitation tracks your result. A real veteran-sourcing channel changes the result. You need both: the form to measure, and a steady flow of qualified veteran applicants to measure something worth reporting.

That is where Best Military Resume fits. BMR is a growing pool of veteran and military-spouse talent built specifically for employers who need to source qualified veterans. The pool adds over 1,000 new candidate profiles every month. More than 60,000 resumes have been built on the platform. For a federal contractor working a veteran hiring benchmark, that is a direct line to the applicants your self-ID data is meant to count.

If you want to put real veteran candidates in front of your hiring managers and move your benchmark numbers, reach out to access BMR's veteran talent pool. Compliance proves you are trying. A pipeline proves you are hiring.