OFCCP Job Posting Documentation Software: 3 Steps for 2027
The short answer
OFCCP job posting documentation and audit trail software is a set of tools that sends a federal contractor's openings to the state job channels the rules require, then keeps dated proof that each posting went live. Our recommendation: if you post only a few jobs a year, buy a per-listing posting service with reports and keep applicant records in the applicant tracking system (ATS) you already use. If you post often and need applicant records tied to each listing, request a quote for a suite with ATS integration.
TL;DR: Software can store the evidence, but it cannot make you compliant. Start from the posting duty that still applies, decide how long you must keep proof, then choose the product that stores that proof in a form you can export.
Key Takeaways
The posting duty most contractors still carry comes from VEVRAA, after the Executive Order 11246 regulations were rescinded.
Proof of each posting, such as a confirmation ID or a dated image, matters more than a vendor's dashboard.
Only one of the five vendors we reviewed publishes a per-listing price. The other four are quote-based.
The contractor stays responsible for compliance. JobTarget's own terms place that representation on the client.
A Zapier or in-house build can produce an audit log, but you own retries, duplicate prevention, access controls and escalation.
Choose by the file you would hand an auditor, not by how many job boards a vendor reaches.
What the rule change means for your audit file
EO 11246 rescission effective: October 26, 2026 according to Cooley (2026). That rescission removes the Executive Order 11246 regulations, which covered affirmative action plans and general recordkeeping, so a file built around those rules no longer maps to current obligations. The same summary says VEVRAA obligations "remain largely unchanged," and that is the obligation still driving job-posting software.
The Department of Labor's VEVRAA page says contractors "must list their employment openings with the appropriate state or local employment service delivery system" (ESDS), and that the listing must use a format the ESDS accepts, according to U.S. Department of Labor. That page's dates are inconsistent, so confirm the current text before you set your policy.
How long to keep the file
The retention periods below come from the VEVRAA recordkeeping section, 41 CFR 60-300.80. General retention period: two years according to Cornell Law School. The Cornell copy we read sets one year for smaller contractors and three years for certain records, and it names "job advertisements and postings" among the covered records.
| Record type | Retention period | Who it applies to |
|---|---|---|
| General VEVRAA records, including job advertisements and postings | two years | Most contractors |
| Same records | one year | Contractors with fewer than 150 employees, or without a Government contract of at least $200,000 |
| Records under 60-300.44(f)(4), 60-300.44(k) and 60-300.45(c) | three years | All contractors |
| Posting proof stored by JobTarget | three years | Vendor policy, not a regulatory period |
Set your policy to the longest period that applies to each record, and confirm it with counsel. The vendor row is listed separately because a vendor's own schedule does not replace your duty.
Who this is for
Who this is for: a federal contractor that must list openings with state channels, has one person who will own the posting file, and wants proof an auditor can read without calling the vendor. It also fits a team that posts often enough that manual screenshots and a spreadsheet become error-prone.
Red flags: you expect the software to make you compliant; no one on your team owns the posting file; you need applicant-level records but plan to buy a posting-only product.
How we evaluated these tools
We weighed five products against the criteria below, using only public pages. We did not run trials or sit through sales calls. The weights reflect what an auditor asks for first: proof that a posting went live, then the channels it reached, then how long you can keep and export it. Price carries less weight because most vendors do not publish it.
| Criterion | Weight | What to check on the vendor's page |
|---|---|---|
| Proof of posting (confirmation ID, dated image or receipt) | 25% | Does each posting produce a proof item? |
| State job bank and ESDS coverage | 20% | Which channels, and are they named? |
| Retention and export | 20% | Stated retention period and export format |
| Applicant record linkage | 15% | ATS integration or an applicant log |
| Price transparency | 10% | Per-listing price, or quote-based |
| Setup effort | 10% | Integration method and what you must supply |
| Total | 100% |
The vendor pages do not publish comparable metrics, so the table ranks what to check, not the vendors themselves.
Feature matrix from public pages
| Vendor | State job bank or ESDS posting | Proof of posting | Report export | Applicant records | Price |
|---|---|---|---|---|---|
| DirectEmployers | Stated | Not stated | Stated (PDF or Excel) | Not stated | Published per listing |
| Mitratech | Stated (all ESDS locations) | Stated (confirmation IDs, PDF snapshots) | Stated | Stated (ATS) | Quote-based |
| Broadbean | Stated (state workforce agencies) | Stated (state confirmation receipts) | Stated (verification reports) | Partial (integrates with most ATS) | Quote-based |
| JobTarget | Stated (state job banks) | Stated (image proofs) | Stated (CSV and Excel) | Partial (ATS integrations) | Quote-based |
| HR Unlimited | Stated (required state job banks) | Stated (confirmation records) | Partial (report types not listed) | Stated (ATS tracks applicants) | Quote-based |
"Not stated" means the page we read does not describe the item. It does not mean the product lacks it, so ask the vendor before you rule anything out.
Pricing and cost
Single job listing: $300 per job according to DirectEmployers (2026). The same page lists $873 for three listings and $1,425 for five, each active for 30 days, according to DirectEmployers. The page targets contractors with a small number of listings and points larger buyers to its Professional and Enterprise tiers, which show no price.
| Vendor | Plan | Published price | Notes |
|---|---|---|---|
| DirectEmployers | Single job listing | $300 per job | Active 30 days |
| DirectEmployers | Three-listing pack | $873 total | Active 30 days each |
| DirectEmployers | Five-listing pack | $1,425 total | Active 30 days each |
| DirectEmployers | Professional and Enterprise | Quote-based | Page directs buyers to a demo request |
| Mitratech | Circa | Quote-based | No price on the page |
| Broadbean | OFCCP product | Quote-based | Demo request only |
| JobTarget | Compliance Suite | Quote-based | Demo request only |
| HR Unlimited | Talent Management and Compliance Tools | Quote-based | Contact form only |
Pricing checked November 14, 2026.
Illustrative case, not a customer: a contractor with 12 openings in a year, each needing a 30-day listing. Buying single listings at $300 each costs 12 × $300 = $3,600. Buying two five-listing packs at $1,425 each covers 10 listings for $2,850, and two single listings cover the other two for $600, for a total of $3,450, which is $150 less. The DirectEmployers page does not say whether packs expire, so the math assumes they can be used across the year, and the page points larger buyers to quote-based tiers, so ask before buying packs at that volume. If you run the log in Zapier, each run record from the /v2/zap-runs endpoint includes zap_id and status, and the default query returns only the last 30 days unless you pass from_date, according to Zapier. An export job therefore has to run before that window closes.
Vendor profiles
Each profile separates what the vendor's page says from our read. Where a vendor publishes no price, we say so.
DirectEmployers, OFCCP Compliance Essentials
What the page says: a VEVRAA job listing and distribution service sold per job, with listings sent to state job banks in all states and U.S. territories, nightly electronic delivery, and OFCCP compliance reports as PDF or Excel. The page does not mention audit records.
Our read: best for a contractor with a few openings a year that wants a simple per-listing purchase and a report for the file. Disqualifier: if you need applicant records or an audit log, this product does not describe either.
Implementation: you buy per job, and you keep each state confirmation with its requisition yourself, because the page does not describe proof files.
Evidence: DirectEmployers OFCCP Compliance Essentials page.
Mitratech, Circa
What the page says: Circa posts to all 56 ESDS locations, according to Mitratech. It captures and retains "proof of postings," including ESDS confirmation IDs and PDF snapshots, and it includes applicant tracking. It can also handle ESDS account registration and management. Pricing is not published.
Our read: best when you want posting proof and an applicant log in one product. Limitation: the page does not claim an audit trail or activity log, so request one in writing before you buy. Quote-based.
Implementation: if the vendor manages your ESDS accounts, setup is lighter, but you depend on the vendor to hold those accounts. Get the account-transfer terms in writing.
Evidence: Mitratech Circa page.
Broadbean, OFCCP product
What the page says: postings go to state workforce agencies, with state-issued confirmation receipts as proof, plus eight diversity websites and more than 5,000 community-based organizations within 25 miles of each job, according to Broadbean. Daily job summaries flag failed postings. The page says its audit support is unlimited and free, and that the product integrates with most applicant tracking systems. Pricing is not published.
Our read: best for teams that must also document outreach, since the page centers outreach records and a partner database. Limitation: the page does not use the term audit trail, and the audit-support claim comes from the vendor, so put it in the contract. Quote-based.
Implementation: ask how the ATS integration handles applicant records, since the page names the integration but not the data flow.
Evidence: Broadbean OFCCP page.
JobTarget, Compliance Suite
What the page says: the suite includes CompliancePost for state job banks, Local Outreach, an Activities App and reporting. It lists 80+ ATS, payroll and HR integrations, and it says image proofs are stored for three years, according to JobTarget.
The user guide describes a Compliance Report, an Activities Report and a Proofs Report. The Compliance Report and Activities Report export to CSV, and the Proofs Report carries Received, Delivered, Verified and Deleted dates. JobTarget's term sheet places the compliance representation on the client and disclaims liability if the client is found non-compliant.
Our read: best for contractors who post often and want proof and reports tied to each posting. Limitations: no published price, and no described audit trail or change history. The Deleted dates mean you should copy proofs into your own store before the vendor's retention window ends.
Implementation: expect ATS integration work, and confirm who owns the job board accounts.
Evidence: JobTarget Compliance Suite page.
HR Unlimited, Talent Management and Compliance Tools
What the page says: the product pairs an applicant tracking system with VEVRAA and ESDS job posting, describes itself as built for federal contractors, and says it keeps required documentation for at least three years, according to HR Unlimited. The ATS tracks applicants and disposition reasons and collects voluntary self-identification data. The page lists no report types and no pricing.
Our read: best for a contractor that wants one system to hold applicant records and posting proof. Limitation: the page does not describe the proof format or an audit log, so request a sample confirmation record and a sample export before you buy. Quote-based.
Implementation: the page says the system integrates with your ATS or internal system. Ask what happens to your records if you leave.
Evidence: HR Unlimited VEVRAA/ESDS page.
Two names we checked and left out
Arcoro's homepage presents a construction-focused HR platform and does not mention OFCCP or federal-contractor compliance. A pricing page we tried to open returned not-found. JobAps describes itself as "Built Exclusively for Government Human Resources," and the page we read does not mention OFCCP, VEVRAA or federal-contractor compliance. Neither is in the scored set, and neither has a deep page that supports a claim about this use case.
Three steps to choose a tool
Define the file. List what an auditor would ask for: each requisition, the state channel used, the proof item and the retention period. Set retention from the rule text in the table above, not from a vendor default.
Check the proof, not the demo. Ask each vendor for a sample proof item and a sample export, and for its retention period in writing. Confirm that the proof shows the posting date, the channel and a confirmation ID.
Match cost to volume. For a few openings a year, buy per-listing postings and keep proof in your own folder. For frequent postings or applicant records tied to listings, request a quote for a suite and compare its exports against your file list.
Where the proof trail breaks
The usual failure is not the posting itself. It is the gap between posting and proof: a requisition opens, someone submits it, and the confirmation sits in an inbox. The two flows below describe how a configured design could close that gap. They describe a design, not a deployment.
US Tech Automations would configure a proposed flow that starts when a requisition in your ATS changes to open. The trigger reads the requisition ID, title, work location and open date through the ATS API or a scheduled export, so the first prerequisite is that your ATS exposes those fields. The action sends those fields to the posting provider you have already bought, using that provider's own submission path. The output is one row in a posting log holding the requisition ID, the submission time, the provider's confirmation ID and the path to the stored proof. A compliance owner reviews every requisition that has no confirmation within the window your counsel sets, and reviews every failed submission by hand before anything is resubmitted.
The second flow in the same design handles the proof file itself. When the provider's report shows a new proof, the workflow downloads the file, names it with the requisition ID and posting date, writes it to a document store your team controls, and adds the storage location to the log. The prerequisites are the provider's report export, write access to that store, and a retention rule taken from your counsel's policy rather than the vendor's. The human review point is simple: someone confirms that each stored file opens, that the dates match, and that nothing was deleted before the retention period ended. The workflow does not decide what counts as compliant.
Build it yourself or use Zapier, Make, or n8n
Building the log yourself is the fair alternative to buying a suite. Zapier's help center says errored runs appear in Zap history, that the Logs tab shows the HTTP status code, error message and API endpoint for an errored step, and that Autoreplay retries temporary failures automatically. It also warns that when a step failed because required information was missing, logs will not be available. Those are real audit features when they are configured. We did not verify Make or n8n for this article, but the same design questions apply to them.
You still have to design and own what those tools do not decide for you. That means observability across the whole chain, idempotency so that a retried submission does not create a second listing, escalation when a confirmation is missing, access controls on the proof store, and maintenance when a state's form or a provider's API changes.
A US Tech Automations design would produce the same log in a configured form, with the prerequisites and review points described above. Whether that costs less than a suite depends on your posting volume and on who will maintain it. When not to use US Tech Automations: skip a configured design if you post only a few jobs a year and a per-listing service with a published price covers your state listings and reports, because a second system adds something to audit. Skip it if your suite already captures proof, exports reports and holds applicant records, since the same proof would then sit in two places. And skip it if you need a system of record for applicant decisions; a workflow layer reads from that system and does not replace it.
Glossary
ESDS: the state or local employment service delivery system that receives VEVRAA job listings.
VEVRAA: the federal law that bars federal contractors from discriminating against protected veterans, and that sets the job-listing duty.
Section 503: the federal law that bars federal contractors from discriminating against people with disabilities.
Proof of posting: a dated image, state receipt or confirmation ID showing that a listing went live.
Audit trail: a record of who changed or deleted what, and when.
ATS: applicant tracking system, the system that holds applicant records and disposition reasons.
Idempotency: a design property that stops a retried submission from creating a duplicate listing.
Frequently asked questions
Does buying OFCCP job posting software make us compliant?
No. The software can store evidence, but the contractor remains responsible for compliance, and JobTarget's own terms place that representation on the client.
Can we post manually and skip the software?
Yes, if every listing goes to the state employment service in a format it accepts and you keep the confirmation with the requisition. The Department of Labor's page lists web forms, electronic submission, fax and mail as accepted formats, so the duty is to list, not to buy a product.
Which retention period should we set?
Set a three-year policy. It covers every period in the retention table above, and it matches the three-year proof storage that at least two vendors describe.
Should we buy a per-listing service or a suite?
Buy per listing if you post a few jobs a year and want a published price. Request a suite quote when you need applicant records and proof tied to frequent postings.
Does a workflow layer replace the posting vendor?
No. A workflow layer sits on top of a posting provider and reads that provider's reports. It does not hold your state account or replace the submissions the provider makes.
Conclusion
Start with the file an auditor would ask for, then choose the product that produces it in an exportable form. Keep applicant records in the ATS you already run, and keep a copy of every proof outside the vendor's system. If you want to see how a configured design would handle those steps, see how US Tech Automations configures this, and check each prerequisite against your own systems first.
About the Author

Helping businesses leverage automation for operational efficiency.