Field service tracking: a live technician map and proof for every job

A service team lives in tickets, while the dispatcher works blind: where the technicians are, who is closest to a new job, whether the engineer has left yet — all known from scraps of phone calls. Taskloc gives the dispatcher a live map and a fact for every ticket: the on-site check-in, the visit time, the route.

A dispatcher's day

• A ticket comes in, and it's unclear whom to send: technician locations are known only from calls.
• There's nothing to prove SLA response time with: the client asks, and the answer is "we were quick".
• A night emergency call-out never made it into the timesheet: the shift was forgotten, the time lost.
• The ticket is closed in the system, but whether the engineer was on site is unknown.
• Preventive maintenance is marked "done" without any proof of the visit.

How field service visit tracking works

1. A service ticket is a task in your tracker, and dispatching stays there. Taskloc doesn't move anything.
2. The technician finds the ticket by search — by number, title or project, even offline — starts a session on it and appears on the team map in the web dashboard.
3. The dispatcher sees who is out on a job and who is free, and assigns the next ticket based on facts, not guesswork.
4. A check-in on site records the visit; when the job is done, the hours for the ticket go to the tracker — including that night call-out.

What the dispatcher and service manager get

• A technician map right now: not an after-the-fact report but a tool at the moment of assigning a ticket.
• Proof of the visit for every ticket: location, geofence, time, route. That's what you answer an SLA question with.
• Emergency and night call-outs are logged automatically: the session records time as it happens, not from memory the next morning.
• Preventive maintenance closed with a check-in: the visit happened, here's the location and time.
• Reports by technician, visits and mileage in the web dashboard.

The value here is shifted compared to ordinary time tracking. In field service, decisions are made when a ticket arrives, not when the month is reviewed: the live map answers "whom do we send" in seconds, while a report answers "why did it go this way" a week later. Taskloc covers both, but the first is why the dispatcher opens the dashboard every day.

What Taskloc doesn't do

Honest boundaries:

• Dispatching and the tickets themselves stay in your tracker. Taskloc doesn't replace your ticketing system or build escalation schedules — it adds the fact of the visit to the tickets.
• There's no automatic SLA calculation. The check-in gives a confirmed visit time per ticket; comparing it with your SLA stays your analytics.
• The app is Android-only; the dashboard runs in a browser.
• Routes, reports and the map need the internet. In the field, tasks and the session work offline.

Technician privacy

The technician starts the session for the ticket. While it runs, location and route are recorded. Stop the shift and you disappear from the team map: no location is collected outside a session. For night call-outs this suits both sides — the time is tracked, and nothing is recorded after the shift.

Rolling it out properly

Introduce GPS visit tracking the way you introduce any workplace policy: in writing, under your internal rules and local employment law, with technicians informed before it starts. For a service team it's a routine step: the call-out procedure is already documented anyway.

Your company remains the data controller: you decide who is tracked, what is collected and who sees it; Taskloc is the tool you do it with. The technical boundary is strict: outside a session started by the technician no location is collected, and no setting can change that.

Which trackers it works with

The one where your tickets already live. There are 19 connectors: Redmine, Jira Cloud, Asana, Trello, ClickUp, monday.com, Bitrix24, OpenProject and more — full list. Time entries for tickets go back to the same tracker if it accepts them; where it doesn't, the hours stay in Taskloc — what each tracker can do. Connector pages: Redmine, Yandex Tracker, Bitrix24, Kaiten, OpenProject.

Questions from dispatchers

Does the dispatcher see technicians after their shift?

No. The map shows only active sessions. Once the shift stops, the technician is gone from the map and no location is recorded.

How do we prove SLA to a client?

With the check-in on the ticket: location, geofence, visit time, route. It's recorded automatically, not reported from memory.

How does a night emergency call-out get logged?

Just like a daytime one: the technician starts a session on the ticket, time is recorded automatically and goes to the tracker when the session stops. Nothing to remember in the morning.

Do tickets have to be moved into Taskloc?

No. Tickets stay in your tracker; Taskloc works on top of it through the API and sends time entries back there.

The engineer closed the ticket but there's no check-in — is that a violation?

It's a reason to ask, not a conclusion. The engineer may not have started a session, may have worked with the phone off, or may have solved it over the phone without a visit. A check-in records the fact of a visit; its absence means exactly that the visit isn't confirmed.

How many technicians can the map show at once?

Everyone with a session running right now. The team map and reports are part of the Team plan; on Free the dashboard works for one seat, with no live team map.

Try it with one crew

Connect your tracker, give the app to two or three technicians and look at the map on your next working day. Free works forever for one seat; the Team trial gives 14 days and 3 seats, once per account. No card is needed at sign-up and nothing is charged when the trial ends — the account moves to Free.

Team payments are currently accepted only with Mir cards issued in Russia and the CIS and via SBP. If you are elsewhere, contact us and we will look at your case — we can't promise a particular payment method in advance.