Internal Due Diligence Statement Reference Handoff

Many teams prepare data well but still fail at the final step: the due diligence statement reference is passed too late, to the wrong owner, or without matching shipment-lot context.

In this article, a production plot is the land where coffee or rubber is grown; a shipment lot is one export shipment (often one container) those plots feed into.

This guide outlines a practical handoff workflow for importer, broker, and downstream teams sourcing coffee or rubber from Vietnam.

Who handles the reference

At minimum, three groups should be aligned:

1. Importer / operator team: creates and confirms the due diligence statement.
2. Broker / customs team: uses the reference in related customs steps.
3. Downstream / commercial team: stores and reuses the reference as goods move forward.

Vietnam exporters prepare the shipment-lot evidence pack. They do not replace the EU operator’s statement filing duty unless a separate authorised process exists.

Without one shared flow, references get lost across email threads and chat channels.

Simple ownership baseline

• Creates and publishes the statement reference: importer / operator team.
• Approves release before handoff: named accountable owner on that team.
• Consulted for exceptions: compliance / legal.
• Informed: broker and downstream recipients — and, when needed, the Vietnam exporter for shipment-lot context matching.

This baseline is usually enough to reduce handoff errors.

Suggested six-step workflow

1. Freeze the shipment-lot data version before releasing the reference.
2. Publish the reference into one central register linked to shipment-lot ID.
3. Handoff to broker with required fields, not the reference alone.
4. Handoff to downstream with matching shipment-lot context.
5. Archive records in a retrieval-friendly structure.
6. Log every exception and version change.

Six common failure points

1. Reference shared across multiple channels without one source of truth.
2. Reference not linked to internal shipment-lot ID.
3. Broker receives the reference without supporting fields.
4. Downstream team receives the reference after processing starts.
5. Data updated after release but no new controlled version is issued.
6. Records stored in personal folders instead of a shared retention path.

Practical five-year retention structure

Do not store by person name or chat channel. Use one simple folder structure per shipment lot:

lot-id/
  01-evidence/
  02-statement-reference/
  03-handoff-log/
  04-change-log/

• 01-evidence/: source records for the shipment lot (documents, chain evidence, legal files).
• 02-statement-reference/: released reference and submission proof.
• 03-handoff-log/: who received it, when, and which version.
• 04-change-log/: any exception or update after release.

The goal is retrieval speed: anyone on the team can find the right file set within minutes.

One-page daily checklist

• Before release: data version frozen?
• At release: reference logged in the central register?
• At handoff: broker / downstream confirmed complete receipt?
• After handoff: archive updated in the right shipment-lot folder?

Conclusion

In EUDR operations, a correct reference can still create risk if handoff is weak. A clear internal workflow keeps shipment-lot execution stable as shipment volume grows — and keeps Vietnam evidence packaging separate from EU statement ownership.

Sources

• Regulation (EU) 2023/1115: due diligence statement and record retention principles
• Regulation (EU) 2025/2650: downstream actor role in the updated application timeline