Say It in Writing: Five Message Structures That Keep Overseas Manufacturing Projects From Drifting
Photo: Internet Archive Book Images, No restrictions, via Wikimedia Commons
Ask a US buyer what went wrong on a failed overseas project and the answer is rarely a defective part or a missed shipment. It's usually a sentence like: "We thought they understood the change applied to the second batch." Communication breakdowns don't announce themselves. They compound quietly until they show up as scrap, delay, or a six-figure dispute.
The teams that avoid this don't communicate more—they communicate in structures. Five message types, used consistently, cover the majority of failure modes.
1. The Kickoff Spec Confirmation
Before production begins, send a single email that restates the complete scope: part numbers, revision levels, quantities, dates, quality standards, and acceptance criteria. Ask the supplier to confirm each line explicitly.
The mistake it prevents: A Midwest industrial equipment maker once discovered that their supplier was tooling against an outdated drawing revision. The confirmation email habit—"Reply confirming Rev C, not Rev B"—makes that error nearly impossible.
2. The Milestone Check-In
A short, scheduled note at every production gate: tooling complete, first articles produced, batch inspection done. Each check-in asks one question—"What has changed since the last update?"—rather than a vague "How's it going?"
The mistake it prevents: Silent problems. Suppliers in relationship-oriented business cultures often won't volunteer bad news; a structured check-in gives them a scheduled, low-friction opening to share it.
3. The Change Notification
Any spec, quantity, or date change gets its own email, numbered (Change Notice #4), with the old requirement, the new requirement, the cost and schedule impact, and an explicit request for written acknowledgment.
The mistake it prevents: The verbal change that never made it to the factory floor. Verbal changes are where warranties go to die.
4. The Escalation Note
When something is genuinely stuck, escalation emails follow a discipline: state the issue, state the business impact in dollars and dates, reference the prior messages, propose a resolution deadline, and copy only the people who can act.
The mistake it prevents: Escalation by frustration—angry, vague emails that damage the relationship without moving the problem. A calm, specific escalation is often what preserves a partnership through a rough patch.
5. The Closure Summary
After every shipment, send a wrap-up: what shipped, what passed inspection, what open issues remain, what's agreed for next time. This becomes the institutional memory that survives staff turnover on both sides.
The mistake it prevents: Repeating last year's mistakes next year. Teams that close projects in writing stop paying the same tuition twice.
Structure Beats Volume
None of these templates require fluency in cross-cultural communication theory. They require consistency. When both sides know what the next message will look like, ambiguity has nowhere to hide—and the six-figure surprises mostly stop arriving.
