What gets discussed far less is what a stale or fake requisition does to the numbers a recruiting team actually runs on. If a meaningful share of open requisitions are not genuinely active, every metric built on top of them, time to fill, time to hire, funnel conversion rate, cost per hire, is measuring a blend of real and fake activity with no way to separate the two.
Why This Is a Data Problem, Not Just a Trust Problem
Time to fill and time to hire both use "requisition opened" as their starting clock. A requisition that has been effectively dead for weeks, frozen budget, internal candidate already selected, forgotten after the hiring manager moved on, keeps that clock running anyway, which means every dashboard reporting these metrics is quietly averaging in postings that were never on a real path to a hire in the first place.
Funnel conversion rate suffers the same distortion from the other direction. A ghost job can show plenty of top of funnel activity, applications, even some early screens, before it stalls with zero real conversions, dragging down the conversion percentage for every genuinely active requisition it gets averaged against.
Cost per hire calculations get skewed too, since sourcing and screening spend against a ghost requisition gets attributed to a hire that will never happen, inflating the true cost of the hires that do close.
How to Audit Your Own Requisitions for This
Pull every requisition currently marked open and sort by days since last candidate stage change, not days since posting. A requisition with recent candidate movement is active by definition. One with zero stage changes in 30 or more days is either genuinely stalled or a ghost job, and it needs a human decision, not a default assumption that it is still hiring.
Cross reference open requisition count against actual approved headcount for the same period. A gap between the two, more open reqs than approved headcount can explain, is the clearest early signal that some requisitions are not being closed when they should be.
Set a mandatory review trigger, 45 to 60 days is a reasonable default, that forces a hiring manager to confirm a requisition is still active or close it. Without a forcing function, stale requisitions default to staying open indefinitely, since closing one requires someone to notice and act, while leaving it open requires nothing at all.
What This Means for Reporting Up
If leadership is reviewing a time to fill number, a conversion rate, or an open requisition count without this audit having been run recently, they are looking at a number that includes some amount of ghost job noise, and they likely do not know how much. Flagging that caveat explicitly, and running the audit above on a regular cadence, is a small operational habit with an outsized effect on whether hiring metrics actually reflect what is happening versus what the requisition list claims is happening.
This is the same discipline behind good quality of hire tracking generally: know precisely what a metric is actually measuring before using it to make a decision.
Final Thought
Ghost jobs are usually framed as a candidate experience problem, and they are one. They are also a data integrity problem for the recruiting team running them, one that quietly inflates or deflates every metric downstream of an open requisition count.
Auditing requisitions against real candidate activity, not just posting age, is the fix, and it is worth doing regardless of how the broader ghost job conversation resolves. For the fuller picture on why ghost jobs happen and what they cost employer brand, see our companion guide to ghost jobs in 2026.




