Documenting What You Did on Site: Scope Notes for Independent Field Technicians

Field Guard Technician Alliance is a 1MatrixTech project for independent field technicians, and its educational material focuses on the everyday practices that help self-employed technicians prepare for, document, and evaluate their own work. This article takes one narrow angle: how to keep a scope record that matches what happened on site. Scope documentation is not a legal instrument and this is not legal advice. It is a working habit that makes your own records easier to read, easier to reconcile, and harder to misremember weeks later.
Why scope notes matter more than memory
Most disputes about field work do not start with bad intent. They start with two people remembering the same visit differently. A customer remembers that you were asked to replace a unit. You remember that you were asked to inspect it and report. Neither memory is fully reliable after a few days, and neither is useful if it was never written down in the moment.
A scope note is a short written statement, made at the start of the job or as soon as you arrive, that describes what you were asked to do. It is different from a closeout record, which describes what you actually did. Keeping both lets you compare them. The gap between the two is where most confusion lives.
Building the scope note at intake
Before you touch equipment, write down the request in your own words. Include the date, time, location or site identifier, the name or role of the person who made the request, and the exact task as you understand it. Avoid paraphrasing so loosely that the meaning shifts. If the work order says restore service, write that phrase, then add what you think it means in practice.
Next, write what is explicitly outside the request. Examples include equipment you were not asked to open, areas of a building you were not asked to enter, software you were not asked to configure, or follow-up visits you did not agree to. Exclusions are often more valuable than inclusions because they prevent the quiet expansion of a job into work nobody priced or planned.
Finally, note the open questions. Ask whether the site has a single point of contact, whether access is confirmed, whether any materials are supplied by the client, and who decides if the scope changes mid-visit. Write the answers as they are given, with the time you received them.
A checklist for scope documentation
Use this plain checklist at intake and again at the end of the visit. At intake: record the date and time; record the requester's name and role; write the requested task in your own words; list explicit exclusions; list open questions and any answers received; note any site conditions that differ from what you expected. At closeout: record what was completed and how you verified it; record anything requested that you did not do, with the reason; record any change to scope agreed during the visit and who agreed to it; record follow-up items and who owns them.
Keep the checklist in one place so you can compare it across jobs. After a dozen visits, patterns appear. You may notice that a particular client keeps adding tasks without noting them, or that a certain type of site always carries surprise access problems. Those patterns are worth knowing before you accept the next job.
Comparing scope records with closeout records
A scope note and a closeout record answer different questions. The scope note answers what was agreed. The closeout record answers what happened. When they match, the job is simple to explain. When they diverge, the divergence itself is information you should record rather than smooth over.
Read them side by side. If the scope note says replace one module and the closeout says replace two, the closeout should explain why the second replacement happened, who approved it, and whether it was in writing. If the scope note lists an exclusion that the closeout appears to contradict, note that discrepancy plainly. Do not revise the original scope note after the fact. Add dated entries instead, so the sequence of events stays visible.
Questions to ask yourself before you sign off
Before you leave a site, ask whether someone reading only your notes could tell what you were asked to do, what you did, and what remains. Ask whether any sentence in your record depends on a memory you have not written down. Ask whether you have stated your verification method, such as a test you ran or a reading you took, rather than only saying the work is done.
Scope documentation is a practice you choose and maintain yourself. It supports your own review of your work and gives you a clearer record to consult when you evaluate whether a job was worth taking. Keep the habit consistent, and it will serve you whatever kind of field work you accept.