Site Vehicle Activity Report

It combines data from multiple tracking sources to deliver detailed insights into site activity, including visit duration, media captured, material usage, and associated notes.

This report is commonly used for:

For each site visit, the report includes:

A visit is fundamentally defined as:

Vehicle + Site + Time Period

The system can combine data from multiple devices installed in the same vehicle.

Examples:

When both devices are installed:

This provides a complete operational picture for each visit.

Visit duration is calculated using advanced logic rather than simply subtracting start time from end time.

This is because:

As a result:

The reported time on site may be less than the difference between start and end timestamps.

This behavior is intentional and improves accuracy.

Because GPS and site boundaries are not always perfectly accurate, the system uses configurable thresholds to prevent false visits.

Grace minutes determine whether a visit continues or a new visit is created when a vehicle temporarily leaves a site.

Example:

Default:

If a vehicle leaves a site and there is a gap longer than:

15 minutes

A new visit will automatically be created.

This threshold is fixed and cannot currently be changed.

Services can be linked to visits in two ways.

Each vehicle can have a default service assigned.

This service will automatically attach to:

Every visit made by that vehicle.

This is useful for:

The system can automatically associate services using audio notes recorded on site.

Process:

This feature requires:

This is considered a Pro Feature and is not widely used by all organizations.

Each visit may include:

Notes are permanently saved with the visit record and can be used for documentation or dispute resolution.

Visits can be converted into jobs for operational and invoicing workflows.

This is particularly valuable because:

Many customers use jobs to generate invoices.

Automations can be configured to convert visits into jobs automatically if required fields exist, such as:

This capability is considered a Pro Feature.

When a visit is converted to a job:

If user identification is required for:

It must be handled separately.

Recommended method:

Use time sheets for user and operator tracking.

The same underlying data structure is used across multiple system views, including:

Core information remains consistent across all views:

The report can be grouped by:

This allows flexible operational analysis depending on user needs.

The Site + Vehicle Activity Overview Report provides a unified operational record by combining:

It supports operational visibility, documentation, and billing workflows while maintaining configurable thresholds to ensure accurate visit detection.