How to e-sign a Statement of Work (SOW)

A Statement of Work (SOW) operationalizes an MSA for a specific engagement: scope, deliverables, timeline, price.

SOW structure

1. Reference to governing MSA (date and parties) 2. Project description 3. Scope of work (specific tasks) 4. Deliverables (measurable outputs) 5. Timeline and milestones 6. Fees and payment schedule 7. Project-specific terms (if any override MSA) 8. Signatures

SOW best practices

### Specific deliverables Avoid vague language. "Provide marketing support" fails. "Deliver 10 blog posts, 20 social posts, 2 email campaigns by Oct 31" works.

### Milestone-based payment Break large fees into milestones tied to deliverables:

• 25% on signing
• 25% on deliverable A
• 25% on deliverable B
• 25% on final acceptance

### Assumptions List what you're assuming (timely client feedback, existing assets available, etc.). If assumptions don't hold, scope adjusts.

### Out-of-scope Explicitly list what's NOT included. Prevents scope creep arguments.

### Change order process State how out-of-scope work is handled: written change order with new SOW or amendment.

Workflow

1. Create SOW template on SignBolt based on your MSA 2. Per engagement: duplicate template, fill variables (scope, price, timeline) 3. Send for signature 4. Client signs; you countersign 5. Work begins per SOW

Change orders

Scope changes = new SOW or amendment: 1. Document change scope + pricing delta 2. Send via SignBolt 3. Client approves before work continues

Next

• How to e-sign an MSA
• SOW template