Three-month plan, seven months done—both sides think the other added scope. Root cause is rarely typing speed—it is scope, interfaces, and acceptance not in contract language: which documents this phase, which integration fields count as done, acceptance by login or by metrics. Verbal consensus works week one; change kills it. Overruns are a language problem—not attitude.
Contract language is not necessarily legal prose—it is the same page you open in dispute: in/out list, interface table, acceptance scripts.
Three Attachments Beat the Kickoff
Scope as in/out table; interfaces with fields, frequency, retry; acceptance as repeatable business-day scripts. Missing any—change disguises as "misunderstanding." Without written reference, schedule fills with overtime.
- New requests must declare what old scope they replace—or which timeline they extend.
- Interfaces pass integration environment test cases—not "dev says it works."
- Acceptance owner is business—not PM checking their own list.
Make Change Priced Language
Change is not forbidden—it needs price and timeline formulas. XYN digital intelligence implementation writes scene packs and interface lists into attachments—fewer "one small extra request." Fewer overruns come from disputable sentences—not another rally.
Next charter: write three attachments before estimating person-days. Person-days without attachments drift at integration week.
