The ticket has been in the queue for four days. The vendor comes back: no bug, the report just wasn't configured to show the field. They've added the column. Ticket closed.
Your engineering roles are still in the market. You still can't clearly see how long they've been open or what the cumulative vacancy cost is running at. The column is there now. The underlying business problem stayed exactly where you left it.
This is the pattern. TA system frustrations get routed to IT or the vendor as technical issues, get resolved as technical issues, and the business cost of the underlying gap stays invisible because it was never part of the scope.
When time-to-fill data is broken in your ATS, the ticket gets logged as a reporting configuration issue. Fixing the configuration addresses the symptom. The hiring strategy question underneath it needs a different conversation entirely.
Without reliable time-to-fill data, you lose visibility on which roles are consistently running long. You lose the pattern you'd need to make a case for changing the sourcing approach, because you can't show leadership what you can't see yourself.
For a senior hire at £90,000 in annual salary, each additional week of vacancy time costs roughly £3,460/week in lost productivity. A TA leader who can put that number in the room has a business case. One who's logging configuration tickets is still talking to the wrong team.
Offer management is where a lot of time-to-accept drag hides. When offer letters get drafted manually because the ATS isn't connected to the document workflow, approvals happen over email and the candidate waits. An offer that should go out in 24 hours takes four days. For a candidate who's been sitting on a competing offer since the debrief, that gap is real risk.
The cost of a first-choice candidate going elsewhere while waiting for paperwork includes the full cost of the preceding recruitment cycle, plus the cost of the role staying open longer. Nobody calculates it as a cost, because it never made it into a support ticket.
Interview scheduling compounds the same way. When scheduling happens over email because the ATS functionality was never set up properly, every round requires manual coordination. Across 100 hires per year, two extra days of scheduling friction per hire adds up to roughly £93,000 in cumulative vacancy cost. The configuration problem is solvable. The business impact has never been calculated.
Every TA frustration has a cost on the other side of it. Getting to that number is what determines who the conversation involves.
"The ATS can't report time-to-fill properly" stays as a TA team problem. "We have 50 open roles that have averaged 12 weeks in market, at an estimated cost of £114,000 per week in lost productivity" gets the CFO in the room.
The translation is mostly arithmetic. It needs someone who understands both the system gap and what that gap costs in terms the board recognises. That's where Udder works. We go into HRIS and ATS configurations, identify the gap between what's set up and what the business actually needs, and quantify the cost in language that gets the right people in the room.
The conversation changes when the number is in it.
We publish one piece a week on TA and HR technology that actually works. If this reframe was useful, there's more where it came from.