What Are Positions Open 90+ Days?
Positions Open 90+ Days is the count of job requisitions that are still open and have been open for more than 90 days as of a specific date. You will also see it labeled Open 90+ Days or Opened 90+ Days. All three point to the same thing: the roles in your hiring backlog that have gone stale.
Think of it as a snapshot, not an average. On any reporting date, you freeze your list of open reqs, measure how old each one is, and count the ones past the 90-day line. That count is the aged tail of your open-requisition backlog.
It is easy to confuse this metric with its neighbors, so here is how it sits next to them. Opened positions counts new requisitions created during a period, which measures hiring demand rather than backlog. Current openings counts every open req you have right now, with no age filter at all. Average days open reports the mean age across your open reqs, while this metric isolates the oldest slice of that same distribution. And time to fill averages the cycle time of requisitions that already closed, which structurally leaves out the roles this metric exists to catch.
That last distinction is the whole point. Time to fill can only measure a req that reached a hire, so the roles that never reach one, the ones that sit for four, six, or ten months, are invisible to it. A dashboard can show a clean 40-day average while a dozen roles quietly rot in the background. Positions Open 90+ Days drags those roles into the light.
Aging reqs are not new. What changed is the cost of ignoring them. Frontline, clinical, and skilled-trade roles are harder to fill than they were five years ago, M&A spreads requisition data across mismatched systems where old roles hide, and finance teams and private equity sponsors now ask harder questions about staffing cost. An open seat is no longer a neutral placeholder. It is a recruiting-efficiency and workforce-risk metric that sits at the seam between talent acquisition and finance, because every aged req is both a process signal and a running cost.
The Positions Open 90+ Days Formula
Positions Open 90+ Days = the number of open requisitions where the days between the opened date and the reporting date are greater than 90.
Here is how to run it, step by step.
- Pick your reporting date. This is the "as of" snapshot, usually a month-end or quarter-end.
- Pull every requisition in an open or active status on that date. Leave out anything filled, closed, or cancelled.
- For each open req, measure its age. That is the number of days between its opened date and the reporting date.
- Count the reqs whose age is greater than 90 days. That total is your Positions Open 90+ Days.
Define your terms before you run it:
- Open requisition: a req in an active, approved status that has not been filled, closed, or cancelled.
- Opened date: the day the req entered that open status. Pick one definition, created, approved, or posted, and hold it steady across every system.
- Reporting date: the snapshot date you are measuring against.
A few variations are worth knowing. Some teams track the same idea at other thresholds, the aged 60+ report being the most common companion, along with 120 and 180 day cuts for roles that run long by nature. Ninety days is the usual escalation trigger because it is roughly the point by which most non-executive roles should have closed. Standard aging reports break the backlog into buckets at 15, 30, 60, and 90 days so you can see the shape of it.
A raw count is hard to compare across teams, so many groups also express it as an aging requisition rate: Positions Open 90+ Days divided by total open reqs, times 100. The count tells you the size of the problem. The rate tells you whether it is getting better or worse.
Worked Example
Halstead Senior Living Group is a private-equity-backed operator with about 1,400 employees across 38 communities in the Southeast. It has grown through acquisition, folding in six smaller operators over the past year.
At quarter-end on June 30, Halstead has 74 open requisitions. Time to fill on the reqs that closed last quarter came in at 39 days, and the VP of Talent Acquisition has been reporting that number to the executive team. It looks fine. Meanwhile the COO keeps flagging that three communities cannot staff their night shifts, and a recently acquired community has had a Director of Nursing seat empty since February.
Run the metric. Count the open reqs where days open exceed 90 as of June 30, and the answer is 19. So 19 of 74 open reqs, an aging requisition rate of 26%, have been open more than 90 days. None of them appear in the 39-day time to fill, because none of them have closed.
Now segment the 19 to turn a number into a diagnosis.
By site origin: 11 of the 19 sit at the six communities Halstead acquired in the past year. Only 8 sit at legacy communities.
By role: the single oldest is a Director of Nursing open for 138 days. Two maintenance technician reqs have passed 110 days. The remaining sixteen are frontline clinical roles, mostly night-shift LPN and caregiver lines.
Here is what that means. The Director of Nursing seat is covered by an interim at roughly $1,100 a day. Across 138 days, that is about $152,000 for one open line, before you count the census and survey risk of running a community without a permanent nursing director. The acquired-site concentration says the problem is not sourcing volume. It is pay bands that were never re-leveled to local market after the deals closed, plus a broken hand-off where acquired-site hiring managers were never trained on the new applicant tracking system. Posting the roles harder will not move them. Re-banding the pay and assigning a dedicated recruiter will. The night-shift cluster points to shift-differential pay, not pipeline. And the two maintenance reqs had drifted in scope, so they should be refreshed or cancelled rather than left to age.
The VP of TA walked into the operating partner review with one line that changed the conversation: nineteen roles, a quarter of the open book, have been open more than 90 days, they are concentrated at six acquired sites, and one nursing seat has cost about $152,000 in agency coverage this year. A 39-day time to fill starts a different, much less useful conversation. This one an operating partner can fund a fix for.
What Data Do You Need to Calculate Positions Open 90+ Days?
The math is simple. The data hygiene is where it lives or dies. You need three fields, and each carries a trap.
- Requisition status. You need a clean open-versus-closed flag as of the reporting date. Cancelled, on-hold, and frozen reqs that were never properly closed in the applicant tracking system get counted as open and inflate the number. The metric is only as honest as your statuses.
- Opened date. You need one consistent definition of when the clock started. Reqs migrated from a prior system during an acquisition often carry the migration date instead of the true opened date, which understates their real age.
- Reporting date. The snapshot date. Run it on the same cadence, usually month-end, so the trend is comparable.
Watch these edge cases, because they distort the count more than any calculation error will:
- Evergreen or pipeline reqs. High-volume frontline hiring often uses reqs that stay open by design. They will always breach 90 days. Tag and exclude them, or they will drown the signal you actually care about.
- Reopened reqs. Decide whether reopening a role resets the age clock. If it does, you will systematically hide your oldest, most painful roles.
- One req, many openings. A single req can represent five seats. Decide whether you count requisitions or openings, and stay consistent.
- Acquired entities. Post-deal, requisition data arrives with different status conventions and date logic. Reconcile it before you trust the number, or the acquired sites will look artificially clean or artificially broken.
Why HR Leaders Need to Track Positions Open 90+ Days
It exposes the backlog your time to fill average hides
Time to fill is a survivor's metric. It only includes reqs that made it to a hire, so the roles that never close are missing from it entirely. That is a blind spot big enough to hide a staffing crisis. Positions Open 90+ Days is the counterweight. Report the two together and you see both the reqs that went well and the reqs that went nowhere.
Every aged req carries a daily cost of vacancy
An open seat is not free. A common rule of thumb sets the daily cost of a vacancy at the role's annual salary divided by about 260 working days, so a $95,000 role runs roughly $365 a day in lost output before you add anything else. For frontline and clinical roles, the real number is often higher, because you are paying agency, traveler, or overtime premiums to cover the gap. Multiply that by a backlog of 19 aged reqs and the count stops being an HR statistic and starts being a finance one.
Stalled roles quietly increase turnover risk
When a role sits open for months, the work does not disappear. It lands on the people still there. Extended understaffing burns out the team covering the gap, and burnout drives the exact voluntary turnover that created more open reqs in the first place. Aging reqs are a leading signal for the next wave of attrition, not just a recruiting inconvenience.
The concentration tells you where your process breaks
A high count in the aggregate tells you there is a problem. The segmentation tells you what it is. When aging clusters around one hiring manager, one location, one recruiter, or one role family, the cause is usually specific: pay that lags the market, a manager who will not commit, an approval stuck in a queue, or a job profile that asks for more than the role pays. You cannot fix "we have too many old reqs." You can fix "three managers account for two-thirds of them."
It gives finance and the board a number they can act on
"We have 60 open roles" is noise. It does not say whether hiring is healthy. "22 of our 60 open roles have been open more than 90 days, and they are concentrated in two business units" is a story an executive team or a private equity sponsor can respond to. This metric translates recruiting activity into the language of risk and cost, which is the language leadership already speaks.
Benchmarks and Interpretation
There is no universal "good" number for the raw count, because it scales with your total openings and your hiring volume. A backlog of 15 aged reqs is a rounding error at a company with 600 open roles and a five-alarm fire at one with 40. Convert the count to an aging requisition rate, divide by total open reqs, and track that instead.
Interpret the threshold by role, not by a single line. Industry hiring data is clear that role level changes what "too long" means. Most professional roles should close inside 60 to 90 days. But nearly 40% of senior-level positions take more than 90 days to fill, and executive searches routinely pass 120. So a frontline hourly req sitting at 90 days is an emergency, while a VP search at 90 days is normal. Set role-specific age thresholds, for example 45 to 60 days for hourly roles, 90 for professional roles, and 120 or more for executives, rather than applying one blanket number that cries wolf on your hardest searches and stays silent on your easiest ones.
Watch the trend and the concentration more than the absolute number. A rising aging rate over three quarters is a clearer signal than any single reading. And your own history is a better benchmark than anyone else's average, because your role mix, your markets, and your pay position are specific to you. External figures set rough expectations. Your internal trend is what you manage against.
Common Mistakes
Reading the raw count with no denominator. Nineteen aged reqs means one thing at a 60-req company and something else entirely at a 600-req one. Convert to an aging rate and follow the trend, or the number is just trivia.
Letting dirty statuses inflate it. Cancelled and on-hold reqs that were never closed in the system pad the count. The first time someone spot-checks a padded number, you lose the credibility the metric was supposed to build.
Resetting the age clock on a repost. Reposting a stale role does not make it younger. If your system restarts the counter every time, you will systematically understate your oldest and most damaging roles.
Judging every role against the same 90 days. A frontline hourly req at 90 days is a problem. An executive search at 90 days is a Tuesday. One threshold across all role levels produces false alarms and false comfort at the same time.
Watching only time to fill. A strong average on closed reqs can sit right next to a backlog full of roles that never close. If time to fill is the only speed metric you report, you are grading yourself on the reqs that already went well.
Reacting to the total without segmenting. The headline number says there is a problem. Only the cut by recruiter, hiring manager, location, and role says what to do about it. Skip the segmentation and you are treating a symptom you have not diagnosed.
Never forcing a decision. A req open 200 days is a decision no one has made. Aging data earns its keep only when it triggers an action: refresh the role, fix the pay, escalate the approval, or close it.
Related Metrics
- Average Days Open. The mean age across all your open reqs, where Positions Open 90+ Days is the aged tail of the same distribution.
- Current Openings. The total number of open reqs right now, and the denominator you divide by to get your aging requisition rate.
- Time to Fill. The average cycle time of reqs that closed, which is exactly why it misses the roles this metric is built to catch.
- Opened Positions. New requisitions created during a period, the inflow that feeds the backlog.
- Filled Positions. The reqs that closed with a hire, the mirror image of the ones still aging.
- Offer Acceptance Rate. A low rate sends roles back to the top of the funnel, where they start aging all over again.
- Cost of Turnover. Turnover creates the backfill reqs that later show up in your 90-day count, linking attrition directly to your open-req load.