Simplify Networks is the field service partner for MSPs and IT service companies: smart hands, rack and stack, IMAC and break-fix, cabling and multi-site roll-outs, delivered on site in the UK and worldwide under your brand.

A statement of work for field services is the document that decides whether an onsite programme runs quietly or generates weekly escalations. When an IT service company or MSP brings in a partner to provide engineers under its brand, the contract covers liability and payment, but the statement of work (SOW) is what the engineer, the dispatcher and the customer site actually work from. This guide explains how to write one that a field service partner can deliver against across the UK and worldwide.

Statement of work for field services: labelled rack of network equipment ready for an onsite engineer

It is for vendor managers and service delivery managers handing work to a field service partner.

SOW, work order or MSA: which document does what?

Most partner relationships use three layers, and many problems start when they blur together.

  • Master services agreement (MSA): the legal terms. Liability, insurance, confidentiality, payment terms, non-solicitation. Signed once.
  • Statement of work: the operating rules for a programme or a type of service. What is in scope, what “done” looks like, service levels, reporting, rates basis and how changes are handled. Usually one per customer programme or per country.
  • Work order: a single job. Site address, date, contact, task, parts. Hundreds may sit under one SOW.

If a detail applies to every visit, it belongs in the SOW. If it changes per visit, it belongs in the work order. Putting standing rules into each ticket is how they get missed.

The ten sections every field services SOW needs

Below is the structure we see work best for multi-site and multi-country programmes. Use it as a checklist when drafting or reviewing.

1. Background and objective

Two or three sentences on the programme, such as “break-fix support for 140 retail stores in the UK and Ireland” or “smart hands for two colocation suites”. Engineers and dispatchers make better judgement calls when they know why the work exists.

2. Service catalogue

List each service by name with a one-line definition: IMAC and break-fix, smart hands, rack and stack, cabling, site surveys. Give every service a code so work orders can reference it, such as BF-4H or SH-NBD.

3. Scope boundaries

State what is in scope, what is out of scope and what needs approval first. Out-of-scope lists prevent more disputes than in-scope lists. Common examples: working at height above a set level, electrical work beyond plugging in, configuration changes without a remote engineer on the call, and lifting equipment above a stated weight without a second person.

4. Locations and coverage

Attach the site list or describe the coverage area, and say how new sites are added. For international programmes, list the countries and note any that need extra lead time. Our coverage map shows the cities we already work in.

5. Service levels and hours

Define each service level precisely: when the clock starts, whether it measures arrival or resolution, the hours it applies to and what pauses it, such as waiting for site access or a customer contact. Our dispatch and SLA page explains how we report attainment.

6. Engineer requirements

Skills, manufacturer familiarity, vetting level, dress code, PPE and whether engineers must carry your branded ID or introduce themselves under your company name. For white-label field services, spell out what engineers say when a customer asks who they work for.

7. Site access and safety

How access is requested, how far in advance, who supplies the engineer’s details to the site, and what the engineer must bring. Data centres often need names and photo ID registered ahead of the visit; offices and retail sites may need induction or a permit to work.

8. Parts and tools

Who ships parts, where they are delivered, who returns faulty units and within what time. State the standard toolkit you expect, plus anything special such as a console cable, label printer or fibre cleaning kit.

9. Reporting and closure

What a completed job looks like: photos before and after, serial numbers in and out, sign-off name, time on and off site, and the format of the report. If the report goes to your customer under your brand, say so.

10. Commercials and change control

Describe the pricing basis without burying the rate card in the SOW: per visit, per hour, per day or retainer, plus how overtime, aborted visits and extra time are handled. Then add a short change process so scope can grow without a new contract.

A quick reference table for the scope section

Topic Weak wording Clear wording
Arrival “Engineer to attend promptly” “On site within 4 hours of dispatch, 08:00 to 18:00 Monday to Friday”
Completion “Fix the fault” “Replace the part, confirm the device is online with the remote engineer, upload photos”
Extra time “Reasonable overruns accepted” “Over 30 minutes beyond the estimate needs approval from the dispatcher”
Aborted visit Not mentioned “Site closed or contact absent after 30 minutes on site counts as an aborted visit”
Branding “Represent the client professionally” “Introduce yourself as an engineer from [partner brand]; no third-party branding”

Worked example: one break-fix job under a well-written SOW

A UK MSP supports a chain of offices for an end customer and has a SOW with us covering break-fix within 4 hours during business hours.

  1. Request: at 10:15 the MSP’s service desk raises a work order for a failed access switch in a Reading office, quoting service code BF-4H. Because the SOW already covers site access, parts and reporting, the ticket only needs the address, contact, fault and part tracking number.
  2. Brief: our London service desk confirms the job within 30 minutes, assigns a vetted engineer and sends the site the engineer’s name for the visitor list, as the SOW requires.
  3. On site: the engineer arrives inside the window, collects the replacement switch from reception, swaps it and stays on a call while the MSP’s network team pushes the configuration.
  4. Report: before leaving, the engineer uploads before and after photos, both serial numbers and the sign-off name. The report reaches the MSP in its own format, ready to forward to the customer, and the faulty unit goes back with the courier label supplied.

Nothing in that job needed a back-and-forth to clarify scope. That is the test of a good SOW. You can see more jobs like this in our recent field service projects.

Common gaps in a statement of work for field services

  • No definition of “on site”. Is it arrival at the car park, at reception or at the rack? Large campuses and data centres can add twenty minutes between them.
  • Service levels with no pause rules. If the customer contact is not there, the clock should stop, and the SOW should say so.
  • Silence on aborted visits. They will happen. Agree how they are charged and reported before the first one.
  • One SOW stretched across countries. Working hours, public holidays, language on site and access rules vary. Add a short country annex rather than rewriting the whole document.

How to roll a SOW out across countries

For multi-site roll-outs and international support, keep one core SOW and attach a one-page annex per country. The annex covers local working hours, public holidays, any language requirement, lead times for data centre access and any country-specific safety rules. If most of your sites are in Britain, our UK field engineers page covers how we staff UK-wide work.

What we bring to the SOW conversation

We coordinate jobs from London through a 24/7 service desk that responds in under 30 minutes all year, with a network of more than 2,000 field engineers and support for 75+ manufacturers. Across our partner work, SLA attainment runs at 99.99% for next business day, 98% for 24-hour and 94% for 4-hour visits. Share a draft SOW and we will flag anything likely to cause friction on site before the first dispatch.

FAQs

What is a statement of work for field services?

It is the document that sets out the services, scope, service levels, site rules, reporting and change process for an onsite IT programme. It sits under the master agreement and above individual work orders.

Should service levels sit in the SOW or the contract?

Put the definitions and measurement rules in the SOW, because they are operational and may differ by programme or country. The contract can refer to them and set any service credits.

How long should a field services SOW be?

Long enough to answer every question a dispatcher or engineer would otherwise ask. For most programmes that is six to twelve pages plus a site list and country annexes.

Can a partner work to our existing SOW template?

Yes. We are happy to work to a partner’s template. We will point out gaps such as missing pause rules or aborted visit terms, but the document stays yours.

Send us your draft SOW

Share your scope, locations and service levels, and we will come back with questions, coverage and rates for engineers on site under your brand.

Request the partner rate cardEmail us

Leave A Comment