---
id: KB-LG-027
url: https://app.codecontract.io/help/logistics/the-leg-that-travels-in-someone-elses-hands
idioma: en
categoria: sector-logistica
subcategoria: ferroviario
audiencia: usuario
nivel: avanzado
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-LG-017, KB-LG-024]
citadoPor: [KB-LG-020]
---

# The leg that travels in someone else's hands

_For days the goods are not in your system but in an operator's, with their own calendar and their own records._

**Responde a:** tracking goods on a rail leg · no visibility over one leg of the transport · documentation between operator and end customer · who answers on a combined transport

Part of the journey is done neither by you nor by a partner you chose for their service: it is done by an operator with their own infrastructure, timetables fixed in advance and systems nothing like yours. **During that leg the goods exist in somebody else's records**, and your customer still asks you where their shipment is.

## What changes versus a leg you control

| What is at stake | Your own leg | An operator's leg |
| --- | --- | --- |
| When it departs | You decide | It is fixed |
| Where it is now | You know | They know |
| What happened en route | You record it | **They record it, their way** |
| **Who answers to the customer** | **You** | **Still you** |

> [!IMPORTANT]
> **With a leg you do not control, information stops being a by-product of the operation and becomes something that must be agreed explicitly.** On your own legs the data appears by itself because your people generate it. On this one nothing appears that was not agreed: what is communicated, when, in what format, and what happens when something departs from plan. Whatever is not in that agreement, you will not have on the day you need it.

## What to settle at the handover points

1. **What is recorded on handing over to the operator** — Condition, quantity and time: it is the snapshot separating you from whatever follows.
2. **What is recorded on collecting it** — The same snapshot, so the two can be compared.
3. **What is communicated in between** — And how often. Silence does not mean everything is fine.
4. **And what documentation travels with the goods** — Especially if it crosses borders or changes regime.

> [!WARNING]
> The place where money is lost is **the handover, not the journey**. A shipment that leaves fine and arrives damaged has passed through at least two hands, and the argument over which of the two is settled —or not— by what was recorded at each handover. Without those records each party reasonably maintains it was fine when they let go, and the bill ends up with whoever documented worst, who is not necessarily whoever broke it.

> [!NOTE]
> What documentation must accompany goods in each transport mode, what liability regime applies to each leg and how a combined transport is structured **depends on the applicable conventions and contracts, and is settled by your adviser**. Here we cover the operational part: how to document handovers and not depend on a third party's system.

**Can I require real-time tracking?**

You can agree it. What is not agreed at contracting does not arrive later.

**What do I do if there is no news for days?**

Give the absence of news a threshold that raises itself.

**Is the transport document enough?**

To operate, yes. To argue over damage, you need both handover snapshots.

## Ejemplos

**Goods arrive damaged and nobody knows on which leg it happened.**

- Records condition at each handover with date and time

→ The two snapshots narrow down where it occurred.

**Days pass with no news and nobody raises the alarm.**

- Warns when a shipment has gone too long without movement

→ Silence stops being mistaken for normality.

**The customer asks and the operator has to be phoned.**

- Gathers what is known about the shipment in one file

→ You answer with what exists without waiting on a third party.

**The leg's documentation lives only in the operator's system.**

- Collects and keeps what the third party provides

→ Your own archive does not depend on another system.

**Each operator communicates differently.**

- Requests the information in an agreed format

→ What is received is comparable across operators.

**Months later a damage claim arises and the departure record is missing.**

- Keeps handovers beyond the closing of the shipment

→ The late claim has something to answer with.