Field service runbook: the steps, checks and evidence a job requires
Why it matters
When work passes through partners and subcontractors, every engineer brings their own habits. A runbook replaces habit with a shared standard: the same steps, the same checks, the same evidence, whoever does the job. It is the practical bridge between the customer’s acceptance criteria and what happens on site.
What a good runbook contains
- Preparation: access arrangements, permits, parts and prerequisites to confirm before travelling.
- Steps: the work in order, short and specific.
- Checks: the tests and inspections that show each step was done correctly.
- Required evidence: for each check, what to capture: a photo of a label, a test result, a reading, a serial number.
- Exceptions: what to record if access fails or a prerequisite is missing, and who to tell.
- Completion: the sign-off required and what triggers review.
Runbook vs method of procedure
In telecoms, a method of procedure (MOP) usually documents a specific change: the steps, timings, rollback and approvals for one piece of work. A field service runbook is reusable across every job of a type, and it is written around acceptance: each step points to the evidence that will be reviewed. Many operations use both, with the runbook referencing the MOP for complex changes.
How to build one
- Start from the customer’s acceptance criteria for the job type.
- List the checks that demonstrate each criterion.
- Decide the evidence for each check, and drop anything that does not answer a question.
- Add preparation steps that prevent the most common revisits.
- Test it with experienced engineers and revise after the first jobs.
How FortyFive does it
Runbooks in FortyFive are attached to job types. Engineers see them before accepting a job and follow them on their phone on site, capturing evidence against each check into the digital site report. See how a job moves through FortyFive.
Last updated · FortyFive
Frequently asked questions
Is a runbook the same as a method of procedure (MOP)?
They overlap. In telecoms a method of procedure often describes a specific change step by step, including rollback. A field service runbook is reusable for a type of job and ties each step to the evidence needed for acceptance.
Who writes the runbook?
The business accountable to the customer, usually from the customer's acceptance criteria and its own experience of what goes wrong. Experienced engineers should review it.
How detailed should it be?
Detailed enough that the evidence answers the acceptance criteria, short enough to follow on a phone on site. Each check should have a reason.
Do runbooks slow engineers down?
A good one speeds them up, because they know what is required before they arrive and do not need to come back for a missed check.
Related terms
Acceptance criteria for field work
Acceptance criteria for field work are the specific, agreed conditions a job must meet to be accepted as complete, and the evidence that will show each one has been met.
Digital site report
A digital site report is the record of a field visit captured on a phone or tablet while the work happens: what was done against each required check, with photos, test results, readings, time, location and sign-off.
Proof of delivery in field services
Proof of delivery in field services is the record that shows a job was completed to the agreed requirement: what was done, where, when and by whom, measured against which acceptance criteria, and who accepted it.
See how FortyFive proves the work.
Book a 30-minute walkthrough and bring a job you have delivered recently.
Book a walkthrough