Write for the person opening the record tomorrow
A note that says 'all done, office to call' can make sense to the person who wrote it. A colleague opening the job tomorrow still needs to know what was done, which request remains open, and who is calling about it. Useful job notes preserve those details while the visit is fresh.
Microsoft's Field Service documentation describes notes linked to a booking as part of its work history. Its work-order finalization guidance calls for reviewing completed tasks, labor, notes, and resolution comments before closure. The practical writing goal is a record another person can check and continue from.
The layout below is a suggested writing template, not a list of software fields or built-in features. Adapt it to your team's record process. Use the relevant approved service instructions for technical work, and record what actually happened.
References: Microsoft Learn: recording work and building its history · Microsoft Learn: review notes and completed work before closure
Keep reported concerns, observations, and actions separate
Start with the source of each statement. 'Customer reports an intermittent interruption' records what someone told you. It does not establish a cause or show that the technician observed the same event. A recommendation, a completed action, and a result are also different entries.
Use ordinary labels instead of blending everything into one paragraph. Include the limits of the visit: an item not inspected, a check not completed, or information still missing. A limitation helps the next person understand what the record supports. Avoid broad conclusions such as 'everything fine' when the note covers only a defined task.
- Reported: who described the concern, and what they said.
- Observed: what the technician actually saw or established during this visit, with relevant conditions and limits.
- Performed: the work actually completed and its task or scope reference.
- Result and next action: what is recorded as the outcome, what remains open, and who owns it.
Copy this service job notes template
Use one copy for each visit and connect it to the correct job. Fill a relevant gap with 'not checked,' 'unknown,' or 'not applicable,' with an explanation where needed. Empty space should not leave a colleague guessing whether something was considered.
- Visit reference: _____. Date and relevant times: _____. Technician or author: _____.
- Job and location: _____. Equipment or service item identifier, when relevant: _____.
- Agreed purpose and scope reference: _____. Additional customer request, if any: _____.
- Customer-reported concern and source: _____.
- Observations and limits: _____. What was not checked or could not be established? _____.
- Work performed: _____. Relevant task/checklist reference: _____. Materials or quantities used, if applicable: _____.
- Observed result and supporting task record: _____. What remains unresolved? _____.
- Customer discussion: _____. Which proposal or change was accepted, declined, or left unconfirmed? _____.
- Next action: _____. Named owner: _____. Due time or next review point: _____. Information needed before another visit: _____.
Before and after: one fictional visit
This example is fictional. Casey attends a planned service visit for Unit A in a small office. During the visit, the customer asks about Unit B, which is outside the agreed work. The technical tasks belong in the team's approved task record; this example shows how the surrounding note can preserve scope and follow-up.
Before: 'All done. Second one needs looking at. Office to call.'
After:
- Visit: DEMO-042, October 26, 2026, 10:00-10:45 a.m. local time. Author: Casey. Location: fictional training office.
- Scope: planned service of Unit A, identified as the front-room unit, using agreed checklist DEMO-C1.
- Reported: customer asked whether Unit B, the rear-room unit, could also be reviewed. This was an additional request.
- Work performed: agreed checklist tasks for Unit A completed; individual tasks and results recorded under DEMO-C1. No work performed on Unit B.
- Result and limits: the Unit A visit scope is complete. Unit B was not inspected, so no finding or repair outcome is recorded for it.
- Customer discussion: Casey explained that the office would review the Unit B request. No return appointment was confirmed.
- Next action: Morgan in the office will confirm the requested Unit B visit purpose with the customer by October 27 at 11 a.m. local time, then check scheduling options.
- Next technician needs: the confirmed purpose and scope of any Unit B booking, plus the relevant approved service instructions.
Give every open item a usable next action
Read the unfinished part of the note as a small assignment. 'Office to call' leaves both the person and the purpose unresolved. 'Morgan to confirm Unit B visit purpose with the customer by Tuesday at 11 a.m.' gives someone a task they can accept and report back on.
Distinguish the action from its eventual outcome. A request for a quote is not an approved quote; a proposed return visit is not a confirmed appointment. If the owner cannot complete the action by the stated time, update the record with the current dependency and the next review point. Keep the customer commitment consistent with that update.
References: For customer timing changes: arrival-window message templates
Make references and handoffs easy to follow
Use an identifiable reference when details live in another approved record: a job number, checklist name and version, or estimate reference. 'See previous notes' is hard to follow when there are several visits. State which record matters and why. Avoid copying an earlier conclusion into today's note as though it were checked again.
The next technician needs the visit purpose, the work already completed, and the unresolved question. The office needs the current outcome, any customer decision, and its next action. Use the same record to support both readers, keeping customer information relevant to the job and within your team's approved information-handling process.
References: Complete the wider customer and office handoff
Use a short readback before saving
Ask a colleague to read a sample note without your explanation. Can they identify the visit, explain the result, and name the next owner? If they have to ask 'which one?' or 'who is doing that?', revise the sentence that left the gap.
Before adopting the template, try it on one visit and review what your team still needs. Keep useful detail, remove repetition, and make the next action easy to find.
- The job, location, date, and relevant item match the visit.
- Reported concerns and technician findings are clearly attributed.
- Completed work, results, and limits can be traced to the relevant task record.
- Unfinished items have a next action and a named owner.
- The customer discussion and current booking or follow-up state agree.