Reconcile ULD custody and condition at each air-cargo handover

The unit arrived, but its damage note did not

A handling station receives a ULD and adds it to available inventory. The sending station had recorded a damage observation, but the transfer interface carried only the equipment identifier and quantity. The physical transfer is correct; the availability decision is unsupported.

The immediate need is a linked custody and condition record. A receiving acknowledgement should confirm where the identified unit is while retaining any unresolved condition information. Availability for operational use requires the applicable authorised assessment, rather than a successful inventory receipt alone.

The IATA — ULD Regulations covers identification, handling, serviceability, damage and repair topics. Its scope explains why a ULD ledger needs more than a location field. The specific criteria and decisions must follow the applicable current procedures and qualified authority.

Separate the questions that inventory tends to combine

For each ULD, distinguish ownership, physical location, accountable custody, observed condition and authorised serviceability or release state. Those attributes can change at different times and may have different sources.

A unit may be physically at station B while station A's transfer remains unacknowledged. Another may have a completed receipt but an open condition assessment. A leased or pooled unit may also have an ownership relationship different from the station holding it.

Use the actual equipment identifier and the organisation's approved identity rules. Preserve labels and partner references without inventing a local number that loses the connection to the original unit. If the identifier cannot be confirmed, hold the reconciliation case open rather than merging it into a similar-looking record.

The operations team should define who can record an observation, who accepts custody and who is authorised to determine serviceability. A person signing a receipt is not automatically authorised to release the unit for use.

Build a handover record that carries unresolved work

A transfer record should identify the sending and receiving parties, each ULD, the intended movement, dispatch observation and receiving acknowledgement. Retain both event times and the time the systems received the records.

Attach condition observations to the unit and transfer, including the source, timestamp and any authorised assessment reference. Where photographs are permitted, retain them with the relevant record and access restrictions. A photograph is supporting evidence, not a self-executing serviceability decision.

If the two parties disagree about condition or count, create a discrepancy linked to the handover. Keep the original observations visible. Replacing the sender's note with the receiver's note may erase the information needed to establish when a change occurred.

The receiving workflow should make missing condition evidence visible before the unit enters an available pool. The agreed procedure determines the operational restriction while the evidence is resolved.

Worked example: thirty units reconcile, but only twenty-nine are released

This illustrative example covers a closed group of thirty owned ULDs at two stations, with no purchases, disposals or transfers outside the group during the period.

Station A starts with twenty units and station B with ten. A transfers six identified units to B, and B acknowledges all six. B later returns two of those units to A, which acknowledges both. One of the four transferred units still at B has an unresolved damage assessment.

At closing, assume the appropriate records support release of all sixteen units at A and thirteen at B. The remaining unit at B is held pending qualified assessment.

The physical balance is sixteen plus fourteen equals thirty. The release-state balance is twenty-nine released plus one held equals thirty. The held unit has not disappeared and should not be listed as in transit merely because it is unavailable.

Suppose the damage note existed at A before the six-unit transfer, but B's system did not receive it. The transfer counts can still reconcile perfectly while the condition trail fails. The review must therefore inspect both the transfer reconciliation and the condition handoff.

This example assumes all transfers are acknowledged before closing. If the two return units were still moving, the ledger would need an explicit in-transit state and a defined rule for accountable custody. It must not count them as physically present at both stations.

Compare tools using a damaged-transfer case

A shared equipment register can be adequate when the fleet and station network are small, provided that identities and assessment records remain controlled. Its weakness is the manual coordination needed when transfers and condition decisions happen in separate teams.

A station inventory system may record receipts accurately but require an additional condition workflow. Demonstrate whether a receipt preserves the sending station's unresolved assessment and prevents an unsupported change to available status.

A specialist ULD platform may offer broader pooling, transfer and condition capabilities. Evaluate the actual partner interfaces, owner permissions and recovery behaviour. A feature name is not evidence that the particular transfer chain is supported.

Use the thirty-unit example for each option. Ask for the physical balance, the held unit, its original observation and the authorised decision that would be needed before release. A count-only demonstration misses the central risk.

Investigate discrepancies in a useful order

Start with identity and physical evidence. Confirm whether the disputed records refer to the same unit and movement. Then compare dispatch, receipt and any intermediate custody observations.

Check for a duplicate transfer, a missing acknowledgement, an unrecorded return or a condition note attached to the wrong unit. These explanations require different corrections. A balancing adjustment should not be the first response simply because the totals differ.

Assign unresolved custody to an operational owner and unresolved condition to the appropriate assessment owner. Set review times according to the applicable operating process. Escalation should make the missing decision visible without granting release authority to the escalation recipient.

When a record is corrected, retain the previous state, reason and approval. If a unit was incorrectly shown as available, review any subsequent allocation or movement through the responsible operational process.

Measure reconciliation and condition continuity separately

Track units without a confirmed custody state, transfers awaiting acknowledgement and condition cases lacking a named assessment owner. State the review cutoff and the set of units included.

Also inspect how many receipts arrived without the required condition information and how long those gaps remained unresolved. A low missing-unit count does not establish a reliable serviceability trail.

For the proposed evaluation, every unit in the closed thirty-unit example should appear once in the physical reconciliation, and the held unit should remain unavailable under the assumed procedure until authorised resolution. This is a test of record integrity, not a technical serviceability assessment.

Preserve the decision that travels with the equipment

A reliable ULD record explains where the unit is, who holds it and what evidence supports its current use status. Those answers should survive movement between systems and stations.

Next actions

1. Trace one transfer with an unresolved condition observation through both stations' records.
2. Identify who accepts custody and who has authority for assessment and release.
3. Reconcile physical balances separately from held and released quantities.
4. Test whether the chosen workflow preserves the condition history during receipt, return and correction.

For a focused review, bring a station ledger, transfer acknowledgements and the associated condition records. The assessment can then identify whether the failure is missing equipment, missing evidence or an unsupported release decision.