Fixed quote after a free call

Rate confirmation and load tender intake for trucking dispatch

Every booking arrives in its own format: a broker's rate confirmation PDF, a shipper's spreadsheet, an email with three stops typed in the body. We build a workflow that reads them from the bookings inbox into a consistent draft load, checks it against the customer's usual details, flags missing references, windows or equipment and puts it in front of the dispatcher to accept before anything reaches the TMS. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why rate confirmations slow trucking dispatch

Dispatchers spend a surprising part of the day retyping. Pickup and delivery addresses, appointment windows, PO and BOL numbers, commodity, weight, equipment and special instructions are copied from PDFs and emails into the TMS, often while the phone is ringing.

Mistakes show up later and cost more: a driver at the wrong dock, a missed appointment, a rate that does not match the confirmation when the invoice goes out. The details are usually in the document; the problem is getting them in accurately and noticing when something is missing.

What we build

What our rate confirmation automation includes

Bookings inbox watcher

Emails and attachments in the shared bookings inbox are collected into one queue, with duplicates and replies grouped.

Document reading

Rate confirmations, tenders and spreadsheets are read into one draft load format: stops, windows, references, equipment, commodity, weight and rate.

Gap and mismatch checks

Missing appointment times, references or equipment, and rates that differ from the customer's agreed lane rate, are flagged rather than guessed.

Dispatcher approval screen

A simple review list where the dispatcher corrects and accepts or rejects each draft.

Into the TMS

Accepted loads are created through the TMS API or import file, with the original document attached.

Booking confirmation

An approved confirmation goes back to the customer or broker once the load is accepted.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Booking arrives

    A rate confirmation, tender or booking email lands in the shared inbox.

  2. 02 Automated

    Draft load built

    The document is read into a draft load with stops, windows, references and rate.

  3. 03 Automated

    Gaps flagged

    Missing details and rate mismatches are highlighted on the draft.

  4. 04 Office review

    Dispatcher checks

    The dispatcher corrects the draft and confirms equipment, capacity and timing.

  5. 05 Dispatcher or safety manager decides

    Accept or decline

    Whether to take the load, and with which truck and driver, is the dispatcher's decision.

How it behaves

How load tender intake behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A booking confirmation once the load is accepted
  • A quick question when a reference or window is missing
  • Fewer surprises at pickup

What dispatch sees

  • A review list of draft loads with the source document beside each
  • Missing details and rate mismatches highlighted
  • Accepted loads created in the TMS without retyping

What the automation does

  • Watches the bookings inbox and groups threads
  • Reads documents into one draft format
  • Never creates a load without a dispatcher's approval

Edge cases and fallbacks

Revised rate confirmation arrives
Matched to the earlier draft and the changes highlighted.
Handwritten or scanned booking
Read where legible; otherwise flagged for manual entry.
Rate differs from the agreed lane rate
Flagged to the dispatcher, never corrected automatically.
AI provider or TMS outage
Emails stay in the inbox as before and dispatch is alerted to key loads manually.

Architecture

Rate confirmation intake for dispatch at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Bookings inbox PDFs and emails n8n workflow Queue and group Document reading Fields extracted Checks Gaps and rates Dispatcher Accepts or fixes TMS Load created
  • Input
  • Logic and services
  • AI step
  • People
  • Data

How it flows

  1. 1 Booking emails and attachments are collected from the shared inbox and grouped by thread.
  2. 2 Each document is read into a draft load with stops, windows, references, equipment and rate.
  3. 3 Checks flag missing details and rates that do not match the agreed lane rate.
  4. 4 The dispatcher reviews and accepts the draft, and the load is created in the TMS with the original attached.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Rate confirmation & load tender intake project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Booking sources, the top customer and broker formats, TMS fields and import options.

  2. 02

    Design

    2 to 3 days

    Draft load format, checks, approval screen and confirmation wording.

  3. 03

    Build

    1 to 2 weeks

    Inbox watcher, document reading, checks, review list and TMS import.

  4. 04

    Shadow run

    About 1 week

    Drafts are built for real bookings while dispatch keys loads as usual, and we compare field by field.

  5. 05

    Launch

    1 to 2 days

    Start with the most common formats, then add the rest.

  6. 06

    Support

    Ongoing

    New customer formats and field changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Microsoft Graph or Gmail API Claude, Gemini or OpenAI for document reading Your TMS API or import (McLeod web services, Rose Rocket or other) Google Sheets or a small review screen

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Formats, fields, checks and the written specification.

    $250 – $450

  • Build

    Inbox watcher, document reading, checks and review list.

    $450 – $1,250

  • Integrations

    Mailbox, TMS import or API and confirmations.

    $150 – $400

  • Testing and shadow run

    Field-by-field comparison on real bookings.

    $100 – $250

  • Launch and training

    Switch-on and dispatcher walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. EDI 204 tenders through a VAN or a two-way TMS link may need a second workflow. AI usage and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • AI model usage: Billed by the provider per use; reading a booking document is usually a small cost per load.
  • n8n: Self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

Rate confirmations contain personal data

Driver names, phone numbers and contact details on confirmations are personal data under GDPR and UK GDPR, so the workflow keeps only the fields dispatch needs.

Source: gdpr-info.eu

US: hours of service still decide capacity

FMCSA hours-of-service rules limit when drivers can drive, so accepting a load stays with the dispatcher who knows each driver's available hours.

Source: www.fmcsa.dot.gov

US: records of duty status

Carriers keep records of duty status and supporting documents for at least six months, and booking documents can be supporting documents, so originals stay attached to the load.

Source: www.law.cornell.edu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Rate confirmation & load tender intake questions, answered.

Most broker and shipper rate confirmations follow a handful of layouts, and modern document reading handles them well. Each draft shows its source document, and anything the reader is unsure about is flagged for the dispatcher.

It automates the paperwork side of dispatch. Assigning trucks and drivers, checking hours and saying yes to a load stay with the dispatcher.

EDI 204 tenders usually arrive through your TMS or a VAN already. We can add them to the same review list, or leave them where they are and focus on emails and PDFs.

The same document reading works on bills of lading, so BOL numbers, pieces and weights can be checked against the load. We usually add it to the POD workflow.

Only after a dispatcher accepts the draft. Where your TMS has an API or import file we create the load from the approved draft; otherwise the draft is laid out for quick copying.

During the shadow run we compare every field against what dispatch keyed. After launch, track corrections per draft, time from email to load created and loads with missing references.

Free 20-minute call

Want this for your logistics & haulage?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call