A new consulting engagement starts next week. The MSA's already signed. The SOW outlines the specific work, deliverables, and price. The client's sponsor signs off; you start.
SOWs close engagements faster than full contracts when MSAs are in place.
Reference the MSA
The SOW should reference the master agreement explicitly. "This SOW is issued under the Master Services Agreement dated [date]." The MSA covers commercial terms; the SOW covers the specific engagement. Together they form the complete deal — neither stands alone.
Specifics in the scope
Deliverables (specific outputs). Acceptance criteria (how the client confirms work is done). Timeline with milestones. Price and payment schedule. Key personnel. Exclusions (what's not in scope). The clearer the SOW, the fewer the disputes during execution.
Send for signature
Use sign PDF to drop signature fields for both parties. Sponsor on the client side, project lead on yours. Same-day execution is normal. The audit trail proves when the engagement started.
Track changes
When scope changes during the engagement, issue a change order or amended SOW and re-sign. Don't let scope creep silently — every change captured in writing, signed by both parties. The discipline pays for itself the first time a dispute arises.
FAQ
Can an SOW be e-signed without re-signing the MSA?
Yes — if the MSA is already executed, the SOW is a separate document that references it. Standard practice.
How long should an SOW be?
2-5 pages for typical engagements. Longer for complex multi-phase work. The SOW gets read; long ones get skimmed.
What if the client wants to change scope mid-engagement?
Issue a change order or amended SOW. Re-sign. Document everything. Verbal scope changes are how engagements blow up.
Should the SOW include success metrics?
Where measurable, yes. Subjective "customer satisfaction" criteria invite disputes; clear measurable deliverables don't.
SOWs close engagements same-day. Send via Flint and you start next week, not next month.