Ghost-Job Laws in 2026: What Startups Need to Record

A ghost job is a public posting without a current, clearly disclosed hiring commitment. Ontario now requires covered employers to say whether a vacancy exists and to update interviewed applicants within 45 days. Comparable U.S. state bills remain pending or await further action; none was enacted as of August 28, 2026. Startups should already track intent, timing, ownership, expiry, closure, and candidate communication.

This is an operational guide, not legal advice. Definitions, employer thresholds, exceptions, and recordkeeping duties vary by jurisdiction, so confirm which rules apply to your company and roles with employment counsel.

What is a ghost job, and why is the “one in five” claim not proven?

There is no single legal definition of a ghost job. The useful employer-side definition is a posting without a current, clearly disclosed hiring commitment. That description focuses on what a candidate can reasonably understand, rather than trying to prove a recruiter’s private motive after the fact.

The Congressional Research Service describes ghost jobs broadly as online postings for positions that do not exist or that an employer does not plan to fill immediately. That umbrella contains four different situations:

1. Current vacancy: Approved work and budget exist, and the employer is actively trying to hire.
2. Anticipated or pipeline role: No current vacancy exists, but the employer is collecting interest for expected or recurring work.
3. Stale posting: A genuine opening was filled, frozen, cancelled, or left active on a copied channel.
4. Fraudulent posting: Someone posts to deceive candidates, steal data, or impersonate an employer.

Pipeline recruiting is not automatically dishonest. A clearly labeled talent-pipeline page lets candidates make an informed choice about submitting their details. The problem is ambiguity: a specific, urgent-looking vacancy used for indefinite resume collection.

You should also reject the viral claim that one in five job postings is fake. No official population-level statistic establishes that number. CRS says official statistics do not exist and notes that vendor studies use unevenly disclosed methods. Cohort selection, observation windows, cancellation rules, and the definition of hiring activity can all change the result.

Nor does closing a role without a hire prove it was fake. In an analysis of more than 22,000 jobs, Ashby found that some roles ended without a hire even after candidates entered active interviews. Budgets change. A finalist declines. The team reorganizes. The honest question is whether the employer recorded and communicated its intent and any later changes.

Be careful with labor-market comparisons too. The Bureau of Labor Statistics definition for a JOLTS job opening requires a specific available position, a possible start within 30 days, and active external recruiting. A count of online ads is not the same dataset, so you cannot infer that stale ads explain the gap between official openings and hires.

Which ghost-job rules are actually law in 2026?

Ontario has an enacted vacancy-disclosure regime in force. The U.S. measures discussed here have not become law as of August 28, 2026. That is the clear answer, despite headlines that make the landscape sound more settled.

Ontario’s requirements for publicly advertised jobs took effect on January 1, 2026. New York’s legislature passed a bill through both chambers, but the official record did not show enactment by the check date. New Jersey, Kentucky, and Pennsylvania had pending bills at different legislative stages.

At the U.S. federal level, there is no specific ghost-job statute or rule. CRS explains that deceptive ads may raise questions under Section 5 of the FTC Act, but proving deceptive intent or legally cognizable unfairness can be difficult. The FTC’s Joint Labor Task Force announcement named deceptive job advertising, including misleading pay or benefits, as a priority. It did not create a ghost-job rule.

Federal attention is still increasing. In June 2026, Senator Ruben Gallego asked BLS, FTC, and DOL to examine prevalence, data quality, platform practices, and possible agency action. Those letters are requests from a senator, not agency findings or employer requirements.

This distinction matters. A sensible internal control can prepare you for several possible laws, but you should not present a proposed bill to candidates or managers as a current legal duty. Keep a dated jurisdiction register and recheck official sources before publishing guidance.

How does Ontario’s vacancy-disclosure rule work?

Ontario now requires covered employers to disclose whether a publicly advertised job is for an existing vacancy, update interviewed candidates, and preserve records. It is the clearest current example of hiring intent becoming a candidate-facing fact backed by evidence.

The Ontario government guide says the rules generally cover employers with at least 25 employees on the day a job is posted. The count includes people such as part-time and casual employees, rather than full-time equivalents. Scope and exceptions still matter, so do not treat headcount as the only applicability test.

For public advertisements of specific Ontario positions, covered employers generally must:

• State whether the posting is for an existing vacancy.
• Include expected compensation or a range, subject to prescribed exceptions and range limits.
• Disclose the use of AI to screen, assess, or select applicants.
• Avoid requiring Canadian work experience.
• Tell an applicant who was interviewed whether a hiring decision has been made within 45 days after the interview, or the last interview in a series.

The regulation and Employment Standards Act also make record retention part of the control. Employers must generally keep the public posting, its associated application form, and every revised version for three years after public access ends. They must keep required interview communications for three years after they are provided.

That version requirement changes the design problem. Editing a live page in place is not enough when the old wording disappears. You need to know what candidates saw, when they saw it, who approved each change, and when public access ended.

Ontario does not force an employer to fill every disclosed vacancy. A legitimate role can still be paused or cancelled. The rule instead makes the initial statement and later process visible and retainable. That is a more practical standard than pretending hiring plans never change.

What has New York passed, and what are other states considering?

The U.S. proposals share one direction: make vacancy status and timing explicit, then require stale postings to come down. Their details differ, and none of the four measures below was enacted as of August 28, 2026.

The New York bill record is especially easy to misstate. Passing both chambers is consequential, but it is not enactment. Its three-way model is useful for process design: fill by a date, fill no sooner than a date, or collect resumes with no current vacancy. Treat it as a proposed operating pattern, not today’s legal requirement.

The current New Jersey Senate text also matters because older summaries can contain interview-notification language that the 2026 Senate amendments removed. Kentucky’s official bill record shows only early action. Pennsylvania’s official status page shows a much broader proposal, but still no enacted duty.

Official interest extends beyond legislation. The Texas Attorney General opened an investigation into LinkedIn over alleged fake or misleading opportunities in July 2026. An investigation is not a finding that LinkedIn violated the law. It does show that posting accuracy is moving from candidate frustration to official scrutiny.

What six fields should every public requisition record?

Every public requisition should carry a six-field hiring commitment: vacancy class, intended-fill date, named owner, review or expiry date, channel-closure plan, and candidate-communication deadline. These controls make honest changes manageable and future legal updates easier to implement.

Make the vacancy class visible

Do not bury the most important fact in an internal requisition note. Say “We are hiring for one approved position,” “We expect this role to open in Q4,” or “This is an ongoing talent community, not a current vacancy.” Give candidates enough detail to decide whether applying is worth their time.

Put time on the commitment

An intended-fill date is not a promise that someone will start that day. It is a management checkpoint. Pair it with an expected start window, review date, and maximum public lifetime. If the date changes, preserve the old version and publish the new expectation instead of silently refreshing the posting timestamp.

Give the requisition an accountable owner

One named hiring manager should own the truth of the posting. A backup matters because leave, reorganization, and founder travel are predictable. Your job-posting workflow should make ownership explicit before a role can move from draft to public.

Define the exit before going live

Record how you will close every distribution channel. Include your careers page, partner boards, XML feeds, paid placements, recruiter copies, and manually reposted ads. The source-of-truth role can close instantly while an untracked copy collects applications for weeks.

Finally, define who must hear from you. Applicants who have spent hours interviewing deserve a different service level from someone who just joined a disclosed talent community. Your policy can exceed legal minimums, but it should never fall below a rule that applies to the role.

What should you do when a genuine role is paused or cancelled?

A changed plan does not turn a genuine vacancy into a ghost job. The failure begins when the employer knows its commitment changed but leaves the old representation public and candidates uninformed.

Use a simple change protocol:

1. Record the reason and time. Note whether the trigger was budget, reorganization, a filled role, changed scope, or a temporary freeze.
2. Change the public state. Pause if there is a credible near-term review date. Close if there is no active path to hiring.
3. Preserve the prior version. Save the posting and application form that were publicly available before the change.
4. Stop new applications where appropriate. A paused public page should not look like an actively reviewed vacancy.
5. Tell active candidates. State what changed, whether their application remains under consideration, and when they should expect another update.
6. Review downstream copies. Confirm that external destinations reflect the new state.

Do not cosmetically repost a frozen role to make it look fresh. If leadership still wants pipeline applications, create a clearly labeled anticipated-role or talent-community posting and state the expected review window. Candidates then get accurate information, while the company can still collect legitimate interest.

Your internal record should also separate intent from outcome. A role that reached interviews and then lost funding was a real search with a cancelled outcome. A role advertised as immediate hiring while the company only wanted market data had a different intent from the start. Treating both as “no hire” destroys the evidence you need to explain what happened.

How do you close every channel and communicate with candidates?

Closure is complete only when the source posting, supported distribution channels, manual copies, and active candidate conversations all reflect the decision. Queueing a deactivation is one step, not proof that an external board removed the ad.

Maintain a channel register for each requisition. For every destination, record the external ID or URL, publication time, responsible owner, takedown request time, and verified removal time. The Public Jobs API can keep an owned integration tied to the source lifecycle. Named integrations, such as Just Join IT and RocketJobs, still need separate verification because you do not control external processing.

Candidate communication should use event-based deadlines, not a vague promise to “keep people posted.” Define updates after application review, interviews, pauses, material timeline changes, and closure. Keep the message, recipient, sender, direction, and delivery time.

Apply the same discipline to rejections. Managing your pipeline should end in a recorded outcome, not an abandoned stage. Anti-stall reminders can surface active candidates who have not received a delivered candidate-facing message within your chosen threshold. A reminder helps enforce your policy, but it does not establish that the posting itself was truthful.

What does Kit support today, and what still requires a manual process?

Kit supports several execution controls for truthful hiring, but it is not a ghost-job compliance system. You still need a manual requisition record and legal review for vacancy classification, jurisdiction-specific language, expiry, version retention, and external verification.

What Kit supports today:

• Lifecycle states: Job postings move through draft, published, paused, and closed states. Publishing and closure have timestamps, and only published roles accept applications.
• Named owners: A posting has hiring managers, and Kit protects against removing or demoting the sole hiring manager without a replacement.
• Candidate correspondence: Applications retain chronological email messages. Rejections record operational details including the candidate message, scheduling, and sent time.
• Anti-stall reminders: Configurable reminders identify active submitted candidates who have gone without delivered candidate-facing contact on published or paused roles.
• Scoped distribution: Lifecycle actions can propagate to supported push integrations and pull feeds. Coverage is specific, and external deactivation is best effort rather than an immediate universal guarantee.

What Kit does not yet provide:

• A dedicated current-vacancy, anticipated-role, or continuous-hiring field.
• An intended-fill date or target-start field.
• Scheduled expiry, automatic stale-posting closure, or a separate expired state.
• A complete, attributed, immutable ledger of every posting state and version.
• A built-in three-year preservation guarantee for every posting version and statutory message.
• Jurisdiction-specific logic that makes a posting compliant with Ontario or any U.S. proposal.
• Proof that every external board removed a posting after deactivation was requested.

That boundary is useful. Use Kit for the lifecycle, owners, messages, reminders, and supported distribution it already handles. Keep the six-field commitment and retention evidence in a controlled requisition record until your system models the missing controls directly.

Ghost-job laws are turning hiring intent into something employers may have to state, revisit, and prove. You need not wait for every U.S. bill to settle. Declare the vacancy honestly, give it a date and owner, review it before it goes stale, close every copy, tell candidates what changed, and retain the evidence. If a law applies, counsel can map that clean process to its exact terms. If none applies, candidates still get a hiring process worthy of their time.