The Business Interruption Number: What a Lost Trading Day Really Costs a UK SME

  • 23 hours ago
  • 0

A recovery plan tells you how to get back on your feet. A business interruption number tells you what being away costs. Many SMEs have one, or at least a document that resembles one, and not the other.

The number in an insurance schedule may have been set months earlier by someone in finance using a rule of thumb. If a loss occurs, an adjuster will rebuild the picture from records: what trade was affected, which costs continued or fell away, what extra spending was necessary and how long the business was disrupted. The gap between the declared value and a figure the records can support is where a claim can come under pressure.

A lost trading day is not simply a day’s turnover. Turnover is where most estimates begin, and it is rarely where an honest answer ends.

When trading stops, some costs continue: payroll, rent and finance commitments do not politely pause. Other costs, such as materials or supplier spend tied to sales, may fall away. Meanwhile, the business may incur new costs to keep serving customers or restore activity. In plain terms, the calculation is shaped by lost gross profit, adjusted for costs saved, together with reasonable additional spending to reduce the interruption.

That makes the honest number a curve rather than a line. The impact changes as the disruption unfolds. The steepest part may be the first few days, when staff are firefighting, customers are waiting and decisions about temporary workarounds have to be made before anyone has a complete picture. A sound estimate has to reflect how the business actually trades, not just divide an annual figure into convenient daily portions.

The recovery time you achieve matters more than the recovery time written in the plan. An untested recovery objective converts directly into a financial assumption. If a plan says a process will return quickly but nobody has rehearsed it, the declared value may rest on hoped-for capability. Recovery testing is therefore not an administrative extra. It is how an organisation finds out whether its assumptions can survive contact with a real outage. A useful disaster recovery exercise demonstrates what can be restored, in what order and with which dependencies.

The loss clock starts at the first failed transaction, not when someone declares an incident. And the systems named in a recovery plan are not always the whole estate that makes that transaction possible. A core application may be available while its integration, file share, print queue, card terminal or phone system is not. These overlooked dependencies can leave the business unable to trade even when the main platform appears healthy.

Mapping them is a business exercise, not simply an infrastructure inventory. Trace each affected process to the application or scheduled job it uses, the platform it depends on, the named person responsible, and the supplier involved. That map may be more useful to an adjuster than a policy document: it shows what actually stopped, how the failure spread and where recovery depended on another party.

A single brass dial on a dark, understated control panel

This is especially important for IBM i Management. The platform may run the overnight batch, order processing, warehouse or despatch jobs, or month-end routines. Yet the recovery time objective conversation is often impossible to answer because nobody has measured what a missed night’s processing costs the business.

That figure is not technical. It is commercial, and it often lives with one person who understands which work can wait and which cannot. If a batch does not run, some processes may carry over to the next day, creating a backlog and extra handling. Others may block order fulfilment, stock visibility or invoicing altogether. The business needs to know which is which, and what the consequences are, before it can make a credible recovery decision.

High availability and replication can extend protection beyond backup, but only for the scope they were designed to cover. Replication does not automatically prove that dependent applications, jobs, interfaces and operational steps will all resume as required. The wider estate matters too: the machine may be healthy while users cannot reach it because the network, terminal sessions or print path has failed.

There is also a time gap to examine. A recovery tier purchased years ago may no longer match the business’s current reliance on the platform. A measured, dated walkthrough of a failed overnight run can expose that mismatch. It produces a real recovery time and a real cost figure, grounded in what the business had to do and what it could not do. That evidence is more valuable than a recovery objective that has never been tested.

For organisations using Dynamics 365 Business Central, transaction visibility can help separate revenue that was deferred from revenue that was genuinely lost. That distinction can make the difference between a defensible claim and a hopeful estimate. The consultancy-led Dynamics 365 Jump Start service can help businesses consider how the system and its processes support better operational and financial visibility.

Microsoft documents how administrators can copy an environment for use as a sandbox, which can support a review or replay of a period. A copy is a point-in-time snapshot, however, not a live replica that continues to follow production activity. It can inform an investigation, but it should not be mistaken for continuous evidence of what happened. See Microsoft’s guidance on production and sandbox environments.

Cloud Solutions introduce another shared responsibility into the calculation. Recovery time may depend on a provider’s contractual commitments, the service actually delivered and the customer’s own configuration and dependencies. The calculation should reflect real performance, not just a headline commitment. A service credit is not the same as the business’s interruption loss, and provider records may become part of the evidence.

Technology Expense Management gives finance and IT a cleaner cost base from which to work. It helps establish what capacity, connectivity, licences, devices and contracts the business was actually paying for at the moment of loss. That earns its keep twice: first by identifying spend that cannot be justified, and then by providing a schedule of what existed when an adjuster asks.

Increased cost of working may include emergency connectivity, temporary devices, extra licences or call routing. A business that already knows its suppliers, contract terms and costs can make decisions in hours rather than negotiate from scratch in a crisis. A current Technology Expense Management view is therefore not just a cost-control exercise. It is part of being ready to explain both the normal cost base and the additional expenditure used to keep trading.

Compliance is most useful here as a consultancy discipline, not a certificate to display. ISO 27001 expects an organisation to understand business impact and make continuity arrangements. The valuable output of a business impact analysis is a costed understanding of what matters and for how long, not a document produced only for an auditor. Cyber Essentials focuses on technical controls against common cyber threats rather than business continuity, so it will not generate the interruption number. The evidence behind those controls can still support a constructive discussion with an insurer.

Operational records help place the loss in time. Helpdesk Support ticket timestamps can identify the first reported failure. Network Solutions records, including firewall and remote access logs, can show when access broke down. Voice and Connectivity call records may help establish when customers could no longer reach the business. Managed IT Services should include someone contractually accountable for keeping the recovery claim honest, by preserving relevant records and joining the technical timeline to the business impact.

A dark staircase with a narrow band of warm light falling across the steps

The work is practical: map the dependencies, measure one real recovery end to end, and price a lost trading day with finance rather than guessing it. Reconcile the declared value against the recovery capability demonstrated, keep the cost base current and review the assumptions after any real outage, while the operational detail is still fresh.

A plan describes how to recover. A number describes what the interruption costs. The Fractal IT Director brings those questions together, setting the strategy first and using specialist partners and bolt-on execution services where needed. David’s consultancy-led approach is to connect technology decisions to business impact, so the figure has a defensible basis rather than a convenient one. Find out more about Evestaff IT Support and Consultancy. For a broader view of the Evestaff group's services, visit https://evestaff.co.uk. The plan is what helps the business recover; the number is the one the board actually feels.

Join The Discussion