One link. One load. Complete visibility.
The driver installs WrapPoint and sees the load, no account needed. The broker watches the truck live until delivery.
Each vehicle above is following a routed path computed by the same engine that renders a broker's map, and the marker colour identifies the reporting source. This is a live feed, not a recording.
Visibility that survives a full shift.
Conventional tracking apps poll GPS on a fixed interval for the entire duration of a load, regardless of whether the truck is running at highway speed or sitting in a dock queue. The cost lands on the driver: a phone that will not last a fourteen hour clock. Carriers respond the way you would expect, by uninstalling the app once the load delivers, and the broker loses visibility on the next one.
WrapPoint reads position every thirty seconds for the entire load, at the dock and on open highway alike. That is a deliberate choice in favour of accuracy: arrival and departure are timestamped from observed position rather than reconstructed afterwards, and the broker's map interpolates along the routed path between fixes so the truck reads as continuous motion. A vehicle that is standing still keeps reporting on the same rhythm, which is what separates a truck waiting at a dock from a device that has gone offline.
Coverage gaps are handled locally. Positions are written to the device and transmitted in batches once connectivity returns, so a run through the Rockies or a long stretch of west Texas produces a complete, timestamped history rather than a gap that has to be explained during a detention dispute.
Reporting state is exposed rather than assumed. The driver sees the queue depth and the timestamp of the last confirmed delivery to the server, and the broker sees the same status from the other side. Where a load is billed against arrival and departure times, both parties need the record to be defensible, not merely optimistic.
Four steps, and the driver is done
The broker sends a link
A single text message carrying a token scoped to that shipment. It opens WrapPoint if the driver already has it, and offers the install if not. The token expires when the load closes.
The driver sees the load
Both stops and their dates are shown before consent. If the load is not theirs, closing the screen leaves no record.
He drives
Collection continues in the background with the screen locked. No credentials to recall, and no interaction required while the vehicle is in motion.
It shuts itself off
When the broker closes the load, the token is invalidated and collection terminates on its own. The driver can revoke at any point.
Why a driver keeps it installed
Because it asks for almost nothing and gets the dispatcher off the phone.
A steady thirty second rhythm
Every thirty seconds for the whole load, at the dock and on the highway alike, so arrival and departure times are observed rather than estimated.
Store and forward
Positions persist on the device through coverage gaps and transmit in batches, producing a continuous history.
Transparent reporting state
Queue depth and last confirmed delivery are visible to the driver, so a silent failure cannot be mistaken for normal operation.
Scoped to a single shipment
No account, no identity record, and no collection outside the window in which the load is active.
Position does not depend on one phone
The app carries the load, and on the runs where it cannot, something else does. Device level tracking fails for ordinary reasons: a dead battery, a phone left in the sleeper, two hours without coverage. LoadWrap resolves position from the highest priority source that is currently reporting, and states which source that is on every load.
| Source | When it carries the load |
|---|---|
| WrapPoint app | This is what the load runs on. Highest positional accuracy and the shortest reporting interval, available to any carrier regardless of telematics provider or fleet size. |
| ELD, optional backup | A carrier already running an ELD can authorise it once, at the fleet level, and it reports underneath WrapPoint at no extra cost. Nothing is asked of the driver, and it is unaffected by the state of his phone. |
| The same link in a browser | A driver who installs nothing opens the identical link in his browser, with no reduction in the broker's view. There is no load that cannot be covered. |
From the text message to the broker's board
The whole path, end to end. One message at dispatch, two screens for the driver, and the load line the broker watches while the truck runs.
Tap once to share your position with the broker:
loadwrap.com/track/K7X2M9
Tracking stops automatically at delivery.
Pinellas Park, FL 33782
Largo, FL 33778
Pinellas Park, FL 33782
Largo, FL 33778
| LOAD | CARRIER | REPORTING SOURCE | LAST FIX | POSITION | ETA |
|---|---|---|---|---|---|
| 4471 | Vela Transport LLC | WrapPoint app | 40 s ago | I-65 near Lafayette, IN | 17:42, on time |
| 4468 | Harlan Freight Co | ELD, phone silent 14 min | 2 min ago | I-70 near Effingham, IL | 19:05, on time |
| 4463 | Pinecrest Carriers | Browser link | 38 min ago, stale | US-31 near Kokomo, IN | held, position not current |
Same load, the broker's side. The source is written on every line, so a dispatcher reading the board knows whether he is looking at a phone or at the truck itself. Load 4468 lost the phone and kept going on the ELD without anyone calling the driver. Load 4463 is honest about being old, which is the line that keeps an appointment from being promised on a stale position.
WrapPoint carries the load. The rest is insurance.
The broker buys one thing: a position he can act on. WrapPoint delivers it, and a carrier that already runs an ELD can be plugged into the same load as backup, at no extra cost.
One product, not a menu. The load runs on WrapPoint, and the same link opens in a browser for a driver who installs nothing, so there is no load that cannot be covered. A carrier already running an ELD can switch it on underneath at no extra cost, which covers the single case a phone cannot, a dead battery. Whatever is authoritative at that second is written on the load, so a dispatcher never has to guess whether silence means a parked truck or a lost signal.
Ten times more positions on the same load
Same load, same 250 miles. A conventional tracking app takes a position every five minutes. WrapPoint takes one every thirty seconds, from the first mile to the last, which is the difference between an arrival time you observed and one you guessed.
How it behaves, in numbers
Published because these are the figures that decide whether a carrier keeps the app installed after the first load.
| Behaviour | Value | Why it is set there |
|---|---|---|
| Position sampling | 1 position / 30 sec | The same rhythm for the whole load. Arrival and departure are timestamped from observed position, and the broker map interpolates along the routed path between fixes. |
| Vehicle standing still | Keeps reporting | A truck in a dock queue still reports, which is how the platform separates a waiting truck from a device that has gone offline. |
| Offline buffer | 500 positions on device | Held locally through a coverage gap and transmitted in batches of 25 once connectivity returns. |
| Source marked stale | 15 min without a fix | Long enough to absorb a normal coverage gap, short enough that the broker learns about a problem before the appointment does. |
| Source marked down | 45 min without a fix | At this point the platform stops presenting the last position as current and falls through to the next available source. |
| ELD polling interval | 2 min | Independent of the driver's phone entirely, and unaffected by its battery or signal. |
| Position history for the broker | 90 days after delivery | Covers the window in which detention, dwell and delivery times are disputed. The broker can export the full ping history for a load as PDF, CSV or XLSX and keep it as evidence. |
| Map matching | Applied to the stored trail | Positions are matched to the road network, so a stored trail follows pavement rather than cutting corners across property. |
The broker keeps the position history of a load for ninety days after delivery and can export it at any point as PDF, CSV or XLSX, so a detention or dwell claim rests on a record rather than on two dispatch notes.
Questions carriers ask before they agree
Answered directly, including the ones that are usually left vague.
If the carrier has connected an ELD, position continues from the vehicle and the map states that it is now reporting through ELD. Nothing is asked of the driver.
If there is no ELD on that load, the source is marked stale after fifteen minutes and down after forty five, with the age of the last known position shown in plain language. The last position is never presented as if it were current.
No. The tracking token is scoped to a single load and is invalidated when that load closes, at which point the app stops collecting on its own.
Position before the load started and after it closed is not collected, so there is nothing to release even if someone asked for it.
No. There is no registration, no password, and no identity record. The driver opens the link, reviews the stops, and consents to that one load.
Drivers who prefer not to install anything can share from the browser instead, with no reduction in what the broker sees.
Nothing. Carrier side connection is free, whether that is the app, an ELD integration, or a push from the carrier's own dispatch system. The broker requesting visibility is the party that pays.
Yes. Position can be posted to the tracking endpoint on whatever schedule the carrier's system already runs, using the token issued for that load. Batched positions are accepted, duplicates are rejected server side, so a retry after a failed request is safe.
Arrival and departure are timestamped from observed position at fifteen second sampling inside two miles of the stop, and the full position history for the load is retained for ninety days after delivery.
That record is what makes a detention or dwell claim defensible rather than a disagreement between two dispatch notes.
Positions are written to the device and transmitted in batches once connectivity returns, so the history fills in rather than showing a gap. The driver can see how many positions are still queued, and the broker sees the source marked stale until they arrive.
ELD connections are handled through a telematics aggregator, so a carrier authorises once at the fleet level rather than per broker. The current provider list is confirmed during onboarding, because coverage changes as providers are added.
No implementation project
Brokers generate a tracking link directly from the LoadWrap board and send it by text at dispatch. Carriers and drivers are not required to hold a LoadWrap account, now or later.
WrapPoint is available on the App Store and Google Play. The same link also opens a browser based tracking page on any modern phone, so no install is required.