State job bank posting is a recurring OFCCP compliance finding, and one of the most preventable. Federal contractors holding a federal contract of $200,000 or more are required under VEVRAA to list virtually all open positions with their state employment service delivery system. That obligation sounds straightforward. In practice, it has enough moving parts that even contractors with solid compliance programs end up with gaps. This post covers what the requirement actually involves, which jobs need to be posted and where, and what it takes to stay clean in an audit.
What Is the ESDS?
The ESDS (State Employment Service Delivery System) is the network of state workforce agency job banks that federal contractors are required to use when listing open positions. Each state operates its own system. There is no single national platform. When a federal contractor posts a job to "the state job bank," they're posting to a specific state's workforce agency website: a system maintained by that state's labor department and used by job seekers in that state.
In most states, the ESDS is the state's American Job Center network or its associated job board (often called something like "WorkInTexas," "CalJOBS," or "PA CareerLink"). The names and interfaces vary, but the underlying obligation is the same: jobs must be listed with the workforce agency in the state where work will be performed or where candidates will be recruited.
Which Federal Contractors Have to Post to State Job Banks?
The state job bank posting obligation is a VEVRAA requirement. It applies to federal contractors with a contract of $200,000 or more.
The obligation applies at the contract level, not just to contractors who also have written Affirmative Action Programs. If your organization meets the dollar threshold, virtually all of your open positions need to go to the state ESDS, even if you don't have enough employees to require a written AAP.
Subcontractors are covered as well. If your organization performs work under a federal contract, even indirectly, the threshold test applies to your contracts too.
Which Jobs Require State Job Bank Posting?
Virtually all open positions must be listed with the appropriate state ESDS. The requirement isn't limited to certain job families, salary ranges, or locations. Three categories are exempt:
-
Executive and senior management positions: high-level leadership roles, not every salaried position
-
Positions filled from within: roles filled through internal transfer or promotion with no external recruiting
-
Positions lasting three days or fewer: short-duration temporary roles that, by their nature, will only exist for three days or less
Claiming an exemption incorrectly is one of the more common audit issues. When in doubt, post it.
Which state ESDS to use depends on where the work will be performed and where candidates will be recruited from. For a job in a single location, that's straightforward. For jobs that recruit across multiple states, post to the ESDS in each relevant state.
Remote jobs require a judgment call. If the role is tied to a specific territory or reporting location, post to the ESDS in that location. If the role is genuinely remote with no geographic restriction (the employee could work anywhere in the U.S.), you can post to any state where you expect to find qualified applicants. The practical resolution most contractors use: post to the ESDS in the state where the company has a physical location.
What Does a Compliant State Job Bank Posting Require?
Getting a job to the ESDS is the first step. A compliant posting has a few additional requirements.
The posting must include the required EEO/AA tagline. Every external posting, including the one on the state job bank, must include language stating the organization is an equal opportunity employer and takes affirmative action for protected veterans and persons with disabilities.
The posting should go up when recruiting begins. VEVRAA requires that job openings be listed with the ESDS at the same time the contractor begins recruiting through any other channel. Posting to the state job bank after you've already started advertising elsewhere creates a timing gap that can surface in an audit.
The posting must actually go live. Submitting a job to the state job bank isn't the same as a compliant posting. If the submission fails, times out, or gets rejected by the platform without your knowledge, the job was never listed. You may have no record of that. What auditors look for isn't a record that you submitted a job. It's proof the posting went live: a screenshot, timestamp, or image confirmation from the platform showing the job was published.
For a full breakdown of what records to keep and for how long, see Federal Contractor Job Posting Requirements: A Complete Checklist.
Where Federal Contractors Get State Job Bank Posting Wrong
OFCCP audit findings on state job bank posting cluster around the same failures year after year.
Jobs never posted. At low requisition volume, it's usually an oversight. At scale, it's almost always a process problem. There's no systematic trigger to send each new job to the ESDS, so postings happen when someone remembers to do it.
Wrong state ESDS. Contractors who recruit across multiple states sometimes post only to the ESDS where the company is headquartered, regardless of where the role is based. If the job is in a different state, the posting needs to go to that state's system.
Exemptions applied too broadly. "Senior manager" doesn't cover every director-level role. "Filled from within" doesn't apply if you also posted externally. When exemptions are applied loosely, the exposure adds up quickly across a large req volume.
Submission records, not proof of posting. A log showing that a job was submitted to the state job bank is not the same as proof it was published. Many contractors discover this distinction for the first time during an audit, when they're asked to produce documentation and find they have records of attempting to post but no confirmation that the posting went live.
At low volume, and if hiring in only one or two states, it's possible to manage state job bank posting manually and stay compliant. At scale — dozens or hundreds of openings moving at any given time, across multiple states — manual processes are where compliance gaps accumulate.
JobTarget Compliance Suite automates state job bank posting, posts directly to the client's state ESDS accounts, and captures image-based proof that each posting went live. Proofs are stored for three years, so the documentation is there when a scheduling letter shows up. It runs inside your existing hiring workflow so posting happens when you open the req, not when someone remembers it's overdue. If you'd like to see how it works, request a demo.
Frequently Asked Questions About State Job Bank Posting
ESDS stands for State Employment Service Delivery System: the network of state workforce agency job banks that federal contractors are required to use when listing open positions. Each state has its own system. There is no centralized national platform. Federal contractors must post to the ESDS in the state(s) where they're recruiting for a given role.
Post to the ESDS in the state where the work will be performed and where candidates will be recruited from. For roles recruiting across multiple states, post to each relevant state's system. For roles with a fixed reporting location but flexible work arrangement, post to the ESDS where the location is.
Three categories are exempt: executive and senior management positions, positions filled from within (no external recruiting), and positions lasting three days or fewer (short-duration temporary roles, not positions that happen to get filled quickly). Claiming an exemption incorrectly is a common audit finding. If a role doesn't clearly fit one of these categories, post it.
Job posting records must be retained for a minimum of two years. Contractors with 150 or more employees or $150 million or more in federal contracts must retain records for three years. That retention period applies to the posting records and any proof of posting.
