Handoffs

Every boundary gets a short written promise.

A handoff agreement says exactly what passes from one side to the other. It is short, plain and signed off by both.

Seven lines, every time

  1. From and toThe sending side and the receiving side, each with a named owner.
  2. WhatWhich records are included and which are deliberately left out.
  3. ShapeColumns, order, header row, delimiter and character encoding.
  4. FormatsHow dates, amounts, codes and empty values are written.
  5. WhenSchedule or trigger, and the latest acceptable arrival time.
  6. WhereThe staging area or destination it is placed in.
  7. If it changesWho is told, how, and how much notice is expected.

Why both sides sign

An agreement written by one side alone tends to describe what is convenient to send. An agreement signed by both describes what is actually needed. The signing is usually a reply to an email; what matters is that the receiver has read it and said yes.

When something later goes wrong, the agreement removes the argument about what was expected. The question becomes simply whether the data met the agreement.

Changing an agreement

Agreements change. A new column is needed, a schedule moves, a partner upgrades their system. Changes are versioned and dated, and the flow is updated to match on an agreed date, not quietly in the middle of a week.

Old versions are kept so any past run can be read against the agreement that applied at the time.

Draft one now.

The handoff agreement drafter turns your answers into a first version to share.