Statement of Work (SOW)

A Statement of Work (SOW) is a project document that spells out exactly what will be delivered, by when, by whom, and under what conditions. It sits between a proposal (which sells the work) and a contract (which legalizes the relationship). The SOW is where ambiguity goes to die — and that's exactly the point.

A good SOW includes: project objectives, detailed scope of work, specific deliverables with acceptance criteria, timeline with milestones, roles and responsibilities for both parties, assumptions, and exclusions. The exclusions section is critical — listing what's NOT included prevents scope creep arguments later.

For freelancers, the SOW often lives inside the proposal itself as a dedicated section. For larger agency engagements, it's typically a standalone document attached to the master services agreement. Either way, both parties should sign or formally acknowledge it before work begins.

The biggest SOW mistake is being too vague. "Website redesign" is not a scope statement. "Redesign of 8 pages including homepage, 5 service pages, about page, and contact page, with responsive layouts for desktop and mobile, delivered as production-ready code" is. The more specific your SOW, the fewer disputes you'll face during and after the project.

PropCraft's proposal generator includes structured scope sections that function as embedded SOWs — clients accept the full document including scope, terms, and pricing in one step.