Free Statement of Work (SOW) Generator

Acceptance is the mechanism most statements of work leave implied. A deliverable goes over on a Thursday, the client says thanks, and three weeks later a message arrives asking for a few tweaks before sign-off. Nothing in that sequence is bad faith. It happens because no one wrote down what would count as done, so there is no event to point at, and the milestone invoice that depends on acceptance has nothing to attach to. Acceptance criteria fix this by describing the test rather than the feeling: the file opens in this format, the page loads under this condition, the report reconciles to this figure.

Put four milestones of $6,000 on a six-month engagement, each payable on acceptance. Add one clause: the client has five business days from delivery to reject in writing with reasons, and silence after that counts as acceptance. The clause does nothing on a well-run project, where the client replies inside two days. On the project where the sponsor changes in month three, it is the difference between an invoice you can raise and a $6,000 milestone that sits open while a new person forms an opinion. The five days are worth negotiating; the written rejection with reasons is the part that carries the value.

Change control is where a signed scope actually holds or fails. The request that starts as a message asking whether something is possible becomes work when someone begins it, and by the time it is delivered there is nothing to invoice against, because the SOW lists six deliverables and this is a seventh. A workable process names who can approve a change, requires it in writing, and states that work does not begin until the change is signed. The last part is the one people skip, and it is the reason a genuine change ends up billed as goodwill.