Business continuity planning in IT is built around systems going down. For a distributed team the more likely disruption is that a region loses power, connectivity or postal service, and twenty people can’t work because of where their hardware is rather than because anything failed.
TL;DR
- Most IT continuity plans cover systems and say nothing about the devices people work on.
- For distributed teams the realistic scenarios are regional: power, connectivity, weather, or a courier network stopping.
- A failed laptop in a market with no local supply is a two-week outage for that person, not a two-hour one.
- Buffer stock held near people beats fast shipping from a central warehouse.
- Decide in advance who can authorise an emergency purchase and up to what value.
- Test the replacement path once. Most teams discover the lead time is double what they assumed.
The scenarios that actually occur
Continuity documents tend to describe dramatic events. The disruptions that affect distributed teams are duller and far more frequent.
A single device fails in a market with no local supply. The most common by a wide margin. One person is offline for as long as it takes to get hardware to them, which in some markets is days and in others is weeks.
Regional power or connectivity loss. Several people offline at once, for an unknown period, with no hardware fault at all. Replacement doesn’t help here; what helps is knowing who is affected, for how long, and what work they can still usefully get done.
Logistics stops. Customs delays, carrier disruption or a public holiday period can add weeks to any shipment. This is the one that converts a manageable single failure into a genuine problem, because the usual answer of shipping a replacement simply stops working.
Why a laptop failure is a bigger outage than people think
In an office, a failed machine is a walk to a cupboard. Distributed, it is a procurement event with a lead time, and the lead time varies enormously by market.
Teams routinely plan on the figure they know, which is the one for their largest market, and apply it everywhere. The result is a continuity position that’s accurate for sixty per cent of staff and badly wrong for the rest, and the people it is wrong for are usually the ones furthest from anybody who would notice.
Measure it first. Work out the real replacement figure for each market before you need it, because the number you assume and the number you get are rarely the same. Ask what a replacement actually takes, door to door, including customs. The spread is usually wider than anybody expects and it changes where you hold stock.
Buffer stock beats fast shipping
The instinct is to solve this with a faster courier. For cross-border replacement that rarely works, because the delay is usually customs rather than transit, and expedited shipping doesn’t expedite a border.
Holding a small number of configured machines inside each significant market converts a two-week problem into a two-day one. The cost is a few devices sitting idle, which is modest against the cost of somebody being unable to work for a fortnight.
What to do:
- List markets with more than about five people.
- Find the real replacement lead time for each, including customs.
- Hold buffer stock where that figure exceeds a week.
- Keep the buffer enrolled and current, not boxed and forgotten.
- Record who holds it and how it is released.
That fourth point is where most buffer schemes fail. A machine held for eight months without updates is a machine that needs half a day of work before anybody can use it, which defeats the purpose.
A team that measured and was surprised
A company with staff across six countries assumed a replacement laptop took about four days anywhere. That figure came from its home market and had never been tested elsewhere.
Timing an actual replacement in each market gave a range from two days to nineteen. The nineteen-day case wasn’t unusual or unlucky; it was the standard path, held up by an import process nobody had looked at. Two further markets came in over ten days.
The response was two spare machines held locally in the three slow markets, at a cost of six devices out of circulation. In the following year four failures occurred in those markets and all four were resolved within two days.
Decide the authority before the incident
The slowest part of most device incidents isn’t logistics. It’s waiting for somebody to approve an unplanned purchase.
Agree in advance who can authorise an emergency replacement and up to what value, and make sure that person is reachable outside working hours. A standing authority of one device up to a set amount, exercised by a named role, removes a day from almost every case and costs nothing until it is used.
Agree the fallback too. If somebody can’t have a company machine for two weeks, what are they permitted to do in the meantime. An answer decided calmly in advance is a great deal better than one improvised by somebody who cannot work and is waiting on a courier.
Where a lifecycle platform helps
RemoAsset is our own product, stated plainly. Its relevance to continuity is coverage: procurement and retrieval in 80+ countries means a replacement can be sourced inside a market rather than shipped across a border, which is the thing that removes the customs delay. Pricing is published, with the Subscription tier from $1,499 a year for companies with 50 to 5,000+ employees, including a 60 per cent reduction on retrieval charges.
Its limits are worth stating. It has no network discovery, so it won’t find hardware you forgot you owned, which matters if your continuity plan assumes spares you can’t actually locate. It has no software licence management. And only the Subscription tier publishes a figure, with the pay-as-you-go tier quoted rather than listed. It doesn’t solve a regional power cut, and nothing in this category does.
Workwize runs its own warehouses, which suits holding buffer stock centrally. Firstbase, GroWrk, allwhere and Deel IT operate on broadly similar lines, and not one of the five publishes a rate card you could plan a budget against. The live Workwize domain is goworkwize.com.
Planning by scenario
| Scenario | People affected | What helps | What does not |
|---|---|---|---|
| Single device failure, fast market | One | Normal replacement | Nothing needed |
| Single failure, slow market | One | Local buffer stock | Expedited shipping |
| Regional power loss | Several | Knowing who is affected | Replacement hardware |
| Carrier or customs disruption | Variable | In-market sourcing | Central warehouse |
| Theft or loss while travelling | One | Remote wipe, then buffer | Waiting for recovery |
The checklist worth keeping
Checklist:
- Real replacement lead time recorded per market, not assumed.
- Buffer stock in every market where that exceeds a week.
- Buffer machines kept enrolled and patched.
- A named person with standing authority to approve an emergency device.
- That person reachable outside working hours.
- An agreed interim position for somebody waiting on hardware.
- The path tested once on a real failure.
Final Thoughts
Continuity planning for distributed teams is less about catastrophe and more about the ordinary case nobody timed. A laptop fails somewhere with no local supply, and the gap between the assumed lead time and the real one is the whole of the outage.
Measure the real figure per market, hold a little stock where it is long, and give somebody the authority to act without a meeting. That’s most of the plan and it fits on a page.
Frequently asked questions
What does business continuity mean for devices?
It is the plan for keeping people able to work when the hardware they depend on is unavailable, whether because a machine failed, was lost, or cannot reach them. For distributed teams this is usually a logistics question rather than a systems one, and it is frequently missing from continuity documents that otherwise cover infrastructure thoroughly.
How much buffer stock should we hold?
Not many. Enough to cover the realistic failure rate over the replacement lead time in that particular market. For a team of 23 in a market where replacement takes two weeks, two machines is usually sufficient. The number matters less than the discipline of keeping them enrolled and updated, because a spare that needs half a day of preparation is not a spare.
Why does expedited shipping not solve this?
Because the delay in cross-border replacement is usually customs rather than transit, and paying for faster carriage does not move a package through an import process any quicker. Sourcing inside the destination market avoids the border entirely, which is why in-market supply beats fast shipping for anything time sensitive.
What should somebody do while waiting for a replacement?
Decide this in advance rather than during the incident. The options are usually a loaner from a colleague, restricted access from a personal device under defined conditions, or accepting the person is unavailable. All three are reasonable depending on the role and the data involved, and the one that causes problems is the undecided version where somebody improvises.
Who should be able to approve an emergency purchase?
One named person. A role carrying a standing limit, reachable outside working hours. The approval wait is frequently the longest single step in a device incident, and it is entirely self-inflicted. A pre-agreed authority for one device up to a set value costs nothing until used and removes about a day from the typical case.
How do we know our plan works?
Time a real one. Run it once on an actual failure and measure it end to end rather than relying on anybody’s estimate. Most teams find the actual figure is roughly double what they assumed, usually because an approval step or a customs process was never counted. Testing once a year in one market is enough to keep the numbers honest.
