Recruitment management system
- Time to hire, days end to end
- 31
- The same in weeks
- 4.4
- Days before an offer is even made
- 26
- Share of the wait that happens before an offer, percent
- 84
Every figure on this page is computed from the inputs entered, by the method stated below it. Reqnix publishes no salary data, no benchmark time to hire, no conversion rate you should expect and no employment law: the days, the costs, the scores and the weights are yours, and the defaults are a worked example to replace with your own.
The figures above start from a worked example (31). Change any input and the answer updates as you type.
Download the Recruitment management system worked example (CSV)
A recruitment management system is bought to make hiring faster, and the first thing worth knowing is where the time currently goes. This sheet takes four numbers you can get from your own last few hires: the days from application to first screen, screen to first interview, interview to offer, and offer to acceptance, plus the reqs you have open. It returns time to hire end to end, the same in weeks, the days that pass before an offer exists at all, the share of the wait that is upstream of the offer, how many hires one pipeline can turn over in a year at that pace, and how many weeks of pipeline your open reqs represent if they ran one at a time. On the worked example, 6 plus 9 plus 11 plus 5 is 31 days, and 26 of them, 84%, happen before anyone makes an offer. Desks that feel slow usually blame the offer stage, and the arithmetic almost always disagrees.
The offer is rarely the problem
Five of the 31 days on the worked example are between offer and acceptance. Shaving that stage to nothing saves 16% of the wait; halving the screening delay saves more, and costs nothing but a calendar habit.
Days, not averages of averages
Work the stages from your own recent hires rather than from a remembered figure. The point of splitting the wait four ways is that one stage is usually much worse than the others, and a single average hides exactly that.
What your open reqs actually represent
Eight reqs at 31 days each is 35 weeks of pipeline if they ran one at a time. They do not, of course, but the figure is the honest answer to whether one person can carry that list.
Reqnix Pro
Keeping what you make
The sheets are free forever. Pro turns them into the record: every req with its stage and its owner, every applicant against the req they applied to with a source and a date, every interview and offer with its outcome, your company's name and logo on what you print, no watermark, and an export when the board or the auditor asks.
- Download as PDF
- No Reqnix watermark
- Save every sheet and reopen it later
- Your company's name and logo on the paperwork
- Export every sheet and every record in one go
- Send a sheet to a hiring manager or a client
- Connect Stripe
- Connect your books
$189per month, whole team
Start Reqnix Pro PricingRenews monthly at the price above until you cancel. We email you before any price change.
Recruitment management system: common questions
Where does time to hire start?
Here it starts at application, because that is the clock the candidate experiences. Some desks measure from when the req was approved, which is a longer and equally legitimate number; whichever you pick, keep it consistent or the trend means nothing.
What is a good time to hire?
This site publishes no benchmark and would be guessing if it did. It depends on the role, the market and how many people the process has to convince. The sheet tells you what yours is and which stage owns the days, which is the actionable half.
Does a faster process mean worse hires?
That is a real trade-off and the sheet does not pretend to settle it. What it does say is where the time goes, so a decision to spend more days is a decision rather than a drift.