Skip to content
Back

Transport files & operations

Rate confirmation: what to include, which template, and why to generate it from the file

The sections of a carrier rate confirmation, where each one comes from in the file, how the French subcontracting model contract fits in, versioning rules and common mistakes.

Updated on 12 October 2026 11 min readBy the Axonovia team
Who is this for?
Freight brokers, freight forwarders, dispatchers and operations managers who subcontract transport to carriers
Question addressed
Know what a rate confirmation must contain and how to produce it without a gap against the shipper’s request or the carrier’s documents.

Short answer

A rate confirmation (also called a load confirmation or carrier confirmation sheet) is the document a freight broker sends to the subcontracted carrier to fix what is being entrusted: the parties and their references, the goods, the locations and time windows, the rate and its conditions (detention, pallets, fuel, insurance), the instructions, the documents expected back, and the prohibition or conditions of re-brokering. It protects the broker only when every section comes from the file and when every change produces a new version that leaves the previous one readable. Vigilo prepares the confirmation from the reconstructed file and flags a missing document or a discrepancy before it is sent.

Key takeaways

  • A rate confirmation has two faces, the shipper’s request and the carrier’s commitment; the template exists to make any gap between them visible.
  • Every section of the template has a precise source in the file; a section filled from memory is a risk, not a time saving.
  • The French subcontracting model contract frames the regular relationship between a transport operator and a subcontractor; it does not replace the per-load confirmation.
  • No confirmation goes out before the carrier’s licence, insurance and compliance certificates have been checked.
  • Every change from the shipper produces a new numbered confirmation or an addendum; the previous version stays readable.

What a rate confirmation fixes, and what it is not

A rate confirmation is the written document by which a freight broker or freight forwarder entrusts a specific load to a subcontracted carrier and sets the conditions of that movement. It records the agreement on one shipment. It is neither the shipper’s request, nor the internal transport order, nor the consignment note or CMR that will travel with the goods. The article on brokerage orders, transport orders and consignment notes covers those distinctions; this one deals with the content of the confirmation and how it is produced.

The confirmation has two faces that must match. On the shipper side, it restates what was requested and quoted. On the carrier side, it turns that request into execution conditions and a buy rate. A time window accepted from the shipper but missing from the confirmation, an accessorial quoted but not assigned, a forgotten temperature requirement: each gap becomes a dispute, uncovered detention or lost margin. The template exists to surface those gaps before sending, not to produce a longer document.

The sections of the template and their source in the file

The table below gives the structure of a rate confirmation as a broker would use it. The third column is the most useful: it states where each piece of information must come from. A section whose source cannot be identified in the file is a section to clarify, not one to complete by habit. Adapt the headings to your master agreement and purchasing terms.

SectionWhy it protects the brokerSource in the file
Parties and references: legal names, company registration, carrier licence number, file and shipper references, contactsPrevents committing to an impersonated carrier; lets the CMR and invoice be matchedVerified carrier record; shipper’s request
Goods: nature, quantity, weight, pallets, packaging, dangerous goods or temperatureFixes what is entrusted, hence the scope of liabilityShipper’s request, dated version
Locations and time windows: addresses, windows, site contacts, access instructionsLimits detention disputes and failed deliveriesShipper’s request; site master data
Rate and conditions: agreed rate and what it includes, free time and detention rate, pallet exchange, fuel surcharge, insuranceStops a carrier invoice from drifting away from the quoteAccepted quote; purchasing terms
Instructions and documents expected: vehicle registration, tracking, incidents, signed CMR, return deadlineProvides the basis for invoice control and document follow-upShipper requirements; internal procedure
Re-brokering and acceptance: prohibition or written consent per load, acceptance method, version and dateReduces double brokering risk; proves what was acceptedMaster agreement; versioning rule

What the French subcontracting model contract frames, and what it leaves to the confirmation

The French Transport Code provides that, absent a written agreement, the relationship between the parties to a road haulage contract is governed by model contracts set by regulation. For transport performed by subcontractors, the model contract is annex IX to the regulatory part of the code, attached to article D. 3224-3, in the version introduced by decree no. 2019-695 of 1 July 2019 and in force since 1 October 2019 (version consulted on Légifrance on 12 October 2026). It covers the regular and significant relationship between a transport operator and a subcontractor, and it expressly excludes “spot” operations entrusted occasionally.

In substance, the model contract provides among other things that the subcontractor sends the operator, before the contract is concluded, a copy of its valid transport licence, and that it periodically supplies the documents related to the fight against undeclared work, according to the threshold and frequency set by the French Labour Code. It lists items that may be agreed in writing or electronically, including execution procedures and how transport documents are transmitted. It provides that the subcontractor performs the transport itself and may not subcontract to a third party without the operator’s prior written consent, load by load, except in circumstances beyond the parties’ control. The rate is negotiated when the contract is concluded.

Two consequences for the broker. The confirmation does not replace the master agreement: it is the execution document for one load, and the master agreement or purchasing terms set the general regime. For an occasional load outside a regular relationship, the general model contract in annex II of the same part of the code may apply absent a written agreement; the confirmation is then often the only written document specific to the load, which makes completeness even more valuable. Confirm this reading with counsel.

Producing a confirmation from the file: the sequence

A confirmation written from memory, or copied from an earlier confirmation for the same carrier, repeats the previous one’s mistakes and ignores what changed in the request. The sequence below starts from the file: each section is filled from an identified source, then the confirmation is compared with the shipper’s request before it leaves. The time saved comes from the absence of rekeying and rework, not from a lighter check.

  1. 01
    Freeze the shipper’s request

    Retain the dated version of the request (email, portal, EDI), its references and its explicit requirements.

  2. 02
    Attach the accepted quote

    Link the buy rate, what it includes (detention, pallets, fuel, accessorials) and the carrier that offered it.

  3. 03
    Vet the carrier before anything is sent

    Check that the licence, insurance, compliance certificates and company registration are present and valid, that contact details come from the carrier record and not from the inbound email, and review its history or score.

  4. 04
    Generate the confirmation section by section

    Fill each section from its source, with no free typing; leave empty what has no source.

  5. 05
    Compare the two faces

    Reread the confirmation line by line against the shipper’s request: windows, quantities, constraints, accessorials, documents expected.

  6. 06
    Send, obtain acceptance and attach it

    Send through the authorised channel, receive the signed return or acknowledgement, check that it refers to the version sent, and attach it to the file.

Versions: every change from the shipper produces a new confirmation or an addendum

The shipper moves a window, adds two pallets, changes the delivery address. Every accepted change must produce either a new confirmation with a version number, or an addendum that references the version it modifies. The previous version stays readable in the file: it is what explains why the carrier invoiced detention or declined a window. Overwriting the original document destroys the evidence of what was agreed at the moment the carrier committed.

The versioning rule is written once and applied to every file. It states who may issue a new version, what distinguishes an addendum from a new confirmation, and what happens when the change arrives after the vehicle has departed. In that case, the instruction given to the carrier is logged with its time and channel, then regularised by an addendum, even if the load is already complete.

  • Number every version, date every dispatch and show what changes.
  • Obtain a fresh acknowledgement from the carrier for any version that changes the rate, the window or the goods.
  • Match the carrier invoice to the version in force at the time of execution.

What Vigilo prepares, checks and keeps on the confirmation

Vigilo prepares the confirmation from the reconstructed brokerage file: the shipper’s request, the accepted quote, the selected carrier and its documents. It fills each section from its source and checks consistency between the two faces: a window, a quantity or an accessorial present in the request and absent from the confirmation is flagged before sending. If the selected carrier has a missing, expired or inconsistent document, or if its score shows an unfavourable signal among those measured, sending is held and the dispatcher receives the reason.

Vigilo keeps every version of the confirmation and its addenda, attaches the carrier’s acknowledgement or signed return to the relevant version, and flags, before sending, a suspicious email such as a domain close to a known one or an unusual change of bank or contact details. Sending remains an authorised action within the scope validated with the teams. Ambiguous cases, a new carrier, an unexplained gap between quote and confirmation, a reply that alters the conditions, go back to the broker with their context. Vigilo does not decide to award a load and does not certify a carrier’s compliance.

Common mistakes to check before sending

The mistakes below appear in most disputed files. They do not stem from a lack of trade knowledge but from a confirmation produced outside the file, under time pressure, often by a dispatcher handling several requests at once. The safeguard proposed for each one is a production rule, not an extra check bolted on at the end of the chain.

MistakeWhat it exposesSafeguard
Confirmation sent before the carrier’s documents are checkedCommitment to a carrier without a valid licence or insurance; exposure under the French principal’s duty of vigilanceDocument status blocks sending while any document is missing or expired
Gap between the confirmation and the shipper’s requestService not performed, uncovered detention, lost marginLine-by-line comparison before sending
Amended version returned by the carrier and not rereadConditions accepted by silence: rate, detention, re-brokeringCompare the return with the dispatch; accept or reject explicitly
Re-brokering section missingDouble brokering without written consent, uncertain recourseStandard clause in the template; written consent load by load
Shipper change applied verballyOutdated confirmation later used as the basis for the invoiceSystematic addendum, even after execution
Contact details taken from the inbound emailCarrier identity theft, diverted paymentContact and bank details taken from the verified carrier record

Frequently asked questions

Direct answers

What should a rate confirmation contain?

The parties and their references (including the carrier’s licence number), the goods, the locations and time windows with site contacts, the rate and what it includes (detention, pallets, fuel, insurance), the instructions and documents expected, the prohibition or conditions of re-brokering, the acceptance method, a version number and a date.

Is a rate confirmation legally required?

This article does not assert a legal requirement of form. The French Transport Code provides that, absent a written agreement, regulatory model contracts apply. In practice, the confirmation is the written proof of what was entrusted and at what rate; without it, the broker depends on the model contract and on its ability to prove the terms some other way.

What if the carrier returns an amended confirmation?

Do not file it as accepted. Compare the return with the version sent, identify every change (rate, detention, window, re-brokering), then accept it through a new numbered version or reject it explicitly. An amended return that nobody rereads becomes a condition accepted by silence.

Can a broker prohibit the carrier from re-brokering?

The French subcontracting model contract provides that the subcontractor performs the transport itself and may not subcontract to a third party without the operator’s prior written consent, load by load, except in circumstances beyond the parties’ control. Restating that rule in the confirmation and defining how written consent is given avoids ambiguity; the drafting of the clause belongs in the master agreement and with counsel.

What does Vigilo do on the rate confirmation?

Vigilo prepares the confirmation from the reconstructed file (shipper’s request, quote, selected carrier and its documents), checks consistency between the request and the confirmation, flags before sending a missing document or an unfavourable score signal, keeps every version and attaches the carrier’s acknowledgement. Sending remains an authorised action within the scope validated with the broker.

Sources

Next step

Map this workflow in your operation

Let us start with a real flow, the tools already in use and the decisions that still require context.

Assess this workflow