Rolling out new hardware to a few sites in one country is a logistics task. Rolling it out to hundreds of sites across ten countries is a programme, with customs, languages, local holidays and many more chances for things to go wrong. This guide sets out how to plan a multi-country IT roll-out so that site 300 in Warsaw is delivered to the same standard as site 1 in London.
It is written for programme managers, vendor managers and service delivery leads at IT service companies and MSPs. For how we deliver this work, see our multi-site roll-outs service.
1. Build a reliable site list
Every roll-out starts with a site register, and most problems start with a poor one. For each site, capture:
- Full address, local contact name and email, and opening hours
- Access rules, such as building passes, induction or escort requirements
- Current equipment, cabling and power at each install point
- Local constraints such as parking, lifts, loading bays and working-hour limits
If the data is thin, run surveys first. Our IT site survey checklist covers what to collect.
2. Plan logistics and customs early
Shipping is usually the longest lead time in a multi-country programme. Moving kit from a UK hub to sites in Germany, France or the Netherlands now involves customs declarations, and shipments to Switzerland, the UAE or the USA have their own import rules.
- Decide who is importer of record in each country
- Prepare commercial invoices with correct descriptions and values
- Check whether any equipment needs local approval or certification
- Choose between central staging and regional distribution hubs
Regional hubs, for example one in the EU and one in North America, often cut transit times and customs risk compared with shipping everything from one warehouse.
3. Localise the kit
Small details cause big delays. Check power cords and plug types per country, keyboard layouts (French AZERTY and German QWERTZ differ from UK QWERTY), and any regional software images or language packs. Labelling each box with site ID and ticket reference saves hours at the loading bay.
4. Stage and pre-configure
Pre-configuring devices before they ship reduces time on site and makes each visit predictable. Agree a staging standard, a build checklist and a test that proves the device is ready before it leaves the warehouse.
5. Write one runbook
Every engineer, in every country, should work from the same runbook. Keep it in English, numbered and short. Include:
- Pre-arrival checks and who to call on arrival
- Step-by-step install and test sequence
- Required photos, before and after
- Removal and handling of old equipment
- Sign-off form and escalation path
6. Schedule in waves
Start with a pilot of a handful of sites, ideally in two or three countries, then fix the runbook before scaling. Group later waves by region, so engineers in Paris, Lyon and Brussels work through nearby sites together.
Build local calendars into the plan. August is slow across much of Southern Europe, public holidays differ by country and sometimes by region, and Middle East working weeks differ from Europe’s.
7. Choose engineers and set SLAs
Local engineers keep travel costs down and handle local language and access norms. A travelling core team suits complex or sensitive sites. Most programmes use both, with clear rules on who covers what. Agree response levels for follow-up faults, and check how they work on our dispatch and SLAs page.
8. Control quality and reporting
Review photos and sign-offs daily, log exceptions centrally and report progress against the plan by country and wave. A simple dashboard showing sites completed, failed and rescheduled is enough for most customers.
9. Close out properly
Confirm old equipment has been collected, returned or disposed of in line with local rules, and that asset records are updated. Hand over a final site-by-site report.
Where we deliver
We have 2,000+ field engineers worldwide and 285 cities on our coverage map, coordinated from London by a 24/7 service desk that responds in under 30 minutes all year. Roll-outs we support often span the United Kingdom, Germany, France, Netherlands, USA and UAE, with engineers in cities such as Frankfurt, Amsterdam, Madrid, Dubai and New York. Everything is delivered under your brand through our white label field services and our field service partners programme.
Frequently asked questions
How far ahead should we plan a multi-country IT roll-out?
Allow enough time for site surveys, customs and shipping before the first wave. Import lead times are often the longest item, so confirm them before you commit to install dates with the customer.
Who should be importer of record for roll-out equipment?
That depends on your contract and each country’s rules. Agree it before shipping, because a missing importer of record is one of the most common reasons kit gets held at customs.
Should we use local engineers or a travelling team?
Local engineers suit large site counts and reactive follow-up. A travelling team gives consistency for smaller, complex deployments. Many programmes use local engineers with a short pilot led by a core team.
How do you keep quality consistent across countries?
One runbook, one photo checklist and one sign-off form for every site, in English, with exceptions logged centrally. We review the first sites of each wave before scaling up.
Planning a multi-country roll-out?
Send us your site list and timeline, and we will come back with engineer coverage by country and our partner rate card.