A field update has two audiences: the person reading it today and the teammate returning to the job later. A short note can serve both when it explains what happened and what should happen next.
What changed?
Describe the progress made during this visit. Be specific enough that someone can understand the update without calling the person who wrote it.
What remains open?
List unresolved questions, missing information, or work that needs another visit. Keep uncertainty visible rather than letting it disappear inside a general “in progress” status.
What provides context?
Attach relevant photos or a location pin when they help someone understand the note. Explain what each attachment shows. A photo is more useful when the next person knows why it was taken.
What is the next action?
Name the follow-up and who needs to take it. For example: “Office to confirm the next access date with the customer before scheduling the return visit.”
Put it together.
Here is a simple operational example:
Today’s visit is complete. Access to the rear portion was unavailable. See the attached entrance photo. The office needs to confirm access before assigning another visit.
The note does not need to be long. It needs to leave the job easier to pick up.
Finally, check that the update reached the shared record. If it was saved offline, leave the app open when service returns and review the pending upload status. A useful note still needs to reach the people who rely on it.