All Learn guides Open LogicCalc
LogicCalc Learn Beginner

European Road Freight Documents & Operations Guide

A practical guide to transport orders, CMR, proof of delivery, T1/T2 customs transit and ADR paperwork—from dispatch to shipment closure.

Beginner

Road Freight Administration for Beginners

A practical first-day guide to the administrative side of European road freight: orders, references, loading updates, transport documents, delivery proof, invoicing and archiving.

What road-freight administration actually covers

The administrative job starts before the truck moves. A dispatcher or transport administrator turns a commercial transport order into an executable shipment: the right vehicle goes to the right loading place, with the right reference, at the right time, and everyone can later prove what happened.

The safest way to work is to treat the shipment as one continuous record. The order defines the job, status updates show how it progressed, transport documents prove handovers, written exception records explain deviations, and the final POD package supports invoicing and archiving.

A shipment from order to archive

1. Read the order before dispatch

Check the parties, exact loading and delivery addresses, date or time windows, cargo description, weight and loading metres where relevant, required equipment, booking or reference numbers, agreed operational instructions and any special document requirements. Do not rely on a short message if the formal order says something different.

2. Confirm the job is executable

Before sending the truck, verify the loading and unloading references, contact people, vehicle or trailer requirement, driver details and any access instructions you actually need. If information is missing or contradictory, resolve it before arrival rather than after the truck is waiting at the gate.

3. Track the important milestones

Record dispatch, arrival, loading completion, departure, delivery and any other milestone that matters to the customer or your own workflow. Keep timestamps and the source of the update. A status should come from a real confirmation, not from an assumption based on planned time.

4. Manage exceptions in writing

Delays, waiting time, damage, shortages, rejected cargo, wrong references and address changes should create a written trail. Record what happened, when it happened, who reported it, what evidence exists and which instruction was received. This is much easier than reconstructing the event days later.

5. Close the shipment properly

After delivery, collect the accepted proof of delivery, review remarks before sending documents to invoicing, attach evidence for agreed extra charges where relevant, and store the final document set under the correct shipment reference. A delivered truck is not automatically an administratively closed shipment.

Worked example: one FTL shipment

A customer orders one full truck from Munich to Milan. Before dispatch you confirm the loading reference, loading window, consignee address and contact. The driver reports arrival and later sends a loading confirmation. During the trip a two-hour delay develops; you record the time, reason and customer notification. At delivery, the consignee signs the CMR without reservations. You attach the signed delivery document to the shipment, check whether the delay created any agreed extra cost, and only then move the file to invoicing. The value is not the number of messages sent; it is that the entire shipment can be reconstructed from the order, status history and documents.

Common beginner mistakes

  • Dispatching from a chat message without checking the formal order
  • Treating planned arrival time as a confirmed status
  • Keeping a changed loading reference only in someone’s personal chat
  • Sending a POD to invoicing without reading remarks or reservations
  • Closing the file while waiting-time, damage or other exceptions are still undocumented
Open LogicCalc →
Daily workflow

How to Read a Transport Order Step by Step

Before accepting or dispatching a load, read the transport order in a consistent sequence. The order is the operational and commercial brief for the shipment, so missed details can become wrong trucks, missed slots, rejected cargo, unapproved costs or payment disputes.

What a transport order is and why the reading sequence matters

A transport order is the written brief that turns a commercial agreement into an executable shipment. Depending on the company it may arrive as a PDF, portal order, email attachment or structured booking, and its exact format is not standardised across Europe. What matters operationally is that it identifies the shipment, the parties, the stops, the cargo, the service requirements and the agreed commercial conditions.

Do not confuse the transport order with the CMR consignment note. The order tells your operation what has been booked and under which instructions; the CMR is a transport document used during carriage. A well-run dispatch process reads the order before the truck is committed, records later amendments, and can show which written instruction was valid when a decision was made.

A reliable order-reading workflow

1. Start with identity and parties

Confirm the order or booking number, customer reference, shipper, consignee, contracting party and the company that sent the order. Keep customer references separate from your own internal trip number. If a subcontracted carrier will physically move the load, make sure the operational file still shows who is contracting whom.

2. Read the route as a sequence of stops

Check every loading, intermediate and unloading address, country, date, time window, booking slot, contact and site reference. Do not stop at the city name. A correct route to the wrong warehouse gate is still a failed instruction. For multi-stop work, verify the order of stops as well as each individual location.

3. Check cargo against the vehicle

Read the goods description, package or pallet count, dimensions, weight, loading metres or volume where relevant, stackability and any handling restriction. Then match those facts to the required trailer type, payload, internal dimensions, temperature control, loading access or other equipment. If the order only says standard trailer but the cargo data suggests otherwise, clarify before dispatch.

4. Find operational and document requirements

Look for loading references, customs or transit instructions, CMR copies, POD requirements, pallet-exchange instructions, ADR information, seals, temperature records, driver identification, site PPE or other shipment-specific requirements. A requirement hidden on page two is still a requirement, so read attachments and special-instruction fields rather than only the first page.

5. Read the commercial section before accepting the job

Confirm the agreed freight rate, currency, what is included, known extras, waiting-time rules if stated, payment term, invoicing reference and any condition tied to documents. Separate what is operationally required from what is commercially chargeable. Never assume an extra will be paid just because it created a cost.

6. Resolve conflicts and record amendments

Compare the formal order with later emails, portal updates and messages. If an address, slot, cargo quantity, rate or other material detail changes, get a clear written confirmation and keep it with the shipment record. Do not silently overwrite the old instruction in a way that makes the history impossible to reconstruct.

Worked example: reading one order before dispatch

A customer sends an order for one curtain-sider from Vienna to Lyon. The first page shows a 13:00 loading slot and 24 pallets; the attachment states 23,500 kg, side loading required and a warehouse booking reference. The commercial section shows EUR 1,480 freight, tolls included, 45-day payment and signed CMR required with the invoice. A later chat message says loading moved to 15:00. Before assigning the truck, you confirm in writing that only the slot changed, keep the original order plus the amendment, verify payload and side-loading capability, add the booking reference to the driver instructions and note that tolls must not be charged again. The job is now dispatchable because the operational and commercial picture is consistent.

Common mistakes when reading transport orders

  • Reading only the first page and missing special instructions in an attachment
  • Copying an address but not the booking reference or time window
  • Checking cargo weight but ignoring dimensions, loading access or trailer requirements
  • Assuming the company that sent the order is automatically the shipper or physical carrier
  • Quoting or dispatching from a chat message while the written order contains different terms
  • Treating tolls, waiting time or other extras as automatically billable without checking the agreed conditions
Open LogicCalc →
Documents

What Is a CMR? Road Freight Consignment Note Explained

The CMR framework governs many international road-freight contracts in Europe, and the CMR consignment note is one of the documents a beginner sees most often. Learn what it records and what a dispatcher should check.

What the CMR consignment note is — and what it is not

The CMR Convention creates a common legal framework for many international road-carriage contracts when the goods move between different countries and at least one country is a contracting party. The consignment note is the practical document used to record the shipment and the parties involved.

Under Article 4 of the Convention, the consignment note confirms the contract of carriage, but its absence, irregularity or loss does not by itself invalidate that contract. Operationally, this means the CMR is important evidence and a working record, not a substitute for reading the transport order, customer instructions or applicable legal requirements.

How to check a CMR in an operational workflow

1. Match the CMR to the transport order

Start with identity: sender, consignee, carrier, loading place, delivery place and shipment reference. Compare the document with the order before focusing on stamps or signatures. A perfectly signed document can still belong to the wrong shipment or contain the wrong delivery point.

2. Check the cargo description and quantities

Review the description of the goods, number of packages, marks or numbers, gross weight or other stated quantity and, where relevant, the packing method. These are among the core particulars listed by the Convention. If the document differs from the cargo actually loaded, resolve the discrepancy and record what changed.

3. Check dates, handover and special instructions

Confirm the date and place where the note was made out, the place and date of taking over the goods, and the place designated for delivery. Also review customs or other instructions that are relevant to the shipment. Do not add assumptions to an incomplete document just to make the file look finished.

4. Read reservations and remarks before closing the job

At loading and delivery, remarks can be more important than a clean signature. Damage, shortages, packaging problems, missing packages or other reservations should be read and escalated according to your company process. Never send a POD to invoicing without checking whether the CMR contains a remark that changes the commercial or claims situation.

5. Store the final version with the shipment record

Keep the readable final CMR or accepted electronic record together with the order, status history and other delivery evidence. The document should be easy to retrieve by shipment reference. If several vehicles, cargo lots or document versions exist, make it clear which record belongs to which movement.

Worked example: one cross-border delivery

A carrier moves 24 pallets from Austria to Italy. The dispatcher compares the CMR with the transport order: consignor, consignee, carrier, loading address, delivery address, 24 packages and declared gross weight all match. At delivery, the consignee signs but adds a remark that one pallet has visible packaging damage. The dispatcher does not treat the signed CMR as a “clean POD”. The remark is preserved, the customer is informed, photos are linked to the shipment file and the issue is handed to the responsible claims workflow before invoicing is treated as complete.

Common CMR mistakes in daily operations

  • Checking only whether the document is signed
  • Assuming a signed CMR automatically means delivery without reservations
  • Ignoring differences between the transport order and the goods or addresses shown on the CMR
  • Editing or recreating a CMR later without preserving what was actually recorded at handover
  • Using the CMR as the only source of truth for customs, dangerous goods or contractual instructions
Official reference

For regulated or convention-based topics, verify the current requirements with the responsible authority or competent specialist.

https://unece.org/trade/documents/2023/10/executive-guide-e-cmr
Open LogicCalc →
Documents

What Is POD in Logistics? Proof of Delivery Explained

Proof of Delivery, usually shortened to POD, is the evidence that a shipment reached the consignee. Depending on the workflow, it may be a signed CMR, delivery note or another accepted delivery record.

What POD actually proves

A Proof of Delivery is the evidence used in a transport workflow to show that the shipment was delivered to the receiving party. There is no single universal POD document for every European road-freight movement: depending on the customer, carrier and process, the accepted proof may be a signed CMR, delivery note, warehouse receipt, electronic signature, timestamped ePOD record or another agreed delivery confirmation.

For operations, the important question is not whether a file is called “POD”, but whether it clearly links to the correct shipment and shows an acceptable delivery event. A dispatcher should be able to connect the delivery evidence to the transport order, consignee, delivery location, date and any remarks that could affect claims or invoicing.

POD workflow from delivery to invoicing

1. Match the POD to the shipment

Check the order number, booking reference, vehicle or shipment reference and destination. A signed document that cannot be matched confidently to the transport is not useful evidence.

2. Check the delivery event

Confirm delivery date and, where relevant, time, receiving company or person, signature/stamp or the electronic confirmation required by the process.

3. Read every remark before closing

Look for damage notes, shortages, pallet discrepancies, waiting-time remarks, refused goods or reservations. A signed POD with negative remarks is not the same as a clean delivery.

4. Escalate exceptions immediately

If the POD contains damage, shortage or refusal, inform the responsible customer/forwarder and keep photos, messages and supporting documents together with the shipment record.

5. Release the shipment for billing only when complete

Store the final accepted POD under the correct reference. If the commercial process requires POD before invoicing, do not send the job to billing until the required evidence is present and exceptions are documented.

Example: delivered, but not “clean”

A truck delivers 20 pallets. The receiver signs the CMR but writes that one pallet is visibly damaged. Operationally, the shipment has been delivered, but the POD contains an exception. The dispatcher should save the signed document, obtain photos if available, notify the responsible party and link the incident to the order before invoicing. Treating the signed CMR as a clean POD and ignoring the remark can create a dispute later.

Common POD mistakes

  • Accepting a photo or scan without checking that it belongs to the correct shipment
  • Looking only for a signature and ignoring remarks or reservations
  • Sending documents to invoicing before missing pages or required evidence are collected
  • Keeping POD in email or chat without attaching it to the shipment record
  • Assuming every customer accepts the same document or electronic confirmation as POD
Open LogicCalc →
Documents

T1 and T2 Transit Documents Explained

T1 and T2 are customs-transit concepts used in Union and common transit. A dispatcher does not need to be a customs broker, but should understand why a shipment is moving under transit and which customs office or procedure must be completed.

What T1/T2 transit means operationally

Customs transit lets goods move under customs supervision while duties, taxes or other import measures are temporarily suspended until the relevant customs formalities are completed. In daily road-freight language, T1 is generally associated with external transit for non-Union goods, while T2 is generally used for internal transit where Union status must be preserved through the movement. The exact procedure must come from the responsible customs party, not from a dispatcher guessing from the route.

The dispatcher’s job is operational control: know whether transit applies, keep the MRN or transit reference attached to the correct shipment, follow the instructed customs offices and time limits, preserve accompanying documents, and obtain confirmation that the movement was properly presented or discharged. Commercial invoices and packing lists can support customs/document checks, but they do not replace the transit declaration or the customs instructions.

Dispatcher workflow for a transit shipment

1. Confirm the customs instruction before dispatch

Identify whether the load is moving under transit and who is responsible for the customs procedure. Record the procedure/reference exactly as supplied. Do not decide T1 or T2 from nationality, route or cargo description alone.

2. Match the MRN and documents to the shipment

Store the MRN/transit reference with the transport order. Cross-check shipper, consignee, goods description, package count and weight against the commercial invoice, packing list and transport information when those documents are provided. Escalate material inconsistencies before departure.

3. Follow the instructed customs offices and route events

Know the office of departure, any office of transit and the destination/presentation point named in the customs instructions. A physical delivery address and a customs destination are not necessarily the same place. Do not skip a customs stop because the truck can physically reach the consignee.

4. Track the movement until customs completion

Record presentation, customs messages or release/discharge confirmation that the responsible party provides. A truck can finish the road leg while the transit procedure remains administratively open. Treat an unresolved transit as an exception, not as a completed file.

5. Archive the evidence with the transport file

Keep the final transit reference/status together with the order, CMR/POD and relevant commercial documents. If customs or the broker requests additional evidence, preserve the communication and the version of documents actually used for the movement.

Worked example: non-Union goods moving inland

A truck collects non-Union goods at an EU entry point and moves them inland to the customs office specified by the broker. The broker provides the transit MRN and instructions. Before dispatch, the planner links the MRN to the load and checks that the commercial invoice and packing list describe the same goods and packages as the transport order. The driver is told where the customs presentation must happen before final delivery. After arrival, the planner waits for the responsible customs party to confirm that the transit movement has been properly dealt with. The customer delivery alone is not used as proof that customs transit is closed.

Common transit-document mistakes

  • Choosing T1 or T2 from memory instead of following customs instructions
  • Mixing an MRN from another shipment into the transport file
  • Treating a commercial invoice or packing list as a substitute for the transit declaration
  • Driving directly to the consignee while an instructed customs presentation is still required
  • Closing the job after POD without confirming the customs movement status
Official reference

For regulated or convention-based topics, verify the current requirements with the responsible authority or competent specialist.

https://taxation-customs.ec.europa.eu/customs/customs-procedures-import-and-export/customs-transit_en
Open LogicCalc →
Documents

ADR Road Freight Documents and Dispatcher Checks

ADR governs the carriage of dangerous goods by road. A dispatcher does not classify dangerous goods by guesswork: the job is to recognise ADR-sensitive shipments, verify that the supplied dangerous-goods data is complete, and confirm that competent parties have cleared the driver, vehicle, equipment, documents and route before dispatch.

What a dispatcher should understand about ADR

ADR 2025 is the current consolidated UNECE framework applicable from 1 January 2025. It covers far more than a document: classification, the dangerous-goods list and exemptions, packaging and tanks, consignment procedures, loading and handling, vehicle crews and equipment, operations, documentation and certain vehicle requirements. A dispatcher therefore needs a control process rather than a single ADR checkbox.

The shipper, dangerous-goods safety adviser, carrier or other competent party may provide the technical classification and compliance decision. Operations should preserve that information and verify that the planned movement matches it. Do not derive a UN number, packing group, tunnel restriction, exemption or vehicle requirement from a product nickname or an old shipment.

ADR pre-dispatch workflow

1. Identify the dangerous-goods data

Link the shipment to the supplied UN number and dangerous-goods description, quantity and packaging information. Check that the data belongs to this exact order and has not been copied from another load. If classification is missing or contradictory, escalate before planning further.

2. Confirm the applicable movement conditions

Ask the responsible competent party which ADR conditions, quantity thresholds or exemptions are being used. Record the decision and any restrictions that affect vehicle choice, loading, segregation, route or documentation. Do not invent an exemption because the quantity appears small.

3. Verify carrier, driver, vehicle and equipment

Confirm that the selected carrier has accepted the ADR movement and that any required driver qualification, vehicle approval, markings, placards, fire extinguishers, PPE or other equipment have been checked by the responsible party. Match the confirmation to the actual vehicle being dispatched.

4. Check documents and crew information before departure

Make sure the required transport document and any shipment-specific supporting documents are available in the agreed form. Confirm that the vehicle crew has the current ADR instructions in writing and any operational information required for the load. Missing safety documentation is a stop condition, not a post-departure admin task.

5. Control loading, route and exceptions

Check that the loading point knows it is an ADR movement and that relevant loading/segregation instructions are followed by competent staff. Record route or tunnel restrictions supplied for the movement and escalate any route change, damaged package, leak, rejected loading or documentation mismatch before continuing.

Example: ADR-sensitive pallet shipment

A customer books several pallets and supplies dangerous-goods data including a UN number, description, quantity and packaging details. The dispatcher attaches that data to the order, asks the carrier to confirm acceptance and the responsible ADR conditions, verifies the actual driver/vehicle assignment and required equipment, and checks the transport document before release. During loading one package is found damaged. Instead of sending the truck because the slot is closing, operations stops the release, records the exception and waits for instructions from the competent dangerous-goods party. The safety decision stays with the qualified party; the dispatcher protects the chain of information and prevents an unverified movement.

Common ADR dispatch mistakes

  • Copying dangerous-goods data from an old order without checking the current shipment
  • Assuming a limited-quantity or other exemption without documented confirmation
  • Checking the carrier company but not the actual driver and vehicle assigned
  • Treating the transport document as the only ADR requirement and ignoring equipment or operational restrictions
  • Changing route, vehicle, load composition or packaging assumptions without rechecking the ADR impact
  • Letting the truck depart while a safety-critical discrepancy is still unresolved
Official reference

For regulated or convention-based topics, verify the current requirements with the responsible authority or competent specialist.

https://unece.org/transport/publications/agreement-concerning-international-carriage-dangerous-goods-road-adr-2025
Open LogicCalc →

Related guides

European Road Freight Planning & Pricing Guide

LogicCalc Learn is an operational learning resource, not legal, customs, tax or dangerous-goods advice. Verify shipment-specific requirements before dispatch.