Assumptions and Exclusions

Assumptions and exclusions are the paired statements in a statement of work that define what conditions must hold for the estimate to be valid and what work falls outside the agreed price. They give the delivery team a documented basis to raise a change order when conditions shift, rather than absorbing the cost.

Assumptions

An assumption is a condition that must be true for the estimate to hold. When that condition fails, the firm has a contractual basis to quantify the impact and issue a change order.

Well-written assumptions are specific, testable, and consequential:

• Specific: “Client will provide clean, de-duplicated CRM data in CSV format within 10 business days of kickoff” rather than “client will provide data.”
• Testable: it is possible to determine objectively whether the condition was met.
• Consequential: if violated, the impact on cost or timeline is clear and attributable.

Common assumption categories include client resource availability, data readiness, third-party system access, approval turnaround times, and environment stability.

Exclusions

An exclusion is an explicit statement of work that the agreed price does not cover. It prevents the implicit logic that clients often apply: if it is not listed as out of scope, it is included.

Write exclusions at the level of detail that matches the inclusions. If three workshop sessions are listed in scope, the exclusion should read “additional workshops or follow-up sessions.” If one integration is listed, exclude “additional system integrations not specified above.”

Exclusions also protect the delivery team by giving them a clear reference point when declining out-of-scope requests without damaging the client relationship.

Common mistakes

• Writing assumptions in language that cannot be enforced, such as “client cooperation is assumed.”
• Stating assumptions without defining the change-order consequence if they are violated.
• Omitting an exclusions section entirely and relying on “items not mentioned above are excluded.”
• Placing assumptions in an appendix that reviewers do not read before signing.

Relationship to scope and change orders

Assumptions and exclusions are the enforcement mechanism for a defined scope. A signed SOW with no assumptions section leaves the firm exposed: any delay or gap becomes a delivery problem rather than a client obligation. When an assumption is violated, the firm references it, quantifies the impact on timeline and cost, and issues a formal change order. The documented assumption is what makes that process straightforward rather than adversarial.

Servantium’s SOW template includes dedicated sections for both assumptions and exclusions, structured to link each assumption to the deliverable it supports.