Skip to content
trackinia

FIELD OPERATIONS

When the plan goes to the field, the process continues.

Send published routes to your drivers, record how tasks are carried out and follow the operation’s progress from the central management screen.

CHALLENGES

What gets lost between the plan and the field?

  1. 1

    A gap between planning and the field

    Operations teams want to know how the plans they create play out on the ground.

  2. 2

    Recording how tasks are carried out

    It matters that completed and incomplete tasks are recorded.

  3. 3

    Operations that do not use a driver app

    Not every business wants its drivers to use a separate mobile app.

HOW TRACKINIA HELPS

How does Trackinia carry the process from planning to the field?

  • Publishing approved routes

    When you publish the plan, routes appear in the driver app assigned to the right drivers.

  • Stop list and map

    Drivers see their stops in order, as a list and on a map.

  • Task status updates

    Drivers start and complete tasks, and enter a reason when a task cannot be completed. Statuses show up on the management screen.

  • Navigation

    A stop’s address opens in the device’s map app for directions.

  • Records are kept when there is no connection

    Reported statuses are stored on the device and sent to the server when a connection is available.

  • For teams that do not use the app

    The operations team can record task realization from the management panel itself.

IN DETAIL

Why plan and execution are separate records

The planned timeline describes a route’s intended timing; it does not show what happened in the field. An execution record captures what actually happened, with the timing that is known. Keeping them apart is a prerequisite for judging how well a plan held up.

A location sample is an observation of a device’s position at a point in time; it is not proof that an activity was completed. Trackinia therefore keeps location records and task statuses separate.

How does this work in Trackinia?

  1. 1

    Task statuses

    A driver starts a task, completes it or reports it as not completed with a reason. Statuses appear on the management screen.

  2. 2

    Recording from the office

    Even without the driver app, an authorized operator can enter execution records from the panel.

  3. 3

    Without a connection

    Statuses and location samples are stored on the device and sent when a connection returns. The operations team sees them after delivery.

  4. 4

    Work session

    A driver’s working period on a route is recorded as a session. A gap in location capture does not by itself end it.

  5. 5

    Costs and measurements

    The route page compares planned and actual costs; entering measurements and expenses depends on permissions.

Scope and limits

  • There is no real-time live vehicle tracking; location samples appear after a connection is restored.
  • There is no electronic signature, delivery photo or automatic customer notification.
  • Cold-chain monitoring and ERP connections are outside this solution’s scope.

EXAMPLE SCENARIO

A driver’s day, the operations team’s view

A driver goes through the stops of a published route in order. The operations team follows the stop statuses on the management screen. Teams that do not use the app can enter the same records in the panel.

Illustrative example: this scenario shows how the product can be used. It is not a customer case or a measured result.

  1. 1

    The driver opens the stop list and starts navigation to the first stop.

  2. 2

    When the delivery is done, the driver marks the task as completed.

  3. 3

    If a delivery cannot be made at a stop, the driver reports it with a reason.

  4. 4

    The operations team reviews the current statuses on the management screen.

Frequently asked questions

Is the driver app required?

No. Teams that do not use the app can record task realization from the management panel.

How is task realization recorded?

In the driver app a task is started, completed, or reported as not completed with a reason. The same records can also be entered from the panel.

What data can be kept when the internet connection drops?

Task statuses reported by the driver and location records are stored on the device and sent when a connection is available.

Is there live vehicle tracking?

No. Location samples are collected on the device and delivered when a connection is available; this is not live monitoring. Progress is followed through task records.

What happens if the driver changes during a route?

On an active route the driver handover is recorded; each driver’s period of participation stays in the route history and the new driver is reserved only for the remaining interval.

Bring planning and field operations together.

Explore the driver app