Explain exclusions as practical boundaries: what the service covers, what remains with the client and which requests require a separate agreement. Place material exclusions near the related promise. Use examples to clarify adjacent work, and check that an exclusion does not contradict the service’s central description.
Find the likely points of confusion
Look for activities that commonly sit next to your service. A website content review may be mistaken for rewriting, uploading or legal approval. A workshop may be mistaken for ongoing coaching. List these neighboring activities and identify which a reasonable client might assume are included. Start with genuine enquiry questions or previous scope discussions when available. If you are drafting a new offer, use a clearly hypothetical brief rather than presenting assumptions as established demand.
Read the service name and headline alongside the proposed exclusions. If the name promises a complete launch but the service excludes production work, the problem lies in the offer itself. Narrow the headline instead of relying on a long exclusions section to undo the first impression. Boundaries should make a credible promise more precise. They should not conceal that the main result suggested by the page cannot be delivered within the stated work.
Pair boundaries with responsibilities
Write exclusions in ordinary language and explain the relevant owner. “Implementation is excluded” leaves a client wondering what happens next. A clearer statement identifies that you supply recommendations while the client’s team chooses and carries out changes. Where professional approval is required, state that the client must arrange it. This is an allocation of work rather than a guarantee that another person is available or that your recommendations meet every requirement of their environment.
Place important boundaries next to the inclusion they qualify. If sample wording is illustrative rather than approved publication copy, explain that near the sample deliverable. A concise exclusions list can collect related details, but it should not be the only place a reader discovers an essential limitation. Avoid unexplained legalistic phrases when a concrete example would help someone recognize the boundary. Use an appropriate separate agreement for detailed terms rather than improvising a contract inside marketing copy.
Explain how new requests are handled
Describe the process for work outside scope: discuss the request, assess dependencies and agree any change before proceeding. Do not imply that every extra request will be accepted or automatically priced at a fixed rate. A new activity may require different expertise or permissions. Offer a useful stopping point where the original service can still be completed, and document unresolved work so the client is not left guessing what was deliberately omitted.
Review exclusions after actual delivery reveals repeated misunderstanding. Sometimes repeated requests justify a new service or a revised inclusion. Sometimes they show that the original description attracts the wrong starting situation. Update the relevant page and enquiry response together. Keep the earlier scope attached to existing engagements; changing a public page does not by itself rewrite commitments already made. Clear boundaries depend on consistent communication across the whole conversation.
Fictional example: a review without a rebuild
A fictional accessibility writer, Elise, offers a review of selected help pages. A draft headline says “make your help centre accessible,” while the details exclude technical remediation and comprehensive evaluation. She changes the headline to describe an editorial review and lists the agreed page sample, written observations and suggested wording changes. She explains that development work and a comprehensive accessibility assessment require separate arrangements.
When a hypothetical client asks for corrected pages to be uploaded, Elise identifies that as an additional activity requiring access and approval. Her example proposal records the review as complete when the agreed findings are handed over, with publication remaining the client’s responsibility. This makes the boundary visible without suggesting that a writing review certifies the whole site.
A checklist for your next step
- List commonly assumed adjacent work.
- Check exclusions against the headline.
- Assign the remaining responsibilities.
- Place conditions near relevant inclusions.
- Agree changes before doing extra work.
Common questions
Do exclusions make an offer sound unhelpful?
They help when written as practical information. Explain the boundary and the next decision instead of listing unexplained refusals.
Can I change exclusions after an enquiry?
Clarify the proposed scope before agreement. For an existing engagement, discuss changes explicitly rather than relying on an updated webpage.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.