Write exclusions that help a client decide

Useful exclusions identify the work outside the fee and explain how additional work is considered.

ContractCanvas insights

Make the boundary concrete

“Anything not expressly included is excluded” may belong in a contract, but it does little to explain a consulting purchase. If an engagement covers research and recommendations, state whether implementation, staff training, translation and continuing support are included. Put the most consequential exclusions beside the deliverables rather than hiding them at the end.

Describe an example

A sample strategy review includes one management workshop and a final report. An extra workshop is outside the base scope. The parties can request it through change review, where the consultant estimates preparation, facilitation and revised timing. This tells the client how to obtain more work without implying that every question triggers another invoice.

Avoid an internal contradiction

Check the proposal summary, scope and pricing table together. An introduction promising end-to-end implementation conflicts with an exclusion of implementation. Correct the promise or the commercial scope. A disclaimer does not make inconsistent sales language clear.

Review from the recipient’s perspective

Ask a colleague to identify three plausible requests and decide whether each fits. Record ambiguous cases and revise the wording. In the prototype, keep exclusions in the approved specification so they travel with the commercial output. The review is about clarity; legal effect depends on the final agreement and applicable circumstances.