Tools for the office and the colleague doing the visit
An assignment is not just a row with a name beside it. It connects a person to an approved instruction at a particular place and time. If the location changes, or a report remains on a phone, the office needs to know which part of that relationship is current.
We develop operational tools that make those distinctions usable in ordinary work.
Keep amendments separate from instructions
Suppose a customer changes the work location after a colleague has received an assignment. The correction may affect coverage, preparation or the quotation. The organization must decide who reassesses it and what the assigned person is allowed to do in the meantime.
The tool can retain the earlier instruction, record the proposed amendment and identify the decision still needed. Accepting an amendment should create an understandable new instruction rather than silently overwriting the evidence of what was previously authorized.
The location-change investigation develops this case. Its purpose is to make a correction reviewable across office and field views.
Give device drafts an honest status
A note stored on a device is not yet a report the office can read. If local drafts are required, we scope how they survive ordinary interruptions, how the person sees pending work and how a later submission meets changes made elsewhere.
Actual devices, browsers and information-handling decisions determine that design. Sign-out, reassignment and an old screen reopened after a long interruption can matter as much as reconnecting. Offline capability should be established through the agreed tests, not inferred from a page staying visible.
A first release may deliberately support only online submission with a clear interruption message. Where retained drafts are essential, the storage and recovery behavior become explicit deliverables.
Review the event behind a status
The office may need to distinguish a visit started, a visit stopped, a report submitted and a report approved. These events have different owners. The field colleague should not be forced to claim completion merely to save a note.
Acceptance uses populated fictional jobs. Reviewers amend one after assignment, interrupt a submission and let a substitute colleague continue through the approved process. A second unrelated job checks that a correction does not change the wrong instruction. Removed access is tested through a saved link, not only a hidden menu.
The scope identifies which events are retained, which actions are permitted for each role and which record supports a customer update.
Make the first version operable
Bring the current assignment method, the information a field colleague needs and one difficult amendment. We will separate necessary coordination from features that can wait, then define private review and handover around that boundary.
Documentation covers daily use, administration, known device limits and support arrangements. The organization retains authority over service decisions and account ownership.
