**Source:** https://heykiku.com/glossary/statement-of-work

# Statement of Work (SOW)

The Statement of Work is supposed to be the definitive reference for what's included in a project. In reality, most agency SOWs are **buried in Google Drive folders** nobody can find. They're referenced during sales, filed after signing, and forgotten until a dispute arises.

This creates a dangerous situation. When scope questions come up—and they always do—**nobody checks the SOW** because finding it takes too long. Instead, people rely on memory, make assumptions, or just say yes to avoid conflict. The document designed to prevent [scope creep](https://heykiku.com/glossary/scope-creep) becomes useless.

A good SOW does more than list deliverables. It **explicitly states what's not included**. It defines [revision rounds](https://heykiku.com/glossary/revision-round) and change processes. It establishes acceptance criteria so both sides know when work is complete. Most importantly, it's accessible to everyone who needs to reference it.

The format of your SOW matters less than its accessibility. Whether it's a formal legal document or a simple project brief, the key is that your team can **find it and use it** when questions arise. An SOW that prevents one scope dispute pays for itself many times over.

## Related terms

- [Scope Creep](https://heykiku.com/glossary/scope-creep)
- [Service Packages](https://heykiku.com/glossary/service-packages)
- [Revision Round](https://heykiku.com/glossary/revision-round)
- [Deliverable](https://heykiku.com/glossary/deliverable)
- [Client Confidentiality](https://heykiku.com/glossary/client-confidentiality)