How to Build OFCCP Good-Faith-Effort Outreach Records
Hire veterans who are ready for the job
We turn real military records into clear, civilian resumes so your hiring team can see what each veteran actually did.
You track your veteran hiring benchmark. You send the self-identification invite. You file VETS-4212 on time. Then a compliance evaluation letter lands, and the scheduling letter asks for your outreach records. That is where most federal contractors freeze.
The rule the benchmark and the reports cover is the "who" and the "what." This article covers the part nobody writes about: the actual file an OFCCP reviewer pulls. The proof that you did the outreach you say you did.
I built Best Military Resume after my own federal transition, and I have spent the last two years working with companies on the hiring side. The pattern with audits is always the same. Contractors do real outreach. They just never write it down in a way a reviewer can read. This guide fixes that.
One note before we start. This is the practice, not legal advice. The dollar thresholds and retention rules move. Confirm the current numbers with OFCCP or your counsel before you act.
Key Takeaway
A reviewer does not score your intentions. They score your file. Good-faith effort is a recordkeeping discipline, not a one-time act. If it is not written down, it did not happen.
What are good-faith-effort outreach records?
VEVRAA asks covered federal contractors to do more than not discriminate. It asks you to take active steps to recruit and hire protected veterans. The legal term for those steps is "outreach and positive recruitment."
Good-faith-effort records are the paper trail behind those steps. They show what you did, who you reached, and whether it worked. The reviewer is not looking for a hiring quota. They are looking for evidence that you tried in a real, documented way.
The core outreach rule lives in 41 CFR 60-300.44(f). It asks contractors to do three things. Run outreach. Assess once a year whether the outreach worked. Keep the records of both.
This sits next to your other compliance work, but it is its own file. Your benchmark tells you the target. Your self-id invite tells you who applied. Your outreach file proves the effort that connects them. For the rule itself and who is covered, see our guide to VEVRAA compliance. This article stays on the evidence.
Who this applies to
Written affirmative action duties generally start at 50 or more employees and a single covered contract at or above the current threshold. The FAR Council raised that threshold to $200,000 effective October 1, 2025. Confirm your status before you assume you are covered.
Why does the file matter more than the effort?
OFCCP calls its audit a "compliance evaluation." It usually opens with a scheduling letter. That letter gives you a short window to submit your affirmative action program and supporting data. Your outreach records are part of that package.
The hard truth about that window is simple. You cannot create good outreach records after the letter arrives. The reviewer can see backdated work from across the room. The file has to already exist, built through the year, dated as it happened.
Think about how a reviewer reads. They are not in the room when you call a veteran service organization. They never see the job fair you worked. All they have is what you wrote down. A strong contractor with a thin file looks worse than an average contractor with a clean one.
From the hiring side of the desk, I have watched this play out. The effort was real. The record was a one-line note that said "did veteran outreach." That note proves nothing. It does not survive a second look. The fix is not more effort. It is better evidence of the effort you already make.
"Conducted veteran outreach in 2026. Posted jobs to veteran sites."
"March 12, 2026: posted 4 reqs to a veteran resume database and 1 base transition office. Contact: name, email. Result: 9 applicants, 2 interviews, 1 hire."
What should you document for each outreach effort?
Every outreach effort needs the same handful of facts. If you capture these at the moment you do the work, your file builds itself. If you try to remember them in December, you will guess, and guesses do not hold up.
Treat each effort like a small case file. The reviewer should be able to pick up any one entry and understand what happened without asking you a single question.
What to capture for every outreach effort
The date and the source
When you did it and which channel, org, or event it was.
The contact and the proof
A name, an email, a screenshot, or a confirmation. Something a third party could verify.
What you asked for
The reqs you shared, the resumes you searched, or the help you requested.
The result, in numbers
Applicants, interviews, hires, or "no response." Even a zero is data you need next year.
That last line matters more than it looks. A channel that produced nothing is not a failure in your file. It is the input to your annual review. You need the zero to prove you measured, and to justify changing course.
One channel you can document cleanly is a veteran candidate database. When you search a pool and pull resumes, the platform gives you a dated, exportable record. That is far easier to file than a hallway conversation at a job fair.
How do you organize the outreach evidence?
A pile of emails is not a file. The goal is a structure a reviewer can read in five minutes. Build one master log, then keep the backup proof behind it. The log is the index. The proof is the appendix.
Your master log is one row per effort, with the columns from the section above. Date, source, contact, ask, result. Sort it by date. A reviewer should be able to scan the year top to bottom and see a steady rhythm of activity, not a panic spike in the fourth quarter.
- •One dated row per outreach effort
- •Channel or organization name
- •Result counts and a link to the proof
- •Emails and confirmations
- •Screenshots of postings and searches
- •Event sign-in sheets and flyers
Name your files so they sort themselves. Put the date first, then the source. "2026-03-12-veteran-database-search" beats "outreach final v2." When a reviewer asks for one entry, you want to find it in seconds.
Keep the file where more than one person can reach it. Outreach records that live in one recruiter's inbox vanish when that recruiter leaves. A shared drive owned by your compliance function survives turnover. Audits often look back across years, so the file has to outlast the people.
How long do you have to keep the records?
Retention has two layers, and they are easy to mix up. Get the longer one right and you cover both.
General personnel and employment records fall under 41 CFR 60-300.80. The standard period is two years from the date the record was made. Smaller contractors get a shorter window. If you have fewer than 150 employees, or no single contract at or above $150,000, the minimum drops to one year.
Your outreach activity records are different. They have their own rule under 41 CFR 60-300.44(f)(4). That section asks you to document all of your outreach activities and keep them for three years. So your outreach file outlives your general personnel file. Build to the three-year standard and you are safe on both counts.
Do not delete on a complaint
If you get notice that a complaint or compliance evaluation has started, hold every relevant record until it is fully resolved. The normal retention clock stops. Purging on schedule during an open matter is a serious problem.
What is the annual outreach review, and why does it trip people up?
This is the step most contractors skip, and it is the one reviewers love to ask about. The rule does not just want you to do outreach. It wants you to grade it once a year.
Under 41 CFR 60-300.44(f)(3), you review your outreach efforts on an annual basis. You write down the criteria you used to judge each effort. Then you write your conclusion on whether each one worked. The review pulls data from the current year and the two years before it.
This is the part people miss. If you decide an effort did not work, you do not just note it and move on. You have to identify and try a different effort. The review is a loop, not a report card. Ineffective channel out, new channel in, measured again next year.
"We reviewed our outreach and it was effective." No criteria. No numbers. No change.
"We judged each channel by applicants and hires over three years. Channel X gave 0 hires, so we dropped it and added a veteran database for next year."
Write the criteria first, in plain language. Applicants per channel. Interviews per channel. Hires per channel. Then let the numbers say which efforts earned a spot for next year. That is what a defensible review looks like.
What gaps do reviewers find most often?
After two years on the hiring side and a lot of conversations with contractors, the same holes show up again and again. None of them are about a lack of effort. They are about the file.
1 No annual review on file
2 Activity with no results
3 A fourth-quarter spike
4 Records lost to turnover
5 No proof behind the claim
Notice that none of these gaps require new spending. Four of the five are pure discipline. You already do the work. You just have to leave a clean trail behind it.
Where does a veteran candidate pool fit in your records?
Outreach only counts if it reaches actual veterans. A documented channel that produces real applicants is worth more in your file than ten vague "posted to a board" lines. This is where a dedicated veteran candidate pool earns its place.
Best Military Resume runs a candidate side built for exactly this. There are over 1,000 new veteran profiles added every month, and more than 60,000 resumes built on the platform. When you search that pool and reach out, each action is dated and exportable. That is outreach you can prove.
It also feeds the part of the rule that trips people up. Because the platform tracks who you contacted and what came back, the result counts drop straight into your annual review. The channel that documents itself is the channel a reviewer trusts.
For other channels worth documenting, see how to use base transition offices, how transition programs work as a sourcing channel, and how a SkillBridge host pipeline doubles as outreach evidence.
"The contractors who pass clean are not the ones who tried hardest. They are the ones who wrote it down as it happened."
How do you build the file across a full year?
The whole thing comes together as a simple yearly loop. Set it up once and it runs in the background. This rhythm keeps a file audit-ready.
Set up the log once
Build the master log and a shared backup folder owned by compliance. Five columns: date, source, contact, ask, result.
Log each effort the day you do it
One row, plus the proof in the folder. Same day, every time. This is the habit that makes the rest easy.
Update result counts as they land
Applicants, interviews, hires. Tie each back to its source so you know which channel earned them.
Run the annual review
Once a year, grade each channel against your criteria. Write the conclusions. Drop what failed, add something new.
Hold the records to three years
Keep outreach activity records for three years. If a complaint or evaluation opens, stop the clock and hold everything.
Do this and the scheduling letter stops being a fire drill. The file already exists. You pull it, you submit it, you move on. That is the whole point of building it as you go.
Two of these steps lean on data you may already collect. Your benchmark tracking and your legal tracking of applicant veteran status feed the result counts. The self-identification invitation tells you who is in the pool. Your outreach file connects the effort to those numbers.
Build outreach you can actually prove
Good-faith effort is a file you hand the reviewer. It is not a speech you stand up and give. The contractors who breeze through a compliance evaluation are the ones who treated outreach like a logged, measured, year-round process.
Start with the channel that documents itself. Best Military Resume gives you a dated, exportable record of every veteran you reach, with over 1,000 new profiles added every month to search. That is outreach evidence you do not have to reconstruct in a panic.
If you want a veteran sourcing channel that builds your good-faith-effort file while it fills your reqs, reach out to access BMR's veteran talent pool. Document the effort once, and let it do double duty.
Frequently Asked Questions
QWhat records prove good-faith effort to an OFCCP reviewer?
QHow long must federal contractors keep veteran outreach records?
QWhat is the annual outreach effectiveness review?
QWhat does OFCCP call an audit?
QWhich companies have to keep these outreach records?
QCan a veteran candidate database count as documented outreach?
QWhat gap do reviewers find most often in outreach files?
About the Author
Brad Tachi is the CEO and founder of Best Military Resume and a 2025 Military Friendly Vetrepreneur of the Year award recipient for overseas excellence. A former U.S. Navy Diver with over 20 years of combined military, private sector, and federal government experience, Brad brings unparalleled expertise to help veterans and military service members successfully transition to rewarding civilian careers. Having personally navigated the military-to-civilian transition, Brad deeply understands the challenges veterans face and specializes in translating military experience into compelling resumes that capture the attention of civilian employers. Through Best Military Resume, Brad has helped thousands of service members land their dream jobs by providing expert resume writing, career coaching, and job search strategies tailored specifically for the veteran community.
Found this helpful? Share it: