State Veteran Hiring Preference Laws for Private Employers

You have an open role. Two finalists look about the same on paper. One of them spent eight years in the Army moving freight for a transportation company. You want to hire that one.

Then somebody in the room asks the question that ends it. "Are we allowed to do that?"

Nobody has a clean answer. So the preference never gets written down. It stays a private hunch that one manager acts on and the next one does not.

That hesitation is not silly. Preferring veterans really can create legal exposure. But a large and growing group of states has passed laws that speak straight to this. Those laws let a private employer adopt a veterans preference policy. And several of them say plainly that the preference does not break that state's equal employment law.

This post covers what those laws do and which states have one. It walks through what your policy has to say. And it marks where the law stops. We read the published text of every law below before we wrote about it.

Why do employers think they cannot prefer veterans?

The worry has a real basis. It is worth stating fairly before we take it apart.

Title VII of the Civil Rights Act bans job practices that hit one protected group harder than another. That covers rules which look neutral on the surface. Lawyers call this disparate impact.

The veteran population skews male. So a preference for veterans lands unevenly by sex. On the numbers, it helps men more. That is the opening for a sex discrimination claim.

Congress wrote a carve-out for this. It is Section 712 of Title VII, at 42 U.S.C. 2000e-11. Section 712 says nothing in Title VII repeals or modifies any law creating special rights for veterans. That covers federal, state, and local laws.

That reads like a full pass. It is narrower than it sounds.

The EEOC has published policy guidance on veterans preference under Title VII. Its position is that Section 712 covers preferences created by law. It does not cover a preference an employer hands out on its own.

The guidance puts it directly. Say a preference is given on the employer's own initiative. Say no statute mandates it. Then the impact of that preference is not shielded from scrutiny under Title VII.

So the instinct in that meeting is sound. A homegrown preference with nothing behind it carries the most risk. Our guide on sourcing veterans without violating EEO rules makes the same point. It leaves the state question open. This post is that answer.

What does a state voluntary preference statute actually do?

These laws share a shape. Each one is a voluntary veterans preference statute. It tells private employers they may adopt a policy that prefers a veteran. Then it sets the terms.

Minnesota is the cleanest example. Minnesota Statutes 197.4551 lets a private, nonpublic employer grant preference to a veteran. That covers hiring and promotion. It also covers the spouse of a permanently and totally disabled veteran, plus a surviving spouse.

Subdivision 3 is the part employers care about. It says granting that preference does not violate any local or state equal employment opportunity law. That includes Minnesota's own human rights chapter.

Virginia reads much the same. Virginia Code 40.1-27.2 lets an employer grant preference in hiring and promotion. It covers a veteran or the spouse of a disabled veteran. It then states the preference does not violate any local or state equal employment opportunity law.

Ohio Revised Code 5903.15 goes a step further on scope. It reaches hiring, promotion, and retention during a reduction in force. It covers service members, veterans, and their spouses or surviving spouses. It also says the preference is not a violation of any state or local equal employment opportunity law.

The newer laws tend to attach conditions. The policy must be in writing. It must be applied the same way every time. Some states add a posting duty on top.

Which states let a private employer prefer veterans?

Here are eleven whose text we pulled and read. Ten are in effect now. Each one speaks to private employers. The details differ, so read your own state before you draft anything.

• Alabama, HB 307 (2026), Act No. 2026-574: Signed in April 2026 and effective January 1, 2027. The policy must be written and applied uniformly. It covers veterans, spouses of veterans, and spouses of active-duty members. You must also tell the Alabama Department of Workforce that you adopted one.
• Idaho, Idaho Code 65-513: A private, nonpublic employer may prefer people eligible under Idaho Code 65-503. It covers hiring and promotion.
• Illinois, 330 ILCS 56: The Veterans Preference in Private Employment Act. The policy must be written and publicly posted at work or on the company website. Your job application must tell every applicant the preference exists.
• Indiana, IC 10-17-15: The Voluntary Veterans' Preference Employment Policy chapter. The policy must be written and applied uniformly to hiring, promotion, and retention during a reduction in force.
• Kansas, K.S.A. 73-231: A permissive preference in private employment. The policy must be written and applied the same way to every initial hiring decision. The veteran must still meet what the open job calls for.
• Minnesota, Minnesota Statutes 197.4551: Preference permitted in hiring and promotion. The statute says it does not violate any local or state equal employment opportunity law.
• Nevada, NRS 613.385: Preferential treatment in hiring a veteran or a veteran's spouse is permitted. The Nevada Equal Rights Commission may review your policy for uniform application.
• Ohio, Ohio Revised Code 5903.15: Covers hiring, promotion, and retention in a reduction in force. Not a violation of state or local equal employment opportunity law. You may tell the state workforce agency you adopted one.
• Oregon, ORS 408.497: Private-sector employers may prefer veterans and people in uniformed service. It covers hiring and promotion.
• Utah, Utah Code 34-50-103: Part of the Veterans Preference in Private Employment Act. Written, applied uniformly, and publicly posted at the workplace or online.
• Virginia, Virginia Code 40.1-27.2: Preference permitted for a veteran or the spouse of a disabled veteran. The statute says it does not violate any local or state equal employment opportunity law.

This list is not the whole country. Other states have similar laws, and more get introduced most sessions. Alabama is the newest one we found, and it does not take effect until 2027.

These statutes also get amended. Read the current text of your own state code, or have counsel do it, before you adopt anything. If you hire in several states, one policy will not travel cleanly across all of them.

What has to be in the policy for it to hold up?

The conditions are the part employers get wrong. Most of these laws protect a policy, not a mood. Skip the paperwork and you may lose the cover the statute was offering.

Is the policy actually in writing?

Illinois, Indiana, Kansas, Utah, and Alabama all say the policy must be written. Name the statute you are adopting it under. Date it. Have somebody with authority sign it.

Are you applying it the same way every time?

Uniform application shows up again and again in these laws. Nevada makes the point sharpest. A job applicant can file a written complaint under NRS 613.385. The Nevada Equal Rights Commission may then review your policy. If it finds you are not applying the policy uniformly, you have to revise it.

So do not use the preference for one role and drop it for the next. That is worse than having no policy. It builds a record of inconsistency.

Where should you post it?

Illinois wants the policy posted at work or on your website. Your job application also has to tell all applicants the preference exists. Utah has a similar posting duty. That transparency is a feature, because candidates who see it self-select toward you.

How do you verify eligibility?

Illinois names the documents you may rely on. That list covers the DD214, the NGB-22 for National Guard members, and a VA award letter. Kansas asks the veteran to submit proof of service and an honorable or general discharge. Ask for the document, log that you saw it, and move on.

Collecting that data has its own rules. We walk through them in our guide on tracking applicant veteran status legally.

Is it a tiebreaker or a quota?

Illinois and Indiana frame this as a preference over another qualified applicant. Kansas asks only that the veteran meet what the job calls for. The rest say nothing about qualifications at all. Keep the preference between qualified people anyway. Nothing in these laws lets you hire someone who cannot do the job. None of the eleven tells you to set aside seats for veterans. A numeric target is a different legal animal and these laws do not authorize it.

What if your workplace is organized?

Your contract may already govern hiring order, seniority, and recall. A preference policy cannot quietly override that. Our post on hiring veterans into a union workplace covers where those two things meet.

What does a state preference law not do?

This is the part to be honest about. The shield is real but it has edges.

It does not rewrite Title VII. A state legislature cannot change federal law. Minnesota and Virginia say the preference does not violate state or local equal employment law. Neither one says a word about your federal exposure, because neither one can. Title VII still applies to you.

It does not settle every federal question. The EEOC guidance draws its line at preferences created by law. Does a state statute permitting a voluntary policy sit on the protected side of that line? Your counsel should answer that for your own facts. Keeping the policy narrow and documented is what shrinks the risk.

It does not change your federal contractor duties. If you hold covered federal contracts, VEVRAA still governs your outreach, your self-identification invitation, and your recordkeeping. A state preference policy sits alongside those duties. Our breakdowns of VEVRAA compliance for federal contractors and the protected veteran self-identification invitation cover that side.

It does not travel. A policy adopted under Kansas law does not carry into Missouri on its own. Multi-state employers usually need the policy scoped to named states, or a separate version per state.

It does not let you exclude anyone. Preferring a veteran between qualified finalists is one thing. Screening people out for not serving is a different thing, and no state statute here authorizes that.

How does this turn into a sourcing lever?

Most compliance write-ups stop here. A lawful, written preference also changes what your recruiters are allowed to do out loud.

Without one, veteran hiring stays a soft goal. Somebody says they like hiring veterans. Nothing in the process changes. The pipeline looks the same as it did last quarter.

With one, you can say it in the job post. You can name the preference in your careers page. You can send a recruiter into a veteran talent pool with a real reason to be there.

That message travels fast in the military community. Veterans talk to each other about which employers actually mean it. A posted policy is proof, and a vague statement about valuing service is not.

It also sharpens the search itself. Run the preference as a tiebreaker between qualified finalists. So you need enough qualified veteran finalists to get a tiebreak. That is a sourcing problem, not a legal one. We lay out the mechanics in our guide to building a veteran candidate search process.

Geography matters too, since these laws are state by state. If your preference policy covers three states, source hardest in the ones with the deepest veteran population. Our map of which states have the most veterans to hire is a good starting point. Employers running several sites should also read how to source veterans across multiple locations.

Money follows the same logic. Several states pair hiring incentives with their veteran employment push. We track those in state tax incentives for hiring veterans and in veteran hiring incentives beyond WOTC.

One more thing worth knowing before you write the policy. The word "veteran" carries more than one meaning under federal law. The four protected veteran categories do not all mean the same thing. Our post on what a protected veteran is spells out the four.

What should you do next?

Start small. You need a one-page document and a short legal read.

Pull your own state code section first. Check whether it is on the list above. Check whether the text still reads the way this post describes. Then have counsel confirm the current version and its conditions.

Draft the policy next. Written, dated, scoped to the states you hire in, and clear that the preference applies between qualified finalists. Post it where your applicants will actually see it.

Then feed it. A preference only matters if qualified veterans reach your final round.

That last part is where BMR comes in. Over 1,000 new profiles are added every month. Veterans have built 65,000+ resumes on BMR. That pool runs deep in project and program management, IT and cyber, logistics, and cleared government work.

Want access to it? Reach out through our hiring page. We will walk you through the search.

Nothing here is legal advice. State laws change, and your facts matter. Use this to have a sharper conversation with your own counsel.