The real cost of an unfilled planning seat on a live programme

Programme budgets count a vacant seat as a saving. Programme directors know better. A missing Kinaxis solution architect in the middle of design doesn’t reduce cost; it moves it somewhere harder to see.

Where the cost goes

Schedule. Design decisions queue behind the vacancy. Each week of delay on the critical path carries the whole programme’s burn rate — the integrator team, the client team, the licence clock. On a mid-sized programme that figure is easily ten to twenty times the day rate of the missing person.

Decision quality. Somebody fills the gap. Usually a capable consultant one grade down, making architecture decisions they’ll be living with for years. The cost appears later, as rework, and is rarely attributed to the vacancy that caused it.

The people who stayed. The remaining senior team absorbs the load. Overtime becomes the norm, then resignations. Attrition on a programme mid-flight is the most expensive outcome of all, and it begins with an unfilled seat nobody thought was urgent.

Credibility. A client who sees a gap unfilled for six weeks draws a conclusion about the firm. That conclusion outlasts the programme.

Why it stays unfilled

The hiring cycle — requisition, approval, search, interviews, notice period — is built for permanent roles and runs in months. Programmes run in weeks. The mismatch is structural, and no amount of urgency in the chase changes it.

The alternative is a network that was vetted before the need arose: people whose delivery record is known, whose terms are already agreed, who can be on a call within 48 hours of a brief and on site the following week.

How we close a seat in days

Our Expert Resourcing practice runs on three steps. You brief us — the role, the programme, the date. We present vetted experts, typically within 48 hours, each screened by consultants who have led the same role themselves. They deliver, and we stay accountable, with a replacement guarantee if it’s ever needed.

The day rate of the person who arrives is the smallest number in this story. The weeks of schedule they give back are the largest.

Counting it properly

If you want the number rather than the argument, count it like this.

Burn rate on the critical path. Take the fully-loaded weekly cost of everyone whose work depends on the missing decision-maker — client team included, not just the consultancy. On a mid-sized Kinaxis programme that is routinely £40,000–£80,000 a week. A six-week vacancy on the critical path is a quarter of a million pounds of people waiting, and it does not appear in any line item called “vacancy”.

Licence clock. Platform subscription usually starts at contract, not at go-live. Every week of slip is a week of paying for software nobody is planning in.

The rework multiplier. Architecture decisions taken by someone a grade below the missing role are not usually wrong at the time — they are locally sensible and globally expensive. Industry rule of thumb, and our own experience, puts the cost of unwinding a data-model decision after build at five to ten times the cost of making it correctly first.

Attrition risk. The remaining senior people absorb the gap. Count the replacement cost of one of them leaving mid-programme — search, notice, ramp, and the institutional knowledge that goes with them — and weight it by how likely that is after three months of overtime. Most directors, doing this honestly, get a bigger number than the day rate they were protecting.

Against all of that, the marginal cost of the person you didn’t hire is the smallest number in the calculation, usually by an order of magnitude.

Why the seat stays open

Rarely because nobody is looking. Usually because of three structural mismatches.

The cycle length. Requisition, approval, search, interview, notice: three to five months to bring someone on permanently. Programmes move in weeks. No amount of urgency compresses a notice period.

The specification. “Kinaxis solution architect” is not a specification; it is a label that means different things at three different firms. Without a description of the decisions the person must be able to take, screening filters on tool names and misses the people who can actually do it.

The screen. A résumé scan optimises for keyword density. The question that matters — what has this person delivered, and what did they get wrong and fix — is not in the document.

What “days, not months” actually requires

It is not magic and it is not a database. It requires three things to have happened before you called.

The network has to be vetted in advance by people who have led the same roles, so screening is recall rather than research. Terms have to be agreed with each expert before presentation, so an offer doesn’t stall for a fortnight on rate. And somebody has to stand behind the placement — a replacement guarantee is the only mechanism that aligns the resourcing partner’s incentive with the programme’s outcome rather than with the fill.

That is the whole of it. When those three are in place, a brief on Monday can produce vetted profiles by Wednesday and a person on the programme the following week. When they are not, you get a long list on Friday.

One question to ask any resourcing partner

“Who screened this person, and what have they delivered themselves?”

If the answer is someone who has never run the role, you are buying a search. If it is a consultant who has run that role on a comparable programme, you are buying judgement. On a live programme with a critical path, the difference between the two is the whole point.