Aspro.Cloud time tracking with GPS: hours logged from the field

In Aspro.Cloud, tasks, projects and employees live in one portal. When work happens at a customer's site, the hours get typed into the task later, from memory and in one lump — and the portal knows nothing about where the employee was or how long the trip took.

Taskloc is an Android app that sits on top of your Aspro.Cloud portal. The employee picks a task, starts a GPS session, and the app records time, route and the on-site visit. When the session stops, the hours go to the portal's time log as a separate entry for the selected employee. Your tasks stay in Aspro.Cloud.

Why field hours in the portal are hard to trust

• An employee spends half a day at the client, and the hours appear in the task in the evening, as one number.
• Travel to the site and work on site end up in the same entry.
• Nobody opens the portal in a phone browser just to log forty minutes.
• When a client questions five hours in a report, there is nothing to show except someone's word.

How it works

1. The portal administrator issues an API key: System settings → API settings, and opens the Tasks, Time tracking, Custom fields, Projects and Org structure modules to it.
2. Connect. In the app: "Add tracker" → Aspro.Cloud → portal address (your-portal.aspro.cloud) and the API key.
3. Pick the employee the hours are written to, in the integration settings.
4. Start a session on a task. Time and route are written automatically; a check-in records the visit.
5. Stop, and the entry is there. The hours go to the task's time log; a status change goes to the same task.

The entry is a real object in the portal's time log with its own ID, not text in the task description.

What the Aspro.Cloud connector supports

What managers get

• Hours recorded while the work was happening, not typed in from memory in the evening.
• Time on site and travel time — separately, for every task.
• The route of each trip on a map, mileage as a number.
• A check-in as proof of the visit: location, geofence, route.
• A live team map and per-employee reports in the web dashboard, which runs in the browser.

Limitations of the Aspro.Cloud connector

• The portal receives the duration, not the time of day. Aspro.Cloud stores only the number of hours in a time entry — no start and no end: "5 hours", not "from 9 to 14". The full picture of the shift — when it started, when it ended, where the employee was — stays in Taskloc and is visible in reports.
• Without a selected employee the hours belong to nobody. The API key is issued by an administrator and does not write hours to anyone by itself. If no employee is chosen in the integration settings, the hours are written to nobody — the app warns you about it.
• Connecting is an administrator scenario. An employee without administrator rights will not see the API key section. This is how Aspro.Cloud works, not a limitation of the app.
• If there is nowhere to write time — the time module isn't open to the key or isn't available on the portal — the session closes normally and the hours stay in Taskloc. The app shows the portal's refusal text.
• No comments. Task discussions live in a separate portal module, which the app does not use.
• Changes come without an author. The portal attributes changes made with an API key to nobody. Hours are the exception: they go to the selected employee.
• No attachments or labels; no idle auto-pause — pauses are set in Taskloc only.

Setup guide: connecting Aspro.Cloud.

Privacy

The employee starts the GPS session. Outside an active session the app does not collect location at all: stop the session and you disappear from the team map. Who sees what is set by team policies.

The API key stays on the device, and the app reads and writes tasks directly in the portal. The Taskloc server never receives it.

Questions from Aspro.Cloud admins

Who issues the API key?

The portal administrator: System settings → API settings. That is also where they choose which modules the key can access. If a module is missing, the app says so — no need to reconnect after it is opened.

Why does the task say "5 hours" and not "from 9 to 14"?

The portal accepts only the duration of a time entry. The session's start and end, route and visit are kept in Taskloc and shown in the web dashboard reports.

Who are the hours written to?

To the employee selected in the integration settings. If none is selected, the hours are written to nobody, and the app warns you in advance.

Aspro.Cloud has its own timer — why Taskloc?

The portal timer counts time at a computer. Taskloc adds what the portal doesn't have: mobile start and stop per task, work with no signal, a GPS route, mileage and an on-site check-in.

Is there an iPhone app?

No. The field app is Android-only; the manager's web dashboard opens in any browser, including on a phone.

Who it's for

Companies that run tasks in Aspro.Cloud and work at the client's site: service and maintenance, installation, implementation, field specialists. If visits are the core of the job and the tracker is secondary, see field employee tracking and field service visit tracking.

Try it on your portal

Connect Aspro.Cloud, install the app on one phone and take one task from the start of a session to the time entry appearing in the portal. Free works forever for one seat; the Team trial gives 14 days and 3 seats, once per account, with no card required. When the trial ends, the account moves to Free — nothing is charged.

Team is paid with Mir cards issued in Russia and the CIS and via SBP, or — with a card issued by a foreign bank — by a one-off Robokassa invoice: contact us and we will send a payment link.