Load-Matching and Tender AI Agent

What this agent does

Shortlists the carrier, never tenders the load

Ingest the load, its lane requirements and your written carrier standard from supported sources.

Re-verify active operating authority at the moment of tender, not only at onboarding, and keep the timestamp.

Reason

Confirm insurance with the insurer or the agent, rather than from a certificate the carrier supplied.

Check the limits actually carried against what this load requires, and record the channel used.

Rank the shortlist against your written standard, and mark what the record does not establish.

Decide

Log every override of that standard with the person who made it and the reason they gave.

Route the shortlist to a named person, who decides which carrier is tendered.

Out

Retain what was checked, what was found and who decided, for the period the records rule requires.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent ranks and evidences; a named person selects and tenders, and your firm stays the broker of record.

Example workflow

One load, request to tender

AgentHuman

1Load receivedShipper order, TMS load record, board posting or lane commitment

2Evidence gatheredOperating authority, insurance confirmed with the insurer, equipment and lane history, each with its source and time

3Shortlist preparedRanked carriers, evidence and confidence

4Controls appliedAuthority re-checks at tender, insurer-confirmed cover, your written standard and the confidence threshold

No human action required

Stages 1 to 4 run unaided and tender nothing — the shortlist is assembled, and the person's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold

High confidence

Goes to the named person to tender.

Low confidence

Adds a compliance read first.

A person tenders

The shortlist is held with its evidence, its gaps and the confidence.

Tender · Reorder · Send to compliance

Tendered — offer out to the carrier▼

6Load records updatedOnly where write access and approval policy allow it

7Outcome evaluatedEvidence gaps, overrides recorded, tender acceptance and what each selection actually rested on

Overrides

Every override of the standard is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Tendering a load or issuing an offer to a carrier.

Deciding which carrier is good enough to be used.

Waiving your written carrier-qualification standard.

Accepting a certificate the carrier supplied itself.

Automation boundaryAgent acts unaided

✓Gather authority, insurance and lane evidence for each.

✓Rank the shortlist against the standard you have written.

✓Mark what the record leaves unestablished, carrier by carrier.

✓Hold the shortlist for the named person who tenders the load.

Any write happens inside the boundaries agreed at implementation, never ahead of approval.

Directing the route, the driver or the manner of haul.

Describing your firm's operations as a carrier's.

Deciding whether a transparency waiver still holds.

Changes to the qualification standard or its rules.

Example output

One shortlist, annotated

Automating selection concentrates the exposure and records it — so each ranking carries its evidence.

Matching output · single loadIllustrative example

Load

Top of the shortlist

Authority re-checked

Insurance confirmed

Confidence

Standard applied

Reefer, long haul

Ranked first on lane history and equipment, with one gap noted

11:42, at tender

Confirmed with the insurer direct

89%

Your written qualification standard

As receivedTaken from the FMCSA record and the insurer's own confirmation.

What was checked Active operating authority Insurance, with the insurer Limits against this load

Why it is firstIt meets the standard you wrote — no court set that standard.

ActionTenderReorderSend to compliance

What the score decidesBelow the configured threshold the shortlist picks up a compliance read before.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Every loadFrom the TMS or the load queue

03Matching

Shortlist against your standard

Draw on the authority record, insurer-confirmed cover and the lane history you already hold.

01Approved path

Shortlist it, a person tenders

Routine lanes come back ranked with the evidence attached.

02Human review

Pass the rest to compliance

Evidence gaps, overrides and low-confidence shortlists are marked, so the desk's read starts where risk concentrates.

04Build an evidence trail

The match, the evidence behind it and the person who tendered stay on the load file.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

TMS and load recordsMcLeod · MercuryGate
Trimble · Revenova

Load boardsDAT · Truckstop
Private capacity networks

Authority and insuranceFMCSA records · Motus
Insurer and agent confirmation

Agent

Load matching and tender

Gathers the evidence
Ranks the shortlist
Holds for tender

Onboarding and filesCarrier onboarding tools
Document archives

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the tender

The layers sit one inside the next. What none of them catches is in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeFall back to listing available capacity when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, standard and check-configuration changes.Track

L4TraceabilityRecord what was checked, what came back and when it was checked.Record

L3Tender heldHold the shortlist for the named person; it governs who tenders, not whether the carrier is sound.Gate

L2Qualification rulesTest each carrier against your written standard; a failure returns the shortlist with the reason.Restrict

L1Confidence thresholdsRoute low-confidence shortlists to a compliance read before anyone sees them.Require review

Model coreShortlist prepared — the ranking, the evidence, the gaps and confidence

L1 – L2Test whether a carrier may be put forward

L3Puts the tender in a person's hands

L4 – L5Hold the match and the evidence behind it

L6Falls back to listing available capacity when signals degrade

How Nestack evaluates it

Evaluate the whole selection — not only the carrier that took the load.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the shortlist the desk reads

Depth of coverage ▼

E1Final-output evaluationWas each check re-run at tender rather than carried from onboarding?

E2Step-level evaluationDid the agent apply your written standard, in its current version?

E3Tool evaluationDid it read the correct authority record and write the correct load?

E4Confidence calibrationDo low-confidence shortlists actually attract more reordering?

E5Slice evaluationHow does performance change across specific carrier segments?

E6Business outcomeHow many shortlists were reordered, and how many should have been?

Floor — the selection your firm answers for

Failure modes

Where each failure originates in the agent

Seven ways a shortlist goes wrong, by stage.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

AQ-03

Onboarding check reused

A months-old authority result stands in at tender.

Stage gathersAuthority, insurance, equipment and lane history

02 · Reasoning2 modes

AQ-04

Standard applied loosely

A qualification rule is read as a preference, not a bar.

AQ-06

Ranking read as decision

The order of the list is treated as the selection itself.

Stage proposesThe ranking, the evidence and confidence

03 · Tool / write2 modes

AQ-02

Tender sent without a person

An offer reaches a carrier before anyone has selected.

AQ-05

Duplicate tender

The same load is offered twice into one lane.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

AQ-01

Carrier-supplied certificate

Cover is taken from a document the carrier provided.

Stage returnsThe shortlist the desk reads and tenders from

05 · Change / Version1 mode

AQ-07

Silent standard regression

A model or rule change relaxes what the shortlist admits.

Stage tracksModel, prompt, qualification standard and checks

Sev-1 · tendered with no person Sev-2 · put forward against the standard Sev-3 · evidence degrades, list routes to review

See the complete Transportation failure-mode catalogue →

Affected slices

One segment carries the selections you would regret

Carriers new to your file is the segment that hides — small enough to disappear into a total, and carrying most of the reordering. Nestack reports the reorder rate by carrier segment, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Carriers new to your file	6.6%	3.2×	Review
Brokered spot coverage	4.5%	2.2×	Review
Lanes covered under time pressure	3.9%	1.9×	Watch
Contracted core carriers	1.2%	0.6×	Normal

Bar: reorder-rate lift vs. contracted-core-carrier baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

Write the case, then close the cycle

The cycle ends in a regression case, not in a meeting about what happened. That suite is what the next tender put out to a carrier is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Reorder rate rises in a carrier segment.

02Diagnose

Take the shortlist apart: which check produced the rank, and which one should have blocked it.

03Improve

Every change is versioned against the tenders that exposed it.

04Verify

A failing case holds the release back.

05Learn

The case joins the suite for good, and the matching rules are revisited.

Learn → DetectThe return edge. The next detection runs against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, matching workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Matching and tender workflow discovery and boundaries.

02TMS and load-board assessment.

03Carrier-qualification standard and evidence mapping.

04Load and carrier-record ingestion.

05Ranking logic and evidence binding.

06Confidence scoring and compliance routing.

07Tender approval workflow.

08TMS and load-board integration.

09Selection-evidence cases.

10Guardrails and tender controls.

11Match-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne lane set, one office ProductionProduction TMS and load boards AdvancedMultiple entities / regions

Introduced at Pilot

Shortlisting to your written standard✓✓✓

Tender held for a person✓✓✓

Match-quality baseline✓✓✓

Introduced at Production

Reporting by lane and equipment—✓✓

Tender workflow in your systems—✓✓

Approved write-back—✓✓

Load-board integration—✓✓

Introduced at Advanced

Multi-entity qualification rules——✓

Multi-stage compliance approvals——✓

High tender volume——✓

Multi-entity tender controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your written carrier-qualification standard → Load and carrier-record ingestion and evidence mappingWeek 1

02Representative past selections → Matching baseline, ranking logic and evidence bindingWeek 2

03Your insurer and authority check routes → Carrier-qualification standard and evidence mappingWeek 1

04Access to relevant APIs, feeds or exports → TMS and load-board assessment, then integration setupWeek 2

05Matches you would not want tendered → Evidence cases and the evaluation suiteWeek 4

06What must reach a person before a load is tendered → Confidence scoring, compliance routing, guardrails and tender controlsWeek 3

07Named people who tender the load → Tender approval workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The bands follow the real work, which is why evaluation and pilot share the fifth week.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Matching workflow discovery, standard mapping and the boundary W2Load-board and authority integration and the matching baseline W3Matching workflow, confidence logic and tender controls W4Evaluation suite, evidence cases and failure-mode testing W5TMS integration, a pilot lane set and targeted corrections W6One tender cycle worked under the desk, then handover

Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.

At the end of W6The cycle closes validation and Agent Care assumes monitoring.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Transportation AI agent

Build a matching agent that shortlists and leaves the tender to a person.

Show us your lanes, your boards and how a load gets covered today. Bring the written qualification standard and the insurer verification route — without a written standard there is nothing for the agent to enforce and nothing for you to show later.

Discuss this agent →

Nestack Agents · Load matching and tenderAGT-TR-08 · Agent Care available after launch