At 03:00, an incident raises two questions. The technical one is what has failed and what will restore service. The commercial one is what the business is allowed to buy, from whom, at what price and on whose authority. Most continuity plans are detailed about the first and remarkably quiet about the second.
A recovery plan tells you what to restore, not who is allowed to pay for it. In the first hour, an incident is often a purchasing problem wearing a technical costume. The engineer may know that a replacement switch, temporary circuit or specialist consultant will get the business moving. But if nobody can approve the commitment, a clear technical fix can sit idle while the loss continues.
Delegated financial authority is usually designed for daylight. There is a purchase order, a threshold that requires a second approval and a budget holder who can be found between meetings. At 03:00, the approver may be asleep, travelling or the one person whose name appears against every relevant spending limit.
A workable plan names who may commit emergency spend, how much they may authorise, who acts as deputy and what happens if neither can be reached. It also distinguishes the incident manager, who coordinates recovery, from the budget holder, who can release money. Assuming one role automatically carries the other is a neat way to discover a governance gap under pressure.

There is a related insurance tension. Business interruption or increased cost of working cover may expect a business to act reasonably to reduce a loss, while its own finance process expects approval before a commitment is made. The business can end up with the worst of both: spending in a hurry and disputing the decision later, or waiting for a signature while the loss grows. Policy wording and circumstances vary, so check the terms with your broker. Operationally, the answer is to agree an emergency spending limit in advance, give it a named holder and defined purpose, and require the decision to be recorded and reported the next working day rather than held up for prior approval.
Supplier terms matter just as much as internal authority. Emergency prices are often higher because the business has no account, no credit terms and no agreed rate with the supplier able to deliver that day. A standing arrangement can establish named contacts, escalation routes, emergency rates and the practical terms for late-night or weekend orders. It should also account for late December, when the buyer’s approvers and the supplier’s account team may both be on leave.
This is an ordinary, unglamorous use of Technology Expense Management. TEM should already provide a view of suppliers, contract terms, renewal dates and the organisation’s spend baseline. Turning that information into an emergency purchasing schedule is a short step, not a new transformation programme. It can also prevent the business buying capacity it already pays for but has never tested or used.
Then there are payment mechanics: boring, decisive and frequently overlooked. Corporate card limits may have been set years ago for travel. The person coordinating recovery may not hold a card at all. Finance may not be able to release a payment at the weekend, and a supplier may not dispatch hardware without cleared funds or an account in good standing. If the finance system itself is unavailable, somebody still needs a defined route to record a purchase made at 03:00 afterwards. The paper trail matters twice: for the audit and for any claim.

A Disaster Recovery rehearsal should therefore reach the purchasing step, not stop when the restore begins. Test who authorises, who pays, which supplier is called, what rate applies and how long delivery is expected to take. A plan that says “procure replacement hardware” without a supplier, limit or named authority is a sentence, not a control.
The economics become particularly important for IBM i Management, where recovery can depend on specialist support and equipment arrangements that are not interchangeable with a routine desktop purchase. Emergency disks or replacement POWER hardware may need to come through a maintenance provider. Feature codes and licence keys may arrive by email and need to be accepted by someone with the right authority. Off-site media or tapes may need to be retrieved. Above all, the specialist who can diagnose and recover the platform may need to be engaged within the hour, at a call-out rate that should not be a surprise to anyone.
In a mid-sized business, it is entirely plausible that nobody available at two in the morning can approve a four-figure call-out. The quotation then lands in an inbox nobody is watching. The technical specialist is ready; the purchase is not. Pre-agreed authority, a named deputy and a rate card make this a manageable decision rather than an improvised negotiation.
A quieter risk is maintenance that lapsed because a renewal was never questioned or properly tracked. The emergency then turns what might have been a covered service call into a capital purchase at short notice. Regular Technology Expense Management can help make those renewals and dependencies visible before an outage exposes them.
For every critical platform, keep a single page stating who can authorise emergency spend, the supplier and escalation route, the agreed rate and the deputy. That is useful IBM i Management in practical form: not another binder, but a decision that can be made when the right people are not all in the same room.
The same gap can appear in Dynamics 365 Jump Start and Microsoft Dynamics 365 Business Central. Purchase approval workflows, spend thresholds and segregation of duties support a business operating normally. A single approver who cannot be reached can block a genuine emergency order. Conversely, quietly widening one person’s approval limit to avoid routine friction may weaken the control the organisation will later need to evidence.
There is also a practical wrinkle: emergency spend may need to be entered after the event in the very finance system that was unavailable. Decide in advance who has authority to raise retrospective purchase orders, what supporting record is required and how the entry will be reconciled with the original approval. A verbal “get it sorted” can be useful in the moment; it is not, by itself, a durable purchasing record.
With Cloud Solutions, recovery capacity is also a procurement question. Who owns the provider account? Who can raise a priority ticket? Which support tier does the business actually have? What happens if the account owner is unavailable, and can capacity be added before a purchase order clears? These are questions about access and authority as much as architecture.
Network Solutions and Voice and Connectivity bring the issue into sharp focus. Emergency connectivity and temporary call routing are among the purchases most likely to be made during an incident, but delivery lead times mean that a decision at 03:00 may become equipment at noon. Establish who authorises it, who chases delivery and whether the business already pays for failover it has never invoked.
The contract for Helpdesk Support or Managed IT Services should make clear what is included, what is chargeable and which rates apply outside normal hours. It should also define whether an incident manager’s instruction to “just get it working” authorises additional spend, or whether that phrase will become an argument three weeks later. A managed provider with defined emergency authority and a pre-agreed rate card is easier to work with than a supplier waiting for a signature.
Supplier controls are part of the wider governance picture. ISO 27001 expects relevant supplier relationships and ICT supply chain arrangements to be defined, controlled and reviewed, with decisions made under pressure still leaving an appropriate record. The NCSC’s supply chain security guidance is a useful external reference for understanding key dependencies and reviewing arrangements before they are needed. Cyber Essentials addresses technical controls; it will not decide who can authorise an emergency purchase.
An emergency purchase approved by a named person within a documented limit, then reported the next working day, is not a failure of control. It is a control working as designed.
Decide the emergency limit, name its holder and deputy, record the suppliers and rates, and set a delivery expectation for each. Test the whole chain once with a real quotation, then review it after any real outage while the invoices are still on the desk. That is the practical value of an expert IT Consultancy: the strategy is set in advance, with a Fractal IT Director bringing financial authority, suppliers and recovery into the same plan. Specialist partners and bolt-on managed services can then execute against that strategy, rather than improvise it at 03:00.
For a broader view of the Evestaff group's services, visit https://evestaff.co.uk.
A recovery plan describes how the business gets back up. A spending authority schedule describes who may pay for it. In the first hour, the second document is often the one that actually moves things.
Join The Discussion