The freight operating layer

The work.
The intelligence.
The record.

Move the load. Know why.
Show the record.

HaulLynx connects the parties, decisions and execution of freight in one operating environment—with Lynx Intelligence bringing context into the work, and Provenance preserving the evidence behind it.

THE CONNECTED RECORD01 — 04
HAULLYNX / PROVENANCE
Chicago, ILDallas, TX
LOAD RECORD / HX-804170DRY VAN
PartiesIdentity. Authority. Source.
01
TermsThe agreement, in context.
02
EvidenceAttached to the work.
03
DecisionWho acted. When. Why.
04
Not just a status. A record you can trace.
CONTEXT → ACTION → EVIDENCE
Built for brokers. Connected to fleets and owner-operators.Follow the record

01 / The gap

The load moves forward.
The context gets left behind.

The terms live in an email. The check happened in a browser tab. The explanation sits in a text thread. When a question surfaces, your team has to reconstruct the story.

EMAIL ATTACHMENTPDF
RATE CONFIRMATIONHX-804170

Chicago, IL Dallas, TX

53′ dry vanPickup · Sep 23
Version 01Accepted · 09:58 AM$2,600
Version 02Sent · 10:04 AM$2,750
Revised rate sent. Acceptance not attached.
rate-confirmation-v2.pdf2 versions
01 / THE TERMS

Agreed. Then amended.

Which version did each party accept?

ONBOARDING FILEREVIEW
CARRIER REVIEWMAR 08

A check is a point in time.

Assigned carrierReview snapshot
Operating authorityFMCSA record · Mar 08, 09:42 AM
Active then
Insurance on fileCertificate · Policy end Sep 21
Dated evidence
Tender date: Sep 22. Where is the latest check?
carrier-review / archived snapshotMar 08
02 / THE CHECK

Reviewed. Then forgotten.

What was known when the load was tendered?

ARRIVAL RECORDSSEP 23
DELIVERY / HX-804170DALLAS, TX

Two times. Different events.

DR
Driver text

“At the gate. Waiting for a door.”

DC
Dock log

“Door 14 assigned. Begin unloading.”

Arrival and dock time are not the same event.
Text message + receiving log2 sources
03 / THE DISPUTE

Two accounts. No shared context.

Which event starts the clock—and where is the proof?

The problem isn’t a lack of information.
It’s the missing connection between it.

02 / The operating layer

One place to operate.
No separation from the context.

From coverage and coordination to execution and settlement. The work, the intelligence and the record belong together.

THE BROKER WORKSPACEHaulLynx / Coverage
HaulLynx broker workspace with sample carrier portraits, priority lanes, shared Fleet truck-image markers on the HERE map, origin and destination pins, recorded sample travel, the projected route ahead, and a hover card showing the load, ETA, driver, carrier and tracking source; activity and settlements below
One place to work. Context that stays connected.Workspace shown with sample data

03 / Lynx Intelligence

Context before the decision.
Evidence after it.

See the distinction between a proposal and an agreement. Lynx surfaces the open item. The authorized person decides. A separate amendment preserves the accepted change.

FOLLOW ONE SAMPLE TRANSACTION

Chicago, IL Dallas, TX

HX-804170Prairie Line Transport · Dry van

01 / THE OPERATING CONTEXT

A proposed change.
Not yet an agreement.

The booking already has an executed rate confirmation. The broker proposes a rate change through the load’s change-order workflow. The carrier has not decided yet.

WORKSPACE

A proposal does not replace the agreed terms.

LOAD RECORD / SEP 22HX-804170
01
Executed rate confirmation

$2,600 · Countersigned at 09:58 AM

Executed
02
Proposed rate change

$2,750 · Broker proposed at 10:04 AM

Proposed
03
Carrier decision

Awaiting acceptance or rejection

Pending

This is a change to an existing agreement—not a new tender or a comparison of emailed PDFs.

Know what is still open.
Decide with the record in view.

Explore Lynx Intelligence

04 / Provenance

The decision has a history.
Put it on the record.

Explore the sources a decision can reference.
When a reason and reviewed sources are explicitly recorded,
Provenance preserves that submitted basis.

PROVENANCE / RECORD EXPLORERHX-804170

EXPLORE A SAMPLE LOAD RECORD

The source remains
part of the story.

IDENTITY / SOURCE RECORDSource linked

A name is a starting point.
Not the whole answer.

Keep the party’s identity connected to the source reviewed and the time it was received.

CARRIER AUTHORITYAuthority record reviewedSource: FMCSA · Received Sep 22, 09:42 AM
PARTY ON THE LOADPrairie Line Transport · HX-804170

The check stays connected to the party and the transaction it informed.

Traced, not asserted.

See where the information came from.

History, not hindsight.

Understand the context at the time.

Context, not another silo.

Follow the connection to the load.

05 / Our standard

Trust is not
a tagline.
It’s a standard.

For brokers, fleets and owner-operators.
Clear expectations. Visible reasoning.
Human accountability.

01Evaluate the parties.

Connect onboarding and review to the work. Keep what was checked, its source, and its timing in context—not scattered across inboxes.

02Explain the decision.

Make the reason visible. Surface relevant information and keep the person’s decision connected to the evidence that informed it.

03Preserve the context.

A later change should not erase what was known earlier. The record should distinguish an original event from a subsequent correction.

04Respect the boundaries.

Connected work does not mean unrestricted access. Each party’s view must respect its role and its permitted access to the transaction.

THE HUMAN STAYS IN CONTROL

HaulLynx supports informed decisions. It does not certify a party or guarantee payment or performance. Responsibility stays with the person making the decision.

The reason we built it

HAULLYNX INC. / MAHWAH, NJ

Freight never lacked software.
It needed an operating layer
that connects the whole job.

HAULLYNX

That is HaulLynx. A connected place to operate. Intelligence within the workflow. Evidence behind the decisions. Not three separate stories. One way to work.

Built for the broker’s next move

Run the load.
Stand behind the decision.

See how the work, Lynx Intelligence and Provenance connect.
Then bring your operation into the conversation.