DEV Community: Dimitrii Khristoforidi

Why Human-in-the-Loop AI Makes Sense in Freight Dispatch

Dimitrii Khristoforidi — Mon, 21 Sep 2026 15:02:32 +0000

Freight dispatch is not a simple classification problem. It is a sequence of decisions made under changing constraints, incomplete information, time pressure, and operational risk.

A dispatcher may need to evaluate rate, loaded miles, deadhead, fuel and toll costs, pickup and delivery windows, driver hours, broker authority, identity and payment risk, destination market, reload opportunities, driver preferences, and customer relationships. Some of these variables are structured and easy to calculate, while others depend heavily on context.

That is why fully autonomous dispatch is not always the most useful goal.

A more practical model is Human-in-the-Loop AI, where AI and automation handle repetitive analysis, data enrichment, prioritization, and anomaly detection, while humans remain responsible for judgment, negotiation, exceptions, and final commitments.

For freight dispatch, this is not a compromise between manual work and automation. In many cases, it is the better system architecture.

What Human-in-the-Loop AI Means

Human-in-the-Loop, or HITL, describes systems where automation performs part of the workflow while a person remains involved at defined decision points.

The basic pattern looks like this:

Data → system processing → recommendation or alert → human decision → action

That differs from full automation:

Data → automated decision → automatic action

And it also differs from a fully manual process:

Data → human research → human calculation → human decision → action

The advantage of HITL is that each side handles the kind of work it performs best. Software is effective at processing large volumes of information quickly and consistently, while humans are better at interpreting ambiguity, weighing context, and making judgment calls.

Freight dispatch contains both types of work, which makes it a natural use case for this model.

Why Freight Dispatch Is Difficult to Fully Automate

At first glance, dispatch can look like a straightforward optimization task: a truck is available, loads are available, so the system should simply choose the best one.

In reality, “best” is rarely determined by one variable.

A load with the highest rate may have too much deadhead, weak reload potential, a difficult delivery window, questionable broker signals, poor fit with remaining driver hours, or a destination the carrier wants to avoid.

A lower-paying load may be strategically better because it positions the truck for another market, fits the driver's schedule, comes from a trusted broker, reduces empty miles, or supports a recurring lane.

Dispatch decisions combine deterministic calculations with contextual judgment. Deterministic software is usually better suited to calculations and rule-based checks, while AI can help interpret unstructured information and assemble relevant context. Humans remain responsible for consequential judgment calls.

Where AI Creates the Most Value

A large share of dispatch work is repetitive.

For each potential load, someone may need to read the details, calculate total miles, account for deadhead, calculate rate per mile, estimate fuel and toll costs, check the broker, review authority or risk data, compare the load with alternatives, inspect incoming documents, and identify obvious problems.

Doing this once is easy. Doing it continuously across dozens of opportunities creates cognitive load.

AI and automation can compress much of that process before the dispatcher needs to engage deeply.

A practical workflow might look like this:

Raw load data
↓
Data normalization
↓
Cost and RPM calculations
↓
Broker and risk enrichment
↓
Document analysis
↓
Opportunity ranking
↓
Human review

The goal is not to remove the dispatcher. It is to move the dispatcher closer to the actual decision by eliminating repetitive research and calculation.

Not Every Dispatch Problem Needs AI

This distinction matters because not every part of the workflow benefits from probabilistic systems.

Some dispatch tasks are deterministic and should stay deterministic.

For example:
total_miles = loaded_miles + deadhead_miles
rpm = rate / total_miles

estimated_contribution_margin = rate

fuel_cost
toll_cost
estimated_operating_cost
other_expected_costs

These calculations do not need an LLM. They need reliable software and accurate inputs.

AI becomes more useful when the system has to interpret less structured information, such as free-form emails, RateCons, incomplete descriptions, unusual broker communication, conflicting data, exceptions, or risk signals spread across several sources.

A strong freight AI system should therefore combine deterministic logic with probabilistic interpretation rather than use AI for every step.

Where the Human Still Matters

Negotiation

Suppose the system calculates that a load becomes attractive at $2,750 instead of the posted $2,500.

That does not mean software automatically knows the best way to reach that number. Negotiation depends on broker urgency, truck availability, lane conditions, timing, relationship history, and how much room the broker is likely to have.

AI can suggest a target, but a dispatcher can interpret the conversation and decide how aggressively to negotiate.

Driver Context

Two trucks may look identical in a scheduling system but be operationally very different.

One driver may need to return home, avoid a region, have limited available hours, prefer a certain lane, have a maintenance appointment, or already be positioned for another load.

Some of this information can be structured, but some of it exists only as operational context that humans understand better.

Exceptions

Freight operations are full of edge cases. Appointment changes, detention, incorrect pickup data, last-minute route problems, suspicious documents, unusual payment requests, driver delays, and weather disruptions can all break an otherwise normal workflow.

Well-defined cases with validated inputs and known failure modes are often easier to automate. The system must still detect when a case falls outside those conditions. Exceptions are where human judgment becomes especially valuable.

Risk Acceptance

AI can flag risk, but it cannot always decide how much risk a company should accept.

Consider two loads.

Load A

good RPM;
familiar broker;
predictable lane;
simple pickup.

Load B

higher margin;
unfamiliar broker;
recent contact change;
unusual payment information.

Software can surface those differences, but the final decision depends on the carrier's risk tolerance, operating strategy, and current context.

That is a business judgment rather than a classification task. Repeated operational constraints should be captured as structured, permissioned data where possible. Human review should cover temporary circumstances and context that has not yet been recorded, rather than compensate permanently for missing system data.

The Better Question Is Not “Can AI Make the Decision?”

A better question is:

Which parts of the decision should AI handle, and which parts should require human judgment?

A practical division might look like this:

Parse load data

System role: AI-assisted extraction
Human role:Review exceptions

Calculate RPM

System role: Deterministic
Human role: Set targets

Estimate trip costs

System role: Deterministic
Human role: Override assumptions

Compare loads

System role: Rules + ranking
Human role: Apply strategy

Check broker data

System role: Data enrichment
Human role: Decide acceptable risk

Flag inconsistencies

System role: Rules + AI
Human role: Investigate

Summarize RateCon

System role: AI-assisted
Human role: Review critical terms

Suggest negotiation range

System role: Decision support
Human role: Negotiate

Rank opportunities

System role: Rules + AI
Human role: Select final load

Commit the truck

System role: Prepare action
Human role: Final approval

This is better understood as decision augmentation than autonomous dispatch.

Human-in-the-Loop Is a Reliability Pattern

Human review improves reliability only when the reviewer has enough information, time, and authority to challenge the system. A confirmation button by itself is not a meaningful control. The interface should expose sources, assumptions, uncertainty, and the reason a case was escalated. There is another reason HITL makes sense: many AI models used for language, document, and pattern interpretation produce probabilistic outputs.

A deterministic rule behaves predictably:

if rpm < target_rpm:
mark_economics_below_target

A deterministic rule can reliably identify that a threshold was missed without deciding, by itself, that the load should be rejected.

An AI system may instead interpret documents, messages, inconsistent terminology, incomplete fields, or risk patterns.

That flexibility is useful because freight data is rarely perfectly clean, but it also introduces uncertainty.

For low-impact tasks, that uncertainty may be acceptable. For decisions with financial or operational consequences, it often makes sense to introduce review thresholds.

For example:
if required_data_valid
and no_material_risk_signals_detected
and economics_above_target:
prioritize_for_dispatcher
else:
route_to_the_relevant_review_queue

The policy should distinguish between missing data, economic exceptions, identity concerns, document conflicts, and operational constraints rather than treating every exception the same way.

The system does not need authority over every downstream action. It needs to reduce the number of situations that require deep manual investigation.

Confidence-Based Escalation

One useful HITL pattern is validation- and confidence-based exception routing. Model confidence or uncertainty signals can be useful inputs, but they should be combined with schema validation, source agreement, required-field checks, deterministic business rules, and out-of-distribution or novelty detection where applicable.

Instead of sending every case to a human, the system escalates only situations that are unusual, incomplete, or ambiguous.

A normal case might have complete information, no material identity mismatch, economics above target, no material discrepancies across the checked broker data, and clear document extraction. In that situation, AI can process and summarize the opportunity.

An exception case might contain conflicting company information, a suspicious contact change, missing fields, unusual payment details, unclear document terms, or low-confidence extraction. That case should be routed for human review.

This is more efficient than either full manual processing or blind automation because human attention is reserved for the decisions where it creates the most value.

Human Attention Is the Scarce Resource

In freight operations, data is not always the main bottleneck. Attention often is.

A dispatcher may simultaneously be searching load boards, monitoring email, talking to brokers, coordinating drivers, calculating margins, reviewing documents, and resolving exceptions.

Every additional lookup consumes attention.

If AI and automation remove ten routine checks and surface one material exception, the value is not simply automation. The value is better allocation of human attention.

The dispatcher spends less time retrieving information and more time deciding what to do with it.

A Practical HITL Architecture for Freight Dispatch

A useful architecture can be split into several layers.

Layer 1: Data Ingestion
The system receives information through authorized APIs, supported integrations, user-provided documents, and explicitly permitted inbox or browser workflows. Access should follow least-privilege principles and the connected platform’s terms.

Layer 2: Data Enrichment
Additional context can then be added, including operating authority, carrier insurance information where applicable, broker bond or trust information, payment or factoring signals, route data, and historical interactions. Each enrichment result should retain its source, retrieval time, coverage, and validation status. Missing or stale data should be shown explicitly rather than interpreted as a positive result.

Layer 3: Deterministic Processing
Calculations that should remain predictable are handled by deterministic software. This includes total miles, deadhead, RPM, fuel estimates, toll estimates, and margin calculations.

Layer 4: AI Interpretation
AI becomes useful for tasks such as extracting document fields, summarizing communication, detecting inconsistencies, grouping and explaining potential risk signals for review, and highlighting why a load may deserve attention.

Layer 5: Decision Policy
The system determines whether a case can continue through the standard workflow or whether it requires human review.

For example:
if not required_data_complete:
route_to("data_review")

elif identity_mismatch_detected:
route_to("identity_review")

elif document_conflict_detected:
route_to("document_review")

elif operational_constraint_detected:
route_to("operations_review")

elif expected_margin < target:
route_to("economic_exception")

else:
prioritize_for_dispatcher()

Layer 6: Human Decision
The dispatcher sees the opportunity together with relevant calculations, risk signals, supporting context, uncertainty, and a recommended next step.

From there, the dispatcher decides whether to contact the broker, negotiate, reject, investigate, or book.

That is the core idea behind AI Dispatch: use automation and AI to compress information and surface decisions, while keeping humans involved where judgment and commitment matter.

Human-in-the-Loop Does Not Mean Human-in-Every-Step
HITL should not mean requiring someone to approve every automated calculation. That simply recreates manual work with additional software around it.

A better pattern is selective intervention.

For example, from 100 opportunities:

60 fall below predefined economic thresholds
25 meet requirements but rank lower
10 are strong candidates
5 require exception review

The dispatcher should not need to reconstruct all 100 cases.

The system should make the 10 strong opportunities easy to compare and the
5 unusual cases easy to investigate.

Human involvement becomes targeted rather than universal.

Keep Humans in Control of Irreversible Actions

A useful design principle is to separate reversible and irreversible actions.

Lower-impact, reversible actions can usually be automated more aggressively, provided their outputs remain traceable and easy to inspect.
Their cumulative effects should still be monitored: an incorrect ranking or summary repeated at scale can materially influence decisions.

Higher-impact actions such as committing a truck, accepting contractual terms, approving a questionable counterparty, sending sensitive information, or creating a financial obligation deserve stronger human control.

The closer an action gets to creating an external commitment, the stronger the case for explicit human approval.

Human Decisions Create Better Feedback

Keeping dispatchers in the loop also creates useful feedback.

Suppose AI recommends Load A, but the dispatcher chooses Load B because it positions the truck better for tomorrow, the broker relationship is stronger, the delivery window is safer, or the driver prefers the destination.

That override contains valuable information.

With explicit feedback, outcome tracking, privacy controls, and periodic evaluation, those decisions can become useful signals for improving future recommendations. An override should not automatically be treated as a correct training label.

The feedback loop becomes:

AI recommendation → human decision → operational outcome → improved future recommendation

Human judgment is therefore not just a safeguard. It can also become a source of learning for the system.

AI Dispatch Should Reduce Cognitive Load, Not Remove Judgment

The strongest role for AI in dispatch may be decision compression.

Instead of showing a dispatcher rate, miles, deadhead, fuel estimate, toll estimate, broker data, documents, and several messages as separate inputs, the system can summarize the situation into something more actionable:

Strong margin. Moderate deadhead. Required broker checks completed against the listed sources. No material risk signals were identified in the checked data as of [timestamp].

Delivery fits the current schedule.

The underlying information still exists, but the dispatcher no longer has to reconstruct the meaning from scratch every time.

That is where AI becomes genuinely useful.

The Future of Freight Dispatch Is Probably Neither Manual nor Autonomous

The AI debate is often framed as two extremes: either humans do everything or AI does everything.

Freight dispatch points toward a third model.

Machines are good at processing large volumes of information, repeating calculations, monitoring many signals, summarizing documents, identifying patterns, and ranking opportunities.

Humans are better at interpreting ambiguity, negotiating, understanding relationships, handling exceptions, balancing competing priorities, and deciding how much risk to accept.

A strong dispatch system should combine both.

The practical architecture is simple:

Deterministic software handles calculations. AI helps interpret and organize complex information. Humans retain authority over judgment, exceptions, and external commitments.

That is not incomplete automation.

For freight dispatch, it may be the more reliable form of automation.

How AI Decision Support Fits Between Load Boards and TMS

Dimitrii Khristoforidi — Tue, 15 Sep 2026 06:28:51 +0000

Freight dispatch software has traditionally been built around two major systems.

On one side, there are load boards - marketplaces where carriers and dispatchers discover available freight.

On the other, there are Transportation Management Systems (TMS) — systems primarily used to plan and manage transportation operations, including dispatch, drivers, documents, billing, tracking, and reporting. Some TMS platforms also support quoting and pre-booking workflows.

Both are essential. But there is a gap between them.

A load board can answer: What loads are available?

A TMS can answer: What loads are we already managing?

Neither system consistently brings together every carrier-specific factor needed to answer the question dispatchers face dozens or hundreds of times per day:

Is this particular load worth booking right now?

That gap creates an opportunity for AI-assisted decision support that connects existing systems and adds carrier-specific analysis.

Rather than replacing load boards or TMS platforms, an emerging class of tools can act as a decision-support layer between freight discovery and execution.

TL;DR

Load boards answer: What freight is available?
TMS platforms answer: How do we execute and manage the load?
The missing layer answers: Should we book this load?
An AI decision layer combines load economics, deadhead, route context, broker data, risk signals, and other information before the decision.
The dispatcher stays in control; AI reduces research, calculations, and context switching.
LoadConnect is one example of this architecture, working alongside existing load boards and TMS platforms rather than replacing them.

The Traditional Dispatch Stack

A simplified carrier workflow often looks like this:

Load Board → Dispatcher → TMS

The load board provides freight opportunities.

The dispatcher evaluates them.

Once a load is accepted, the TMS becomes the primary operational system.

The architecture looks simple, but the dispatcher step in the middle is usually anything but simple.

Before accepting a load, a dispatcher may need to evaluate:

linehaul rate;
loaded miles;
deadhead to pickup;
total trip miles;
revenue per mile;
estimated fuel impact;
tolls;
pickup and delivery timing;
available driver hours and appointment feasibility, based on authorized HOS/ELD data when available;
broker authority;
broker payment history;
fraud indicators;
factoring compatibility;
route positioning;
the likelihood of finding the next load.

Much of this information does not exist in one place.

The actual workflow therefore looks more like this:

Load Board → Maps → FMCSA / broker checks → Rate calculator → Email → Spreadsheet → Dispatcher judgment → TMS

The dispatcher becomes the integration layer.

That works, but it does not scale particularly well.

Why Load Boards Do Not Solve the Entire Decision

Load boards are optimized for freight discovery. Their primary job is to connect available capacity with available freight.

Modern platforms may also provide rate information, broker ratings, routing tools, saved searches, alerts, and other useful signals.

But the existence of those signals does not necessarily mean the entire booking decision happens inside the load board.

Consider a simplified example.

A dispatcher sees two loads:

Load A

Rate: $2,800
Loaded miles: 1,000

Load B

Rate: $2,550
Loaded miles: 900

At first glance:

Load A RPM = $2.80
Load B RPM = $2.83
Load B appears slightly better.

But then deadhead is added:

Load A deadhead: 20 miles
Load B deadhead: 170 miles

Now the economics change.

Then the dispatcher notices:

Load A delivers into a strong outbound market.
Load B delivers into a weak reload market.
Broker A has established payment history.
Broker B requires additional verification.
Load B also creates a scheduling problem for the driver's next appointment.

The decision is no longer a simple load-board query. It is a multi-variable decision problem.

Why the TMS Does Not Fully Solve It Either

A TMS is usually the system of record for transportation operations.

Once a load enters the operation, a TMS can manage:

load assignments;
driver status;
equipment;
documents;
billing;
settlements;
tracking;
customer communication;
operational reporting.

But many TMS platforms are optimized around execution, not necessarily around evaluating every external spot-market opportunity before it is accepted.

That creates an architectural gap:

Freight discovery → ????? → Operational execution

The missing component is not another freight marketplace. It is a decision-support system.

The AI Decision Layer

An AI decision layer sits between discovery and execution.

A simplified architecture looks like this:

Load boards and operational systems → Decision-support layer → Dispatcher
Dispatcher-approved actions → TMS and communication tools

The purpose of the middle layer is to combine fragmented information before the dispatcher makes the final decision.

That can include:

Load data + route data + deadhead + rate information + carrier economics + broker information + fraud signals + historical context + communication + documents
Decision context

The output does not have to be:

Book this load.

A more useful system might provide:

Estimated RPM: 2.74
Deadhead: 31 miles

Broker:

Authority active
Established operating history
No major risk indicators found in the sources checked

Route:

1,042 total miles
Historical and currently available market data suggest stronger reload potential for this equipment type. Availability is not guaranteed.

Potential issue:

Delivery window may conflict with next planned load

The dispatcher still makes the decision.

The software reduces the amount of research required to make it.

Decision Support Is Different From Full Automation

This distinction matters. There is a tendency to describe every AI product as an autonomous agent that will eventually perform the entire workflow.

Freight dispatch is more nuanced.

Some tasks are highly automatable through calculations, rules, APIs, document-processing models, or a combination of these approaches:

Calculate RPM
Calculate deadhead
Extract a rate from a document
Look up an MC number
Compare structured records
Draft an email
Detect a changed field

Not every automated step requires AI. Deterministic calculations and authoritative data checks should remain deterministic; AI is most useful for interpreting unstructured information, assembling context, and explaining tradeoffs.

Other tasks depend heavily on context:

Should we accept $2.55/mile on this lane today?
Is the expected value of repositioning this truck greater than the additional fuel, time, HOS consumption, and risk of waiting for the next load?
Should we negotiate or take the current offer?
Does this broker relationship justify accepting a weaker rate?
Is this load strategically useful because of where it delivers?

Those decisions combine data with operational judgment.

A practical AI architecture therefore looks less like:

AI → autonomous booking

and more like:

AI → analysis → dispatcher decision → action

This is the human-in-the-loop model.

Where the Data Comes From

An AI decision layer becomes useful only when it can combine information from multiple sources.

For example:

Load Board → Route Data → Broker Data → Carrier Costs → AI Decision Layer → Dispatcher → TMS

The architecture becomes particularly useful when it can operate inside the existing workflow rather than forcing users to constantly open another dashboard.

That is why authorized APIs and TMS integrations are preferred where available. Browser extensions and inbox integrations can provide useful workflow access, but they require appropriate permissions, security controls, and compliance with the connected platform’s terms.

A Practical Example

Imagine a dispatcher searching a load board. A promising load appears.

Without an additional decision layer, the process might be:

Open load
Copy pickup address
Open maps
Calculate deadhead
Calculate total miles
Calculate RPM
Search broker
Check authority
Check payment information
Return to load board
Write broker email
Wait for response
Compare against another load

With a workflow-embedded decision layer:

Load data received through an authorized API, integration, or supported in-workflow interface → Route calculated → Deadhead calculated → RPM calculated → Broker context retrieved → Risk signals surfaced → Communication prepared → Dispatcher reviews

The important change is not that AI replaces the dispatcher.

The change is that information assembly becomes software work rather than dispatcher work.

Why This Architecture Matters

Freight software has accumulated many specialized systems:

load boards;
TMS platforms;
ELD systems;
mapping software;
email;
broker databases;
accounting tools;
factoring platforms;
safety databases;
document-management systems.

The problem is not a lack of software.

The problem is that the dispatcher often has to connect all of it manually.

An AI decision layer creates a different architecture:

Systems of Data → Decision Layer → Human Judgment → Systems of Execution

That pattern is not unique to trucking. Similar decision-support architectures are appearing in other data-heavy workflows where humans need to make frequent decisions using fragmented information.

Load Boards, Decision Layers, and TMS Solve Different Problems

The easiest way to think about the three systems is:

LOAD BOARD
What freight opportunities are available?
↓
DECISION-SUPPORT LAYER
How does each opportunity fit our economics, constraints, and risk criteria?
↓
DISPATCHER
Which tradeoffs are acceptable right now?
↓
TMS
How do we plan, execute, and manage the selected load?

This is why an AI decision layer should not necessarily be evaluated as a replacement for either system.

Its role is different.

A carrier may continue using DAT or Truckstop for freight discovery.

The same carrier may continue using its existing TMS for execution.

The AI layer sits between them and helps reduce the manual reasoning and data assembly required before a load enters the operational system.

An Example: LoadConnect

LoadConnect is one example of this architecture.

Rather than positioning itself as another load board or a full TMS replacement, it works around the existing dispatch workflow.

Its role is to provide an AI decision layer around load evaluation by bringing together signals such as:

RPM;
deadhead;
route context;
broker information;
factoring context;
fraud-related signals;
communication;
document analysis.

For a deeper look at how this type of system works, see AI Dispatch Software.

The broader idea is more important than any individual product: AI becomes most useful when it connects systems that already contain valuable information and surfaces that information at the moment a human needs to make a decision.

This layered model is likely to matter more as freight software becomes more specialized.

The Future Is Probably Layered, Not Monolithic

There is a recurring assumption in enterprise software that one platform will eventually replace every specialized tool.

Freight may move in the opposite direction.

The future dispatch stack may look more modular:

Marketplace Layer → Decision Layer → Execution Layer → Financial Layer → Analytics Layer

Each system can continue doing what it does best. AI becomes the connective layer that interprets data across them.

For dispatch teams, that may be more practical than replacing an entire TMS or abandoning the load boards where freight is already available.

The most important question therefore may not be:

Which AI system can automate dispatch?

It may be:

Where in the dispatch workflow does AI reduce the most decision friction without removing useful human judgment?

That is the architectural problem worth solving.

How We Decide What NOT to Automate

Dimitrii Khristoforidi — Fri, 28 Aug 2026 14:50:43 +0000

A follow-up on building an AI copilot for freight dispatch

TL;DR: We don't decide whether to automate a task based on how repetitive it looks. We look at four things: how much the right decision varies between real-world cases, the cost of being wrong, whether the task’s value comes from speed or judgment, and how quickly a wrong output would be detected.

Together, those determine whether our AI dispatch copilot should suggest, ask for confirmation, act autonomously, or stay out of the way.

Automation is not the default win condition

There's an assumption baked into a lot of AI product thinking right now: if a task can be automated, it should be. Manual is friction, automation is progress, ship it.

We don't work from that assumption anymore. Not because automation is bad - obviously most of what we build is automation - but because treating "can we automate this" as the only question skips the one that actually matters: should this specific task be automated, given what happens when it's done wrong, and how often "wrong" looks different each time.

That second part - how often "wrong" looks different - turned out to be the real hinge. A task can be low-stakes and still be a bad automation candidate if every instance of it is weird in its own way. And a task can look scary and still automate well if the failure mode is boring and consistent.

The four questions we actually ask

We stopped trying to have one big "automation philosophy" and instead run four concrete questions per feature. None of them require ML expertise. They require someone who understands the actual operational process and is willing to ask honest questions about it.

1. How much does the right decision vary from one instance to the next?

Extracting predefined fields from a rate confirmation can be relatively consistent once the prompt and extraction logic have been properly refined. In practice, reaching that level of consistency may require several rounds of prompt improvement and validation. Even then, the task is not entirely straightforward: the total may combine linehaul, fuel surcharge, accessorials, different currencies, or handwritten adjustments.

High-variance tasks are different. Negotiating detention time with a broker who's annoyed about a missed appointment involves interpreting tone, the history with that broker, and how much leverage the carrier actually has that week. Two instances of what appears to be “the same task” can therefore require completely different judgment calls.

Low decision variance → a potentially good automation candidate, provided the inputs are reliable, the output can be validated, and failures are detectable.

High decision variance often means the task cannot be made reliably automatable through prompt engineering alone. It may require richer context, structured rules, specialized tools, historical data, or human review to handle different scenarios consistently.

2. What does a wrong output cost, and does the cost scale with volume?

This sounds like the reversibility question from our earlier post, “Where Should an AI Agent’s Autonomy End?”, but it's slightly different — it's about whether errors compound. Auto-flagging a possible detention clause mismatch that turns out to be a false positive costs a dispatcher thirty seconds of annoyance. Auto-sending a rate counter-offer that's off by a meaningful margin, at volume, across dozens of loads a week, doesn't just cost thirty seconds each time - it can quietly damage a broker relationship you didn't even know was at risk until the relationship is already gone.

Even small errors create operational costs, and those costs accumulate as volume grows. Some errors scale roughly in proportion to the number of occurrences, while others create disproportionate or delayed damage by eroding trust, reputation, or a counterparty’s willingness to work with you again.

3. Is the value of doing it mostly about speed, or mostly about judgment?

Some manual tasks are slow because nobody's built the tooling yet - that's a straightforward automation opportunity. Others are slow because they require judgment, and the slowness isn't the bug; it's the mechanism by which a human catches something a faster process would have missed.

Confusing these two is probably the single most common mistake in early-stage automation decisions: “this takes a dispatcher ten minutes” gets read as “this is inefficient” instead of “this is where the actual thinking happens.”

4. How quickly and reliably will we detect a wrong output?

A reversible error is only safe if someone notices it in time. Some failures become obvious immediately — through a validation check, a dispatcher catching the issue, or a product metric moving in the wrong direction. Others may surface only days or weeks later, through a damaged broker relationship, a lost customer, or a pattern of operational friction that is difficult to trace back to a specific automated decision.

This matters beyond the product itself. An incorrect output can affect how a dispatcher communicates with a broker and, if it goes unnoticed, influence the relationship between them.

The longer and less reliable the feedback loop, the less autonomy we should give the system.

This is also how we think about agent autonomy: it's not a property we give an agent once. It's something we earn task by task.

Autonomy should be earned per task, not granted to the agent as a whole.

That's why we don't think about an AI copilot as simply being “autonomous” or “not autonomous.” Different tasks can - and should - have different levels of autonomy.

We start with decision variance and failure cost, then adjust the level of autonomy based on how much judgment the task requires and how quickly and reliably failures can be detected.

That's the approach we're taking with LoadConnect's dispatch workflow automation, where different tasks can have different levels of autonomy depending on decision variance, failure cost, and the need for human judgment.

A framework, roughly

We use decision variance and cost-if-wrong as the first pass — effectively a 2×2 for determining the initial level of autonomy:

Low variance + Low cost if wrong → Automate freely
Low variance + High cost if wrong → Automate + confirmation
High variance + Low cost if wrong → Draft / suggestion + human finalizes
High variance + High cost if wrong → Keep manual

The matrix is only the first pass. Whether the task’s value comes primarily from speed or judgment acts as a separate filter: if judgment is central to the task, we lower the level of autonomy by one step.

Detection speed is another. Even a low-cost, reversible failure deserves less autonomy if we are unlikely to notice it quickly and reliably.

In practice, these autonomy levels map to different system designs. “Automate freely” still means validation and logging. “Automate + confirmation” means generating a structured action but requiring explicit dispatcher approval. “Draft / suggestion” means the model can prepare the response but cannot execute it. “Keep manual” means AI may retrieve context or summarize information, but the actual decision remains outside the agent.

The more autonomy we give a task, the more explicit its validation, logging, and failure signals need to become.

The goal isn't maximum automation. It's the right level of automation for the task.

The high-variance, high-cost category is smaller than people expect. But it is also where the “automate everything” instinct can do the most damage. These tasks often look repetitive and well-defined from a distance, but become much less predictable once you examine real-world cases and the consequences of getting them wrong.

An example that goes the "wrong" way on purpose

Most of what I write about tends to be examples where we correctly chose not to automate something. It's worth including one where we got it wrong first.

Early on, we built a feature that automatically sent a standard response when a load’s pickup window changed slightly — a templated “here’s the updated appointment, please confirm” type of message. On paper, it looked like a low-variance task: a time changed, so send an update.

In practice, the reasons behind those pickup window changes turned out to be far more varied than the template assumed. Sometimes the change was routine. Other times, it signaled a larger issue with the shipper that the dispatcher needed to address directly rather than paper over with an automated message.

We had measured variance at the surface of the task — a timestamp changed — instead of at the level of the decision underneath it, where the real variation was.

Surface-level variance ≠ decision-level variance.

We walked the automation back to a suggestion the dispatcher reviews before sending, rather than an auto-send.

The lesson wasn't "don't automate messaging." It was: **measure variance at the level that actually matters, not the level that's easiest to measure. **A timestamp is easy to check for variance. The judgment call underneath it isn't, and that's usually the one that counts.

What this costs us

Being disciplined about this has a real cost, and it's worth naming instead of glossing over: it means shipping fewer flashy "the AI just does it for you" features than we technically could. Some AI demos look more impressive because they auto-execute actions that we deliberately keep behind a confirmation step.

We've made peace with that trade. A demo that auto-books a load looks great in a thirty-second clip. It looks a lot worse the first time it books the wrong one, and in freight, that first time is a phone call and a canceled contract, not a bug report.

The checklist, if you want to steal it

Before we automate a task fully - not just assist with it, actually remove the human step - we want honest answers to:

If we sampled a representative set of real instances — including rare and high-impact edge cases — would they require essentially the same decision, or are meaningfully different situations hiding under the same label? Are we measuring variance at the level of the actual decision, rather than just the surface of the task?
Does a wrong output stay a small, contained mistake, or can its financial, operational, or reputational cost compound as volume grows?
Is the current “slowness” of this task mostly wasted motion, or is it where a human is actually doing the hard part?
If the system gets this wrong, how quickly and reliably will we know — and who is likely to notice first, us or the customer?

That last one matters more than it sounds. Some bad automation decisions surface immediately, in your own metrics. Others surface three weeks later, in a broker's inbox, and by then it's not really a product decision anymore - it's damage control.

Closing thought

"What should we automate" gets asked constantly in AI products right now. "What should we deliberately not automate, and why" gets asked a lot less, and it's usually the more useful question - because it's the one that forces you to actually understand the task instead of just measuring how often it repeats.

What's one task your team has deliberately kept human-in-the-loop - and what made you decide not to automate it?

Where Should an AI Agent's Autonomy End?

Dimitrii Khristoforidi — Fri, 14 Aug 2026 12:13:38 +0000

Notes from building an AI copilot for freight dispatch

TL;DR: Every few weeks, another "AI agent" launches that can act on someone's behalf — booking things, sending things, updating things. The interesting engineering question isn't "what can it do?" It's "where should we draw the line, and why?" This post is about how we thought through that line while building the AI assistant inside LoadConnect, a dispatch tool that helps truck carriers and dispatchers analyze loads, rate confirmations, and carrier information.

The wrong question

When people talk about AI agents, the conversation usually starts with capability.

Can it read a document? Fill out a form? Call an API and take an action without a human in the loop?

That's a fun question to build for. It's also, in my experience, the wrong first question.

A more useful question is: what does the agent have access to, what can it do with that access, and what happens when it gets something wrong?
These are related, but they're not the same thing:

Capability - what the model can understand, generate, or reason about.
Access - what data, sessions, and systems the agent can technically reach.
Autonomy - what the agent is allowed to do with that access without human confirmation.

You can have a highly capable model with almost no autonomy - it analyzes and recommends, but never acts. You can also have a relatively simple system with dangerously high autonomy because it can make changes on its own.

So the risk profile isn't determined by model capability alone. It depends on the combination of access, autonomy, likelihood of failure, and potential impact.

Two axes, not one

Capability still matters, but it's not the main architectural lever we can control. For the system we were building, the most useful way to reason about risk was to map access and autonomy separately:

Low Access + Low Autonomy → Low Risk
Low Access + High Autonomy → Moderate Risk
High Access + Low Autonomy → Moderate Risk
High Access + High Autonomy → High Risk

The dangerous quadrant isn't necessarily "highly intelligent AI." It's a system that combines broad access with broad autonomy.

Capability affects how well an agent can perform a task - and how sophisticated its mistakes might be. But access and autonomy determine how far those mistakes can propagate.

A highly capable model with access limited to a single document and no ability to take external actions has a relatively small blast radius. A much simpler system can become significantly riskier if it can access sensitive data and make irreversible changes without confirmation.

That distinction became one of the most useful mental models for us when deciding what our assistant should - and shouldn't - be allowed to do.

Why this isn't abstract in freight

Dispatch is a good stress test for this idea because the cost of a wrong autonomous action is immediate and expensive. If an agent misreads a rate confirmation and books the wrong appointment window, that's not a UX bug - it's a missed delivery, a detention fee, or even a damaged relationship with a broker.

So when we were designing the AI assistant, "what should it be allowed to decide on its own" wasn't a philosophical question - it was a product requirement with real financial consequences.

Consider a rate confirmation. Before signing or otherwise accepting the final terms, the dispatcher reviews it to verify that it matches the negotiated load. The assistant helps with the understanding part - extracting the rate and mileage, calculating RPM, flagging detention terms, catching inconsistencies between the document and the load details, summarizing what deserves attention. It does not touch the commitment part - it doesn't accept the load, message the broker, change the appointment, or modify the booking on the carrier's behalf.

The distinction isn't about whether the model could technically perform those actions. It's about whether the system should give the model the permissions required to perform them. We want the assistant to reduce the work required to make a decision - without quietly becoming the decision-maker.

That split turned into two separate design decisions we now make independently for every feature:

What information does this feature actually need to see to do its job - not what would be convenient, but the minimum required.
What is the agent allowed to do with what it finds - surface it, or act on it?

Treating these as one decision ("give it access and let it be smart about the rest") is, in my opinion, where most agent projects get into trouble.

Access: a deliberately narrow scope

The basic architecture is intentionally boring:

User selects a document or load
↓
Relevant content is extracted
↓
Scoped AI task is created
↓
AI analyzes the available information
↓
Recommendation / result is returned
↓
Human decides what happens next

The important part is what isn't in this flow. The agent doesn't get access to the user's authenticated browser session, cookies, or credentials. It doesn't continuously observe other tabs or websites. It doesn't have a general-purpose action layer that can execute arbitrary changes.

A simplified permission model looks more like this:

AI Assistant
├── Read selected document
├── Analyze extracted data
├── Calculate relevant metrics
└── Recommend an action

✕ Access credentials
✕ Read unrelated browser sessions
✕ Monitor activity in the background
✕ Send external messages
✕ Book or modify loads
✕ Change external systems

This creates a useful property: even if the model produces an unexpected output, the set of things that output can affect is already constrained by the architecture - not by a rule the model is trusted to follow.

The instinct when building an assistant is to wire it into everything, because more context makes the model perform better in demos. The problem is that "better in demos" and "safe in production" can pull in opposite directions. The rule we settled on is simple to state and annoying to actually follow: an agent should only touch what its current task needs, for as long as the task requires it. No background processes, no session or credential access, no cross-site visibility, no accumulating data "because it might be useful later."

None of this is exotic security engineering - it's mostly saying no to permissions during the design phase instead of restricting them with policy afterward. Saying no early is a lot cheaper than walking back scope creep once a feature ships and people depend on it.

Autonomy: think in terms of blast radius, not just error rate

The second axis is where it gets more interesting, because autonomy is about trust as much as it is about architecture.

There's a meaningful difference between an agent that says "this rate confirmation has a mismatched detention clause, you should look at it," and one that silently updates the record itself. Both use the same model. Both might even be equally reliable most of the time. But only one of them leaves a human in a position to catch the cases where the model is wrong before that mistake becomes a real-world consequence.

Not every model error has the same consequence, so it's worth separating capability from what happens when that capability fails:

Extract information → Misreads a rate → Incorrect recommendation
Calculate RPM → Uses the wrong mileage → Poor dispatch decision
Flag a contract issue → Misses a clause → Risk goes unnoticed
Send a broker message → Sends incorrect information → External commitment
Change an appointment → Picks the wrong time → Operational disruption
Book a load → Selects the wrong load → Financial and reputational impact

A wrong recommendation can be reviewed and may be caught before it produces an external consequence. A wrong external action may already have created a commitment before anyone notices. That's why we think about autonomy partly in terms of reversibility: the more consequential or irreversible an action is, the stronger the case for keeping a human confirmation step - regardless of how confident the model is.

A useful rule of thumb that came out of this: analyze → recommend → confirm → execute. The first two steps are where an AI assistant provides real leverage. The last two are where human responsibility stays, on purpose.

That doesn't mean every AI action needs a confirmation dialog - low-risk, reversible operations can often run on their own. But when an action creates an external commitment or is hard to reverse, the default should be human confirmation. The question isn't "can the model do this?" It's "what happens if the model is wrong and nobody stops it?" That question changes the design discussion considerably.

In our case, it led to a deliberately conservative boundary: the agent analyzes, flags, and recommends. It does not approve, execute, or take ownership of an outcome, because accountability must remain assigned to identifiable people and organizations; it cannot be delegated to the model. If something goes wrong, "the agent decided" isn't an answer anyone in freight - or honestly, anywhere - is going to accept.

We're building LoadConnect as an AI dispatch copilot that helps dispatchers analyze information, surface risks, and make better decisions while keeping higher-risk actions and external commitments under human control.

A framing that's helped more than any specific rule

The framing we kept coming back to, especially when a new feature request tempted us to expand scope, was this: don't build a system that's secure because of policy - build one where the risky thing simply isn't possible by design.

A policy says "the agent shouldn't do X." Architecture should make prohibited high-impact actions unreachable by the model, while policy, authorization, monitoring, and data-handling controls address the remaining risks. It's a more boring way to build software. It's also a lot more resilient, because it doesn't depend on every future engineer remembering the rule, or every prompt update preserving the guardrail.

Questions worth asking before you widen an agent's scope

If you're building an AI agent right now, here's roughly the checklist we run through before adding a new capability:

What does the agent actually need to see? Does this feature require a new data source, or would access simply be more convenient?
What's the blast radius if it gets this wrong? A bad recommendation, or an external commitment?
Is this analysis or action? Are we asking the agent to understand something, or to change something?
If it's an action - is it reversible? The harder it is to undo, the stronger the case for human confirmation.
What's the minimum permission required? If the feature works without credentials or persistent sessions, don't add them "just in case."
Do we need this access now, or are we adding it for a possible future use case? If it's the latter, don't add it yet.

The goal isn't to make an agent incapable of doing useful work. It's to make the boundary between what the agent can understand and what it can change explicit - as a product decision, a security decision, and an architectural decision, not something left to a prompt.

None of these questions require exotic tooling to answer. They mostly require being willing to say no to your own feature ideas, which is the actual hard part.

Closing thought

The capabilities will keep expanding. The boundary shouldn't have to move at the same speed.

What an agent can do will keep getting more impressive every quarter. What it should be allowed to do on its own is a much slower-moving, much more durable question - and it's the one that ultimately determines whether people trust the system enough to let it near their real work.

I'm curious how other teams building AI agents are drawing this line internally — especially in domains where a wrong autonomous action has a real, immediate cost. Happy to compare notes in the comments.