Most refresh requests aren’t rejected. They’re postponed, which is a different problem.
A deferred infrastructure request isn’t a decision against the work, it’s a decision to not decide yet. The useful response is to capture why it stalled while the detail is fresh, keep the underlying information current rather than letting it age, and come back when something has genuinely changed. Resubmitting the same case with more urgency is the most common second attempt and the least effective one.
“Let’s revisit this next quarter” is the outcome most infrastructure requests actually get. Not a no, but not a yes either.
That ambiguity is the hard part. A clear rejection at least tells you where you stand. A deferral leaves the work undone, the equipment ageing, and no obvious next step beyond waiting for a moment that may not announce itself.
What happens in that gap largely determines whether the second attempt goes better than the first.
Was it deferred, or was it declined?
These get treated the same way and shouldn’t be.
Declined means someone assessed it and decided against it. There’s a reason, and usually a stated one: the money is committed elsewhere, the risk is considered acceptable, or the business has a different plan for those systems. Understanding that reason matters more than reopening the question, because reopening it without addressing the reason gets the same answer faster.
Deferred usually means nobody has decided anything. The proposal arrived during a busy period, or raised a question nobody could answer in the room, or simply didn’t rank against what else was competing for attention that week. Nothing was rejected on its merits.
The distinction matters because they call for different responses. A decline needs the underlying objection addressed. A deferral needs better timing and, often, one missing piece of information.
If you’re unsure which you got, ask. “Is this a not yet or a no?” is a reasonable question and most people will answer it honestly.
The first week matters more than the next three months
Whatever happened in that conversation is clearest immediately afterwards, and it fades quickly.
Three things worth writing down while you still remember them precisely:
- The question you couldn’t answer. Almost every deferred request has one. A cost you didn’t have to hand, a timeline you couldn’t commit to, a question about whether it could be staged. That gap is usually the actual reason, whatever the stated reason was.
- The stated reason, in their words. Not your interpretation of it. “We’ll look at this in the new year” and “I’m not convinced this is urgent” point to very different second attempts.
- Who said what. If several people were involved, their positions probably differed. That’s worth knowing when you decide who to approach first next time, a point we covered in which arguments land with each decision maker.
This takes twenty minutes and it’s the single highest-value thing you can do after a deferral. Without it, the second attempt is built on a vague memory of why the first one didn’t land.
The gap isn’t neutral
The assumption behind most deferrals is that nothing much changes by waiting. For infrastructure in 2026, that assumption doesn’t hold, and being able to show it is often what makes the second conversation different.
Three things move while you wait.
- Replacement cost. Gartner expects average PC prices to be 17% higher than 2025 levels by the end of 2026, driven by memory manufacturers shifting capacity toward AI infrastructure. A quote from six months ago is no longer the number.
- The cost of staying put. Organisations running Windows 10 on extended security updates are now in the second year of that program, which began on 14 October 2026. Microsoft’s documentation is explicit that the program is purchased by year and that coverage is cumulative, so an organisation enrolling later pays for the years it skipped as well as the year it wants. Deferring enrolment increases the total rather than reducing it. Worth confirming current pricing through your licensing partner, since it varies by agreement.
- The equipment itself. Devices don’t hold their position during a deferral. Warranties lapse, failure rates climb, and the proportion of the fleet past end of support grows.
None of this is an argument for urgency theatre. It’s that “nothing changes if we wait” is a factual claim, and you’re usually in a position to show it isn’t true.
What makes the second attempt different
Persistence isn’t an argument. Coming back with the same case and more emphasis tends to confirm the original instinct that this could wait.
What changes the outcome is new information. Specifically, one of four things:
- The missing answer. If the request stalled on a question you couldn’t answer, answering it is the entire job. Everything else in the case already worked well enough to get a hearing.
- A changed input. Pricing moved, a lead time extended, a support date passed, a device failed. Any of these legitimately reopens a decision that was made without them, and it isn’t reopening a debate, it’s reporting a change.
- A smaller version. A deferral is sometimes a scope problem rather than a merit problem. A phased proposal that starts with the highest-risk portion is easier to approve than a single large number, and it gets work moving.
- A different moment. Infrastructure conversations land better at some points than others, which is the subject of when’s the best time to talk about new hardware. If the first attempt was badly timed rather than badly made, the case may need nothing except a better week.
What not to do
Four responses that tend to make the next attempt harder.
- Resubmit immediately. Coming back within a fortnight with the same material signals that you didn’t hear the answer. It also means nothing has changed, so there’s nothing for anyone to reconsider.
- Go around the person who deferred it. Occasionally this works. More often it costs you the relationship with someone whose support you’ll need, and the person you approached will usually route it back to them anyway.
- Let it go quiet completely. The opposite failure. If nothing is heard about it for eight months, the second attempt starts from scratch, and the information in it will have aged badly. A brief, factual update when something genuinely changes keeps it alive without being a nuisance.
- Treat it as a verdict on the work. Most deferrals have nothing to do with the quality of the case. Reading it as a judgement produces a second attempt that’s either defensive or over-argued, and neither helps.
Keeping the material current
The practical problem with a deferral is decay. Six months later the fleet audit is out of date, the quotes are stale, the warranty positions have shifted, and rebuilding all of it is a bigger job than it was the first time.
That’s usually what turns a deferral into a permanent postponement. Not a decision, just the cost of starting again.
The organisations that come back successfully are the ones where the underlying picture stays current, so that when a moment opens, the case is a short update rather than a project.
Where to start again
If your refresh was deferred and the material has aged, our free hardware refresh business case rebuilds it: a current assessment of your environment, a total cost of ownership analysis, an infrastructure risk analysis, and a phased plan you can take back with numbers that hold up.
Coming back with a current picture and a staged option is a materially different conversation from coming back with the same proposal. There’s no obligation attached.
If you want a figure before that, the cost of delay calculator gives you an indicative view of what the deferral is costing in a couple of minutes.
FAQs
What should you do if your IT budget request is rejected?
Establish first whether it was declined on its merits or simply postponed. A decline needs the underlying objection addressed. A postponement usually needs better timing and one missing piece of information, most often an answer to a question you couldn’t give in the room.
How soon should you resubmit a deferred hardware request?
Not immediately, and not only when something has changed. Resubmitting the same case within a few weeks signals that nothing is different. The better trigger is a changed input, such as a price movement, a support date passing, or an equipment failure.
Does deferring a hardware refresh save money?
Not reliably in current conditions. Replacement costs have risen through 2026, and extended support arrangements for unsupported operating systems are priced cumulatively, so delaying enrolment increases the total rather than reducing it.
How do you keep a deferred proposal from being forgotten?
Keep the underlying information current rather than the proposal itself alive. Fleet condition, warranty status and replacement costs all age. A brief factual update when something genuinely changes is more effective than periodic reminders.
Is a deferral the same as a rejection?
No. A rejection is a decision made on the merits. A deferral usually means no decision was made at all, often because the request arrived at a difficult moment or raised a question nobody could answer. They call for different responses.