Milestone gates: the invisible reason engagements don't drift
Milestone gates are the cheapest insurance an offshore engagement has. The structure, the cadence, and the language to use in the email.
What a gate is
A milestone gate is a scheduled, written checkpoint where the agency presents output, the client formally accepts or rejects, and the liaison witnesses the exchange. It is not a status call.
Acceptance is binary and written. 'Looks good' in chat is not acceptance.
Cadence
Every two weeks for engagements under three months, every three for longer ones. Set them at kickoff and put them on every calendar at once.
Each gate has named acceptance criteria written before the work begins, not after.
The email template
Subject: Gate N. Acceptance request. <project>.
Body: bullet list of acceptance criteria with pass/fail and links to artifacts; a one-line ask ('please reply ACCEPT or REJECT with reasons by Friday EOD'); next gate's date.
The liaison is on the To line, not Bcc.
- 01Disputes shrink to a single gate, not an entire engagement.
- 02Scope creep is caught at the next gate instead of three months in.
- 03The buyer's emotional state is paced by predictable yes/no moments.