Trust and security
What the platform puts behind a load: written terms, a compliance gate, tracking, proof of delivery, carrier vetting and settlement held against the load.
Written terms per load
One agreement per engagement, covering the main load, the return load, vehicle requirements, non circumvention and the written confirmation, signed by both parties with name, position and date.
Carrier vetting
Carriers submit company documents, vehicle roadworthy certificates, driver licences and insurance certificates for review. Approval is a step, not an assumption, and expiry is monitored.
Compliance gate
A load cannot be accepted while a required document is missing or expired. The platform enforces it rather than leaving it to the parties to check each other.
Tracking on active trips
Position and ETA while the load is moving, visible to the parties on that load. Tracking runs only during an assigned trip and the driver can see when it is on.
Proof of delivery
Photographs, delivery note, quantity and condition, exception notes and a signature taken on the device at handover, attached to the load record and available to a dispute.
Settlement held against the load
Funds are held in escrow against the specific load and released on the agreed trigger, with the ledger visible to both sides.
Incidents in the field
Theft, hijacking, breakdown, accident and delay are facts of South African road freight, not edge cases. The driver app carries a single prominent incident action so an event is reported from the roadside as it happens, timestamped and positioned, rather than relayed by phone hours later.
What follows an incident, including any claim, is governed by the terms of the engagement and the cover the parties hold. Log-A-Load does not state a cover level or a liability position on this site.
Non circumvention
The load agreement carries non circumvention and non bypass terms. The prohibition extends to the introduced party and to return loads, repeat loads and related business arising from the introduction. Breach is treated as material.
Data and access
- Role based access, enforced on the server rather than in the browser
- Drivers see the trip and the paperwork, never rates, invoices or commercial terms
- Internal staff access is separate from customer accounts and cannot be created through public sign up
- Administrative actions on an account are logged, attributed and timestamped
- No sensitive data is held unencrypted on a driver handset, and a session can be revoked remotely
Disputes
A dispute is raised against the record: the agreement, the acceptance and confirmation, the tracking trail, the proof of delivery and the messages on the load. The evidence bundle is the basis of the decision, which is why the capture steps are built the way they are.
Ask the hard questions
If you want the detail on vetting, escrow, incident handling or the terms of an engagement, ask and we will answer it in writing.