Skip to content
A dump truck on a haul road
Fleet & assets

An undocumented trip is a claim you can’t prove

Contractor truck trips at project gates: each starts by scanning the asset’s code and is recorded with its location, time, photos, and quantities. Anything outside the geofence or off on quantity is flagged before approval.

Before

What happens today without this module

  • 01Quantities and times are reported verbally, turning every claim into a debate
  • 02Trips get logged outside the site boundary without anyone noticing
  • 03Contractor statements are compiled at month-end, after the window to object has passed
Capabilities

Exactly what this module does

  • Scan-to-verify

    A code printed on the truck opens the trip and ties it to the truck and its project.

  • A geofence with a declared margin

    A perimeter per site that accounts for signal accuracy — anything outside is rejected at the moment of scanning.

  • 2 mandatory photos

    The load and the plate at scan time, with automated checks for duplicate and tampered photos.

  • 28 fraud-detection rules

    4 of them reject the trip on the spot; the rest flag it for review or run retroactively overnight.

  • Purchase orders that cap trips

    A ceiling by trip count or days per contractor — beyond it, nothing gets recorded.

  • Monthly billing report

    Per contractor, truck, and material: approved trips only, ready for accounting.

Inside the service

How it actually works in your company

Contractor truck rounds at project gates are usually run on paper, pen, and trust — so the month-end statements arrive carrying numbers no evidence supports, and every line becomes a negotiation. This service makes a round exist only by scanning the truck's code at the gate, stamped with its location, time, two photos, and quantities, then passes it through fraud-detection rules that run at scan time and others that run overnight. The billing file arrives approved and evidence-backed before any dispute can even start.

01

A round exists by scan, not by entry

Every contractor truck carries a printed code. The gate supervisor scans it to open a round tied to that truck and its project, records the material and quantity on supply operations, and captures two mandatory photos — the load and the plate — straight from the camera; the system refuses a photo picked from the device gallery. Recording rounds is a defined authority for the transport-and-supply supervisor, the project manager, the data-entry role, and administration — not every user on the account.

02

Instant refusal, not later review

Strict rules decide at the very moment of scanning: a location outside the project's geographic boundary is refused, with signal accuracy factored into the equation; a signal weaker than the acceptable threshold is refused as well; a photo that is not a live capture is refused; a gap shorter than allowed for the same truck is refused; and a truck or material outside an active purchase order never opens a round at all. Every refused attempt is logged in a dedicated register that management reviews.

03

Purchase orders are a hard ceiling

Each contractor's purchase orders cap their rounds by count or duration. Consumption is deducted at scan time through an operation robust against simultaneous recording from more than one gate, and the remaining balance is shown to the supervisor the instant each round succeeds — when the ceiling runs out, recording stops on its own. No contractor exceeds the agreed limit, and nobody is surprised at month-end by rounds beyond the purchase order.

04

Rules that work while everyone sleeps

Alongside the instant rules, synchronous checks flag a round for review on a duplicated photo, a capture date that does not match the scan time, an impossible move between two locations, or a quantity beyond the truck's capacity. A nightly job then sweeps the whole log, spotting empty or blurred photos through artificial intelligence, a sudden surge in a contractor's rounds, a supervisor's favoritism toward one party, recording clustered into the day's last minutes, and spikes just before billing dates.

05

Confined decisions, clean billing

A flagged round is never decided by whoever recorded it: approval, dispute, and rejection are the authority of administration and the project manager alone within their own project, and rejection removes the round from billing permanently while its trace stays in the audit log. The monthly billing report is built from approved rounds only, detailed per contractor, truck, and material — alongside supervisor reports, daily activity, and an export ready for accounting.

Inside the product

The screen as your team uses it

Transport & Trips
Screen of Transport & Trips
The flow

How the process runs end to end

  1. 01

    Start by scanning

    The supervisor scans the truck’s code at the gate

  2. 02

    Field evidence

    Location, time, two photos, and quantities

  3. 03

    Conflict flagging

    Whatever doesn’t match is rejected or flagged for review

  4. 04

    A restricted decision

    Approval and rejection belong to the project manager and management — not to whoever recorded

After rollout

What actually changes

No promises built on numbers we don’t know about your company. What follows is the structural difference of wiring this module into the rest of the platform.

A backed claim
by a document, not a story
Fewer disputes
with contractors and clients
Faster approval
the file arrives complete from the field

Limits of this module

Location is captured at the moment of the action, not as a continuously tracked vehicle route.

Try Transport & Trips on your own assets — not a generic example

We tailor the demo to your operation, starting with the module that blocks your team today.