What belongs in a data delivery agreement (DLV)?

• Governance: rights and obligations, purpose and division of tasks, responsibility, the data-protection provisions.
• Data: a description of the data, agreements on timeliness, quality and type of delivery (full delivery or change notifications).
• Technical annex: formats, encodings, interfaces, transport route, encryption, protocols.

The content falls into three groups, and each answers a different question:

1. Who is responsible for what?

• Rights and obligations of both parties.
• Purpose of the delivery and the division of tasks.
• Responsibility (who answers for errors, who fixes them).
• The details needed to settle the data-protection issues (basis, purpose limitation, deletion).

2. What exactly is delivered, and how good must it be?

• A description of the data: which attributes, which meaning, which value lists.
• Agreements on timeliness (how fast changes arrive), quality (completeness, correctness) and the type of delivery: complete deliveries or change notifications.

3. How does it technically get there? (the technical annex)

• Formats and encodings, interfaces, transport route, encryption, protocols.

Splitting off the technical annex is practical: the business part is signed by managers and changes rarely, while the technical part is maintained by engineers and changes with every system upgrade.

Go deeper:

• Interface control document (Wikipedia) — the engineering counterpart of the technical annex: formats, protocols and transport between two systems.
• ICO: Data sharing code of practice — what a data-sharing agreement between organisations should contain.