Ghost job posting compliance: build a provenance record now
New York's S8877 would turn every job ad into a written representation about whether the role is real. Most talent teams cannot yet prove, per posting, who approved it or when it goes stale.
Ghost job posting compliance has moved from reputation management to paperwork. On June 2, 2026, New York lawmakers passed S8877, a bill that would require larger employers and the platforms carrying their ads to say plainly whether a posting reflects a current vacancy, when they expect to fill it, or whether it exists only to build a pipeline. The practical problem for most talent acquisition teams is not disagreement with the premise. It is that they cannot currently produce, per posting, the evidence that would back up either answer.
Indeed Hiring Lab analysis of BLS JOLTS, July 2026 report.
| Value (Openings, YoY change) | Change vs. prior year |
|---|---|
| Retail Trade | 155000 Openings, YoY change |
| Manufacturing | 152000 Openings, YoY change |
| Leisure & Hospitality | -187000 Openings, YoY change |
What S8877 would actually require employers to say
According to coverage from the National Law Review and SHRM, S8877 reaches employers with 100 or more employees and extends to the job-posting platforms that host their ads. The core obligation is a notice attached to the posting identifying whether the position is a live vacancy and the timeframe in which the employer expects to fill it. Fisher Phillips attorney Amanda Blair has framed the bill as forcing a distinction most recruiting functions have kept informal: is this ad tied to an open role, or is it collecting resumes for something that may or may not be funded later?
That distinction is easy to state and hard to document. Pipeline-building postings are not inherently deceptive, and the bill does not ban them. What changes is that the designation becomes a public, dated representation an employer has to stand behind, and one a candidate or a regulator can later test against hiring records.
Exposure does not stop at the New York line. A Congressional Research Service In Focus on ghost job postings notes that deceptive job advertisements may implicate Section 5 of the FTC Act, which reaches unfair or deceptive practices generally. Employers that treat this as a single-state compliance project are reading the risk too narrowly.
A posting that was accurate in February can become a misrepresentation by August without anyone touching it.
Why the labor data makes phantom reqs easier to spot
The timing is not accidental. BLS released the August 2026 JOLTS report on Sept. 29, 2026, and Indeed Hiring Lab summarized it as "Little Change, Limited Dynamism," flagging that the vacancy yield - hires per job opening on a three-month moving average - has been falling. Openings stay posted. Hires do not follow at the same rate.
Earlier in the year the pattern was already visible: roughly 6.9 million openings in March 2026 against a 1.2% layoff rate, the flat-but-frozen configuration that lets stale requisitions quietly accumulate on career sites. Indeed Hiring Lab's analysis found new graduates and other labor market entrants absorbing the worst of the gap, applying into openings that convert to offers at steadily lower rates.
None of that proves any individual posting is fake. But it is the macro signal that candidates, journalists and legislators are now using as a proxy for phantom reqs, and it is why the disclosure argument gained traction so quickly. HR Executive has separately reported candidate ghosting at record highs, with research suggesting discouraged applicants often do not reapply. The employer brand cost arrives well before any legal one.
The posting provenance record: what to capture per req
The fix is unglamorous and mostly structural. Every live posting needs a provenance record that a recruiter, a comms lead or outside counsel could read in under a minute. At minimum: the requisition ID, funding status and the finance owner who confirmed it, the approval date and approver, the expected fill window, an explicit pipeline-only flag, a syndication map of every board and aggregator carrying the ad, and a scheduled takedown or refresh date.
Two of those fields do most of the work. Funding status separates a real opening from an aspirational one, and it is the field most often assumed rather than verified. The refresh date converts a one-time attestation into something durable, because a posting that was accurate in February can become a misrepresentation by August without anyone touching it.
Pair the record with a standing stale-posting sweep on a fixed cadence, ideally monthly, owned by TA operations rather than individual recruiters. The sweep should produce an exception list, not a dashboard: every posting past its expected fill window, every req with unconfirmed funding, every ad still live after the role closed.
Syndication is the blind spot most teams will miss
Because S8877 reaches platforms as well as employers, the copies matter as much as the original. A posting taken down from the career site but still circulating through aggregators, staffing partners and scraped feeds is still a representation to candidates, and the employer's name is on it. Most talent teams have no authoritative list of where a given ad was distributed, let alone a reliable takedown path.
Start by mapping distribution at the point of posting rather than reconstructing it after a complaint. Document which boards receive the feed, which partners repost manually, and who is accountable for removal on each channel. Where contracts with job boards and staffing vendors are up for renewal, add takedown service levels and accuracy obligations explicitly.
Recruiter metrics may be rewarding the regulated behavior
The second-order problem sits inside the scorecard. Where recruiting teams are measured on applicant volume, pipeline depth or time-to-slate against an evergreen posting, the system quietly rewards keeping ads live past the point of usefulness. A disclosure law does not change that incentive. It just makes the output legally reviewable.
Before the rule lands, run the metric review alongside the posting audit. Shift weight toward offer acceptance, quality of hire and posting accuracy rates, and give recruiters an unpenalized path to flag a req as pipeline-only or close it outright. The compliance work fails if the measurement system keeps pulling the other way.
