One timeline for the whole voyage.
The sensor record is only half the story. LoadGuard pulls telemetry together with the paperwork and the correspondence — and correlates all of it against containers, vessels, and voyages on one continuously updated shipment record.
Where is it, right now.
Container and vessel movements against the booked voyage — position, leg, transshipments, and ETA. The journey draws itself on one globe: every port call, every leg, every landmark the box passes.
Readings are judged against the cargo's own documented requirements — not generic thresholds. An excursion relative to the certificate, a route deviation, a missing inspection, a discrepancy between a document and observed activity: flagged as it happens.
Four streams, one record.
01
Device telemetry
Temperature, humidity, location, movement, shock, door and device-health readings — including everything recorded offline at sea and synced later.
02
Documents
Bills of lading, packing lists, invoices, certificates, inspection and survey reports, claims documents — read for what they contribute.
03
Correspondence
Carrier updates, booking confirmations, delay notices, and claims threads, forwarded to a dedicated shipment inbox.
04
Carrier tracking
Container and vessel movements against the booked voyage — position, leg, transshipments, and ETA.
The hard part isn't collecting it. It's connecting it.
Every email, document, alert, and sensor reading is identified against the shipment, container, vessel, voyage, cargo, and parties it concerns — then attached to that shipment's evidence record. Nothing sits as an isolated data point; a delay notice lands next to the telemetry from the same leg, and the inspection report next to the door event it explains.
Every extracted fact keeps a link back to its source, so operators can always verify where a claim in the record came from.
01
A dedicated shipment inbox
Each customer gets an individual address. Forwarded mail is processed, its shipment, container, vessel, and voyage identified, the original preserved, and the message filed to the evidence record — out of personal inboxes for good.
02
Document intelligence
Not just storage. Each document is analyzed for the cargo, quantities and values, parties, required conditions, handling instructions, findings, and agreements — every fact linked back to its source.
03
Context-aware monitoring
What's happening is judged against what the record knows: the cargo's documented requirements, the planned route and schedule, earlier events, and open investigations. It catches evidentiary gaps as well as physical risks — a missing certificate, a monitoring gap, a document that contradicts observed activity.
04
Alerts & investigation management
When something material is detected, the platform opens an auditable trail: what evidence triggered it, who was notified and when, whether it was acknowledged, what was done, and how it closed. In a claim, the response record matters as much as the event.
Ask in plain language. Get a plain answer.
> What actions were taken after the day-11 alert?
The excursion alert was sent to two operators at 08:41 UTC, acknowledged at 09:03. The carrier was notified at 09:17; the reefer setpoint was restored at 04:12 the following day. Corrective-action note and correspondence attached — 4 sources.
Where is it, right now
Position, leg, and ETA against the booked voyage
Did it stay in condition
Setpoint compliance across the whole journey, not spot checks
Was it mishandled
Shock, orientation, and door events with time and place
What's missing
Documents and evidence the record still needs
What do I send the insurer
A compiled evidence report, not a folder of screenshots