Outsourcing Field Service: When External IT Technicians Pay Off

Outsourcing field service pays off when your locations are spread out, the number of jobs fluctuates and your IT specialists should move projects forward instead of swapping printers. In-house technicians, by contrast, make sense with many jobs at a few locations close together. What matters is an honest calculation of job volume, travel time and utilization.

A broken printer in Hamburg, a new workstation in Munich, a POS system in Leipzig: if you operate multiple locations, you know the drill. Keeping your own technicians everywhere is expensive – and yet you still need fast help on site. This article offers a decision guide with a comparison table, a calculation method, billing models and a checklist for choosing a provider.

What field service covers

Field service refers to all IT work that has to take place physically on site – in other words, wherever remote maintenance reaches its limits. Typical areas include:

• IMAC: Install, Move, Add, Change – setting up, relocating, expanding and modifying workstations
• Break & Fix: resolving faults, swapping devices
• Rollouts: new hardware in planned waves
• Infrastructure: network, Wi-Fi, rack & stack

On top of that come commissioning printers and POS systems, replacing components under the manufacturer’s warranty, and supporting location openings and closures.

In-house technicians or external field service?

Both models have their place. What matters is how many jobs come up, where they come up and how evenly they’re spread across the year. The table summarizes the most important criteria.

Criterion	In-house team fits when …	External field service fits when …
Locations	a few locations are close together	locations are spread across regions or all of Germany
Job volume	consistently high and easy to plan	fluctuating, with short-notice peaks
Know-how	highly specialized knowledge that is hard to transfer	standard devices and repeatable processes with a checklist
Travel time	short distances, technicians are fully utilized	technicians from the region, no overnight stays for your own staff
Cover	you arrange cover for vacation and sick leave yourself	cover is part of the service scope
Cost structure	fixed personnel costs are covered by steady workload	variable costs per job, flat rate or allotment

When outsourcing pays off – and how to calculate it

External field service teams pay off especially when your locations are spread out and job volumes fluctuate, when peaks such as rollouts or relocations are coming up, or when your internal IT should focus on strategic topics. A good indicator is travel time: if your technicians spend more time in the car than at the device, you lose money – and waiting time for colleagues on site rises. New locations are also a good occasion: instead of building your own staff there right away, you cover the need flexibly with a partner first and reassess later based on real job numbers.

Here’s how to arrive at a reliable number:

1. Evaluate job data: pull the number, type, location and duration of jobs from the last twelve months out of the ticketing system
2. Record travel and waiting time: how much of the paid time is actually spent at the device
3. Determine the full cost of a technician: salary and overhead, vehicle, tools, training, cover – divided by productive hours on jobs
4. Price external offers for the same job volume: including travel, minimum times and surcharges
5. Factor in peaks and growth: include planned rollouts, relocations or new locations in both calculations

Practical example and interplay with remote maintenance

Suppose a retail company operates stores in several federal states and a small IT department at headquarters. Most faults can be resolved by remote maintenance. But when a POS terminal fails or a network switch has to be replaced, someone is needed on site. With external field service, headquarters reports the job through the ticketing system, a technician from the region takes over, works through the agreed checklist and documents the result directly in the ticket. Internal IT keeps the overview without having to drive anywhere. When a project such as a POS changeover comes up, the team simply scales with it.

The most economical field service is the one that doesn’t have to drive at all. That’s why every job should be preceded by a short check by IT support: can the problem be solved by remote maintenance? Is it just a missing setting, a driver or a restart? Only when it’s clear that hardware has to be swapped or work has to be done on site does a technician head out. Preparation matters just as much: before traveling, the technician should know which device is affected, what has already been tried and which spare part to bring. That way, the first visit is ideally also the last.

Billing models at a glance

How field service is billed depends on the type and predictability of the jobs. What matters is that travel, waiting time, follow-up appointments and surcharges for work outside business hours are clearly regulated – otherwise the invoice holds surprises.

Model	Best suited for	Advantage	Watch out for
Flat rate per job or job type	recurring, clearly defined jobs such as IMAC or device swaps	high cost predictability	What is included in the price, and what counts as extra effort?
Billing by effort	irregular tasks and faults of unclear scope	you pay only for time actually worked	minimum times, call-out fees and surcharges
Project price	clearly defined undertakings such as a rollout or a site move	fixed sum for a defined scope	fix scope and exclusions in writing
Framework agreement with allotment	ongoing need with fluctuating volume across several locations	fixed terms and quick call-off	What happens to unused allotment?

What to look for contractu­ally

Clear service descriptions, dedicated contacts and complete documentation of every job are the foundation. Just as important: the technicians should know your processes – through briefings, checklists and access to your ticketing system.

Service description and response times

What exactly is part of a job, and what isn’t? Distinguish between response time (start of handling), time to arrive on site and time to restore service, and define service hours. What applies to which type of fault, and what happens outside business hours? The more precisely this is recorded, the fewer discussions you’ll have when it matters.

Docu­menta­tion and reporting

Every job should be traceable: what was done, which device with which serial number was swapped, is the problem resolved? The documentation belongs in your own ticketing or asset system so it stays with you if you change providers. Regular reports show where faults cluster – and where an investment achieves more than the tenth job on the same device.

Data protection and confi­den­tiality

Technicians have access to devices and rooms, in some cases also to personal data. If they come into contact with it, a data processing agreement under Art. 28 GDPR is generally required. Also regulate confidentiality obligations, access, the handling of credentials and proof of data erasure for old devices.

Spare parts and logistics

Who provides replacement devices, where are they stored, how do defective devices come back? Clarified logistics decide whether a problem is solved in one visit or in three. Also clarify how warranty cases are handled with the manufacturer.

Management and legal framework

External technicians should work as if they were part of the team – legally, though, they aren’t. If they are de facto integrated into your organization like your own employees and follow your individual instructions, this can be treated as temporary agency work (Arbeitnehmerüberlassung), with consequences for licensing requirements and liability. So manage through service descriptions, checklists and tickets, and have the contract structure reviewed legally if in doubt.

How the start with a field service partner works

1. Inventory: record locations, devices and previous job types
2. Service catalog: define job types, processes and response times
3. Briefing: provide checklists, access and escalation paths
4. Pilot phase: closely monitor and evaluate the first jobs
5. Regular operation: with reporting and regular check-ins

Checklist for choosing a provider

• Does the partner cover all your locations?
• Are there dedicated contacts for planning and escalation?
• How is every job documented, and do you have access to it?
• Can peaks such as rollouts or relocations be covered at short notice?
• Are data protection, access and old devices regulated contractually?
• Do the technicians work to your checklists and in your ticketing system?
• Are billing, travel, waiting time and surcharges clearly defined?

How Nano Concepts supports you

Outsourcing field service doesn’t mean giving up control. With clear processes, you get flexible capacity exactly when you need it. Together with our IT service partners RELEDER and FAIMA IT Services, we operate across Germany: Nano Concepts plans and coordinates the jobs, and our partner teams work on site. We handle field service and IMAC, planned IT rollouts – as described in our checklist on planning an IT rollout – and IT support from 1st to 3rd level. In a free initial consultation, we clarify which model fits your locations.

This article does not replace legal advice.