“In progress” can mean almost anything. The technician may be driving, standing at the property, preparing the work area, or already performing the service. When one broad label covers the entire visit, dispatchers and customers have to guess what is actually happening.
Exoserva separates the field visit into four practical actions: on the way, arrived, work started, and completed.
Each action answers a different question
These stages are useful because they describe different operational facts.
- On the way tells dispatch that travel has begun.
- Arrived records that the technician reached the service location.
- Work started separates physical presence from the beginning of the service.
- Completed records that the technician is closing the field workflow after reviewing the required details.
A technician can be onsite without having started work. Access may be blocked, the customer may be explaining the problem, or the team may need approval for a changed scope. Keeping arrival separate from work started preserves that distinction.
A synthetic example
A technician leaves for a morning repair and marks the visit as on the way. At the property, the technician records arrival. The customer then asks the technician to wait while access to a utility room is arranged. The visit is not yet work in progress simply because the truck is parked outside.
Once access is available and the service begins, the technician uses the work-started action. After the agreed work and required review are finished, the visit can move to completed.
The timeline now reflects what actually happened. Dispatch can see the delay between arrival and work start without inventing a travel problem or assuming the service took longer than it did.
Notifications should follow a real event
Customer messages are most useful when they are tied to a meaningful, confirmed stage. An arrival action can support an arrival notification when that communication is configured. Internal corrections or unrelated status changes should not automatically create a customer message.
This keeps communication intentional. The system can help the team notify at the right moment while the technician remains responsible for choosing the correct action.
Completion deserves its own review
“Completed” should not be a shortcut for “I am leaving.” Depending on the company’s workflow, the technician may need to review notes, photos, materials, signatures, payment state, or remaining work before closing the visit.
Separating the final action makes it easier to ask whether the record is ready. If a return visit is required or the scope is unfinished, the team should preserve that next step instead of using a completed label that hides open work.
Better status for dispatch and reporting
Clear stages give the office a better operational picture. Dispatch can distinguish travel from onsite delay. Managers can review visit flow without treating every minute as active labor. Customer communication can be connected to the event that actually matters.
The design is intentionally simple: four field actions that describe observable progress, not one vague state that everyone interprets differently.
Available actions, notification behavior, and completion requirements depend on workspace settings, user permissions, and company workflow. Technicians should record the stage that has actually occurred.
Which visit stage is hardest for your office to understand in real time?
— The Exoserva Team