Writing Down What You Were Actually Asked to Do
Most scope disputes on field jobs do not start with bad intent. They start with a sentence in a work order that two people read differently, or with a verbal request made at the door that never reached paper. A technician who can point to a clear, dated statement of scope is in a much stronger position than one reconstructing events from memory. This article walks through a method for capturing scope before, during, and after a visit, without assuming any particular contract terms or outcomes.
Start With the Request, Not the Assumption
Before you touch equipment, write down the request in the words it was given to you. Record who made it, through what channel, and when. If the work order says 'check the uplink,' do not translate that into 'replace the uplink module' in your notes. Quote the original and then add your interpretation separately, labeled as interpretation.
This separation matters later. When someone asks what you were asked to do, the quoted text answers the question, and your reading of it becomes a clearly marked secondary note rather than something that looks like the original instruction.
Turn Vague Language Into Answerable Questions
Vague phrases such as 'clean up the closet,' 'make it work,' or 'fix the intermittent issue' leave room for disagreement. Before starting, convert each one into a question you could answer yes or no at the end. Does 'make it work' mean restoring the previously reported service level, meeting a specification in the ticket, or simply leaving the site in a stable state? Asking the dispatcher or site contact and writing down the answer is ordinary professional practice.
If you cannot get an answer before the visit, note the ambiguity in your initial record and state what you plan to do about it. That single line can save a long argument later.
Record Boundaries as Clearly as Tasks
A scope statement describes what is included and also what is not. Write down items you were asked to leave alone, areas of the site you did not enter, equipment you saw but did not service, and tasks you flagged for a separate visit. Boundaries are often more useful in a dispute than task lists, because they show where your responsibility stopped.
Keep these notes factual. 'Customer asked me not to open the rear panel; I did not' is more defensible than a general statement that you only worked on certain things.
A Simple Comparison: Before, During, and After
Before the visit, your record should contain the original request, the answers to your clarifying questions, the access arrangements, and any stated constraints such as working hours or restricted areas. During the visit, note deviations from the plan as they happen, with times, the reason, and who approved the change if anyone did. After the visit, record what was completed, what was partially completed, what was not attempted, and what follow-up the site or dispatcher needs to schedule.
The three stages build on each other. A thin pre-visit record makes the during-visit notes harder to interpret, and both together determine how persuasive the closeout is.
A Practical Checklist for Your Scope Record
Keep this list short enough to use on every job. Confirm that the original request is quoted verbatim with its source and timestamp. Confirm that every vague term has either a written clarification or a noted assumption. Confirm that exclusions and out-of-scope items are listed. Confirm that any change to the plan during the visit has a time, a reason, and an approver where possible. Confirm that the completed, partial, and not-attempted items are each stated separately. Confirm that follow-up needs are written with enough detail that someone else could schedule them.
Store the record in the same place for every job so you can find it later. A scope record is only useful if it can be retrieved when a question arises months afterward.
Questions to Ask Whoever Hands You the Work
Ask what outcome the requester expects to see when you leave. Ask which systems or areas are off limits. Ask who can approve a change to the plan if you discover something unexpected on site. Ask how the closeout should be delivered and to whom. These questions take a minute to ask and produce the information that most scope disagreements lack.
Good documentation is a habit rather than a single event. Build the routine, keep it consistent, and treat your own written record as the primary account of what you were asked to do and what you did.