Veteran Sourcing When Your ATS Has No Veteran Field

Your applicant tracking system has no veteran field. No checkbox on the application. No tag you can search on. So when leadership asks how many veterans applied last quarter, you have nothing to hand them.

You can still run veteran sourcing. You just run it in a different place than most people expect. The move is knowing which data you may track freely and which data carries legal rules. Those are two separate piles, and mixing them is where teams get into trouble.

This guide covers the tooling gap, not the parser. If qualified veterans are sinking in your rankings, read why your ATS is burying qualified veteran applicants. Storing self-identification answers is its own subject. Our guide on tracking veteran status legally owns those rules. This post defers to it. What follows is the workaround. How to tag, count, and report veteran sourcing inside software that will not tag it for you.

What can you track when there is no veteran field?

Split your data into two piles before you touch a setting. The piles look similar on a screen. They are not the same thing.

Pile one is sourcing and channel data. That is where a candidate came from. Which event, which outreach list, which database, which referral. It describes what your team did. You can track it, report on it, and share it.

Pile two is protected veteran self-identification. That is the applicant telling you they are a protected veteran. It is voluntary. It is confidential. If you hold a federal contract, it carries rules about storage and use.

A source code says what your team did. A self-ID answer says something about the person. Keep the two apart and most of this problem gets small.

One line you do not cross. Never guess someone's status from a resume, a name, or an employment gap. And never write a guess into a record as a status flag. A guess is not self-identification. It creates a record you would rather not explain later.

Why should you tag the requisition and not the person?

Most applicant tracking systems ship with a source field on the application. Many also let you tag or fold a requisition. Those two fields can carry your whole program.

Start at the requisition. Flag the req itself as a veteran-focused sourcing effort. A tag, a folder, or even a naming rule on the req title works. Now every application on that req is countable as part of the effort.

Then set the source value on candidates you brought in yourself. Lock the values to a short picklist so nobody types their own version. Free text turns into forty spellings of the same event and kills your reporting.

What source values should you use?

• VET-EVENT: a veteran hiring event or an on-base career fair.
• VET-DB: outreach from a veteran resume database.
• VET-ORG: a referral from a veteran service organization.
• VET-EMP: a referral from a veteran already on your team.
• VET-ALUM: outreach to a service academy or unit alumni group.

Read what that value actually says. It records the channel. It does not record whether that person served. Some people who come through a veteran channel will not be veterans, and that is fine. You are measuring your outreach, which is the thing you can defend.

How do you count and report with only channel data?

Channel data gets you further than most talent teams think. Here are the numbers you can pull from any ATS once the source field is clean and locked.

The math on that last one is worth its own sit-down. Our walkthrough on cost per veteran hire by channel shows how to build it.

How should you label the report?

Label the report honestly and the compliance risk drops. Write "applications from veteran sourcing channels" on the slide. That is a true statement about your outreach.

Be careful with the phrase "veteran applicants". Use it only when the count comes from self-ID data you may use that way. Those two lines look alike in a deck. Only one of them is a claim you can back up.

Once the channel numbers are steady, roll them into a standing view. Our guide on building a veteran sourcing scorecard gives you the layout and the review rhythm.

Where do you keep records the ATS will not hold?

Outbound sourcing already lives outside the ATS on most teams. Nothing wrong with that. A simple sheet does the job if you build it with the right columns.

Good columns are date contacted, channel, role targeted, req number, and outcome. Every one of those describes your activity. None of them describes a protected status.

Now the columns you leave out. No "veteran? Y/N". No notes about branch or discharge that you picked up from a conversation. No copy of a self-ID answer pulled out of the ATS and pasted into a shared file.

This guide is not legal advice. These rules are current as of August 2026. Rules shift, and state law can add its own layer. Have your counsel sign off on how you store what a candidate self-reports.

What do federal contractors still owe when the field is missing?

This section is scoped. It applies to federal contractors and subcontractors covered by VEVRAA, the law at 38 U.S.C. 4212. If your company holds no federal contract, these specific duties do not fall on you.

A missing ATS field does not cancel any of them. That is the part teams get wrong. The software gap is your problem to solve, not a reason the duty pauses.

Does the invitation still have to go out?

Covered contractors invite applicants to self-identify before an offer and again after an offer. The rule sits at 41 CFR 60-300.42. Each invitation has to state six things.

• The company is a federal contractor that must take affirmative action to employ and advance protected veterans.
• A summary of the relevant parts of the law and the company's affirmative action program.
• The request is being made on a voluntary basis.
• The answer will be kept confidential.
• Refusing to answer brings no adverse treatment.
• The answer will not be used in a manner inconsistent with the act.

If your ATS cannot host the form, the invitation can still reach people another way. Our post on the protected veteran self-identification invitation walks through the timing and the wording. Plenty of applicants will leave it blank, which is normal and allowed. We cover that in what to do when an applicant declines to self-identify.

Which annual numbers still have to exist?

41 CFR 60-300.44(k) lists computations a covered contractor documents each year and keeps for three years. There are five of them.

1. Applicants who self-identified as protected veterans, or who are otherwise known to be.
2. Total job openings and total jobs filled.
3. Total applicants for all jobs.
4. Protected veteran applicants hired.
5. Total applicants hired.

Read item one carefully. "Otherwise known" covers a person whose status you hold from a clear disclosure. It is not permission to guess from a resume or a gap in dates.

How do your channel tags become evidence?

The same section says a contractor reviews its outreach every year and judges whether it worked. Paragraph (f)(3) asks for documented criteria and a written conclusion on each effort. Your applicant and hire numbers from paragraph (k) must sit among those criteria. Use the current year and the two years before it. If the total effort was not effective, the contractor picks and runs different methods.

Paragraph (f)(4) is short and blunt. The contractor documents all activities it takes to meet this section. Those records are kept for three years.

That is why the source picklist earns its keep. Your channel tags are the record of what you tried. They also show what came of it. They do not replace the paragraph (k) numbers, which the annual outreach evaluation calls for. A year later, your channel record is a big part of your proof.

What should you ask your ATS admin for?

Bring a list, not a complaint. Most of these are config, not custom development, so the ask is smaller than it sounds.

Ask one more question before any of it. What does the platform already support that nobody turned on? Some systems ship a compliance module or a source field that nobody set up at go-live. Config usually beats a build request.

When is a custom veteran field worth the config request?

Sometimes the answer is yes. A dedicated field pays for itself when you are a covered contractor and you owe those annual computations. It also pays off when your platform can hide the field. Only the person who owns the reporting should see it.

Skip it when the source field already answers your leadership questions and you hold no federal contract. You would be adding a maintenance job for a number you never needed.

Watch the visibility question harder than the cost question. Self-identification answers stay confidential, and you may use them only in ways VEVRAA allows. The pre-offer invitation exists to measure your outreach, not to screen people. Say you put a veteran flag on the profile every interviewer reads. That data now sits right where hiring calls get made. Even with clean intent, it looks bad in a review.

How do you keep a veteran pipeline you can actually see?

Even with perfect tagging, your ATS only shows people who already applied. A pipeline you can see starts earlier than that. It starts where veterans are looking for work.

Saved searches do a lot of that lifting. Set them once and let matches come to you. No more running the same query every Monday. Our setup guide on veteran sourcing alerts covers the build.

Veteran-specific channels do the rest. Hiring events, service organizations, and resume databases where veterans choose to be found. The EEOC's own guide for employers on veterans and the ADA lists that approach. It names "online resume databases that connect job-seeking veterans with civilian employers" as one step. That guidance covers hiring veterans with disabilities.

That is the cleanest data situation you can be in. The veteran chose to be listed in that database. Your source tag records the channel, which is a fact about your outreach. Nothing about it depends on a field your ATS refuses to give you.

Best Military Resume runs that kind of pool. More than 1,000 new profiles are added every month. Over 65,000 resumes have been built on the platform to date. Employers only see candidates who have consented to employer search.

What to Do Next

Open your ATS today and look at one thing. Find the source field on an application and check whether it is free text. That single answer tells you how much cleanup is ahead.

Then work the short list.

1. Write five source values for your veteran channels and get them locked to a dropdown.
2. Add a tag on every requisition where your team runs veteran outreach.
3. Send your ATS admin the five config asks from above, in one message.
4. Pull a baseline report of applications and hires by source for last quarter.
5. If you hold a federal contract, confirm the self-ID invitation still fires before and after an offer.

None of that needs a new system. It needs a naming rule, one tag, and a report you run every month.

The other half is supply. Tagging a channel only helps if the channel has veterans in it. You need a pool of people who built a resume and asked to be found. Reach out about access to BMR's veteran talent pool. We will show you who is in there for your open roles.