Direct answer
Field service job tracking means knowing which job is where and who has it. When the answer lives in phone calls, messages and a shared spreadsheet, the office cannot say what has been done and the technician cannot see what is next. A job tracking system gives each job one record that moves through a defined lifecycle and is updated from the field. LATYNEX builds this as a scoped web application around how your team works. It is not a dispatch optimiser and it does not track vehicle location; it tracks jobs, people and status.
Job lifecycle
Define the stages once and use them everywhere. A common shape is:
- Requested or booked
- Assigned to a person or crew
- In progress on site
- Waiting, for example for parts or access, with a reason
- Completed, then confirmed
Assignment
A job has one accountable person or crew at a time. Assignment is made by whoever plans the work, using the information they have: skills, availability, the customer's wishes. The system records the choice and shows each technician their own list. It does not choose the assignment for you or optimise routes; that judgement stays with your planner.
On-site updates, parts and notes
The technician needs a simple screen on a phone: update the status, add a note, record what was used. Keep required fields minimal, because a form that is slow on site will not be filled in. Parts used can be logged against the job for later reference. Connecting to a stock system is a scoping decision; see internal stock request handling for the internal side.
Photos and sign-off as scope choices
Photos of the work and a customer sign-off are useful for some businesses and unnecessary for others. We treat them as optional parts of the scope, agreed at the start, rather than defaults. If included, they are stored on the job record. A sign-off in the system records that a person confirmed the work; we make no claim about its legal weight.
Customer updates
Customers ask the same thing: has someone been assigned and when will they come. Job status can feed a message or a simple customer view so that the office answers fewer status calls. What is shared, and how, is your decision. The trigger is the status change on the record.
Reporting
Because every job carries its stage and timestamps, the office can see open jobs by person, jobs waiting and why, and completed work by period. That is the same idea as the age and blocked views in operations bottleneck dashboard. The reports reflect what people enter, so the discipline of updating on site matters more than the tool.
Questions
Does it optimise routes or track vehicles?+
No. It tracks jobs, assignment and status. Route planning and location tracking are outside this scope.
Can technicians use it on a phone?+
Yes. The field screen is designed for a phone, with a small number of required fields so that updating on site stays quick.
Are photos and sign-off included?+
They are optional parts of the scope, agreed at the start. If included, they are stored on the job record.
Can customers see job status?+
It can be arranged, either as messages or a simple view. What is shared with customers is your decision.