Website Design OutsourcePowered by StealthAgents

How to Review the Exclusion List in an Outsourced Website Maintenance Contract

A practical way to read the exclusions in a website maintenance agreement, separate labour from pass-through costs, and price the boundary before a routine request becomes a dispute.

Visual guide for How to Review the Exclusion List in an Outsourced Website Maintenance Contract
On this page
  1. The exclusion list sets the real price
  2. Separate labour exclusions from pass-through costs
  3. Test each exclusion against a real request
  4. Watch the four exclusions that cause most disputes
  5. Put a price and an approval path on the boundary
  6. Check accessibility and content exclusions carefully
  7. Review the list at renewal, not only at signing
  8. Turn the review into a one-page schedule

The exclusion list sets the real price

Most buyers compare maintenance proposals by the monthly retainer and the included hours. The exclusion list rarely gets the same attention, even though it determines what happens when a request falls outside the defined scope. A low retainer with broad exclusions can cost more than a higher retainer that covers the work you actually send. Read the exclusions as a price list for the moments your site is most likely to need help.

Exclusions are not automatically unfair. A vendor cannot include unlimited design, copywriting, and third-party licence costs in a small maintenance fee. The problem starts when the boundary is vague, when the add-on rate is missing, or when a routine task is quietly classified as new work. The review should test whether the boundary is clear enough to apply without a meeting.

Separate labour exclusions from pass-through costs

Start by sorting every exclusion into two groups. Labour exclusions describe work the vendor will not do under the retainer, such as new page design or content migration. Pass-through costs describe money the vendor pays to someone else, such as hosting, premium plugins, stock images, or font licences. The two need different controls because one is a capacity decision and the other is a reimbursement decision.

For pass-through costs, ask who buys the item, who owns the account, and how the charge is approved. A vendor should not purchase a renewal on your behalf without a written cap or a named approver. For labour exclusions, ask for the hourly or fixed rate that applies when the work is approved. A boundary without a price is only a promise to negotiate later.

Test each exclusion against a real request

Take ten requests from the last six months and map each one to a clause. Include a routine image swap, a broken form notification, a new landing page, a plugin renewal, and an urgent fix on a Friday evening. If a request maps to two clauses, the contract is ambiguous and will produce a different answer depending on who reads it. This exercise takes an hour and reveals more than a general conversation about flexibility.

Write down the answer for each request and mark it as included, excluded, or unclear. Sort the unclear entries by how often they appear in the queue. The unclear column is the useful one, because those are the requests that will generate a quote, a delay, or an argument at the worst moment. Fix the unclear entries before renewal, not after the first disputed invoice.

Watch the four exclusions that cause most disputes

New page design is the first common exclusion. It is reasonable when the retainer covers maintenance rather than growth. The risk is a definition that treats every layout change as new design, including a small section added to an existing template. Ask the vendor to state what counts as a new page and what counts as an edit to an approved template.

Copywriting is the second, because many maintenance plans cover publishing but not writing. Third-party services are the third, since a plugin failure can require a vendor ticket or a paid upgrade that nobody budgeted. Emergency out-of-hours work is the fourth, and it needs a rate, a trigger, and an approval path rather than a vague promise to help if available. Treat the emergency rate as part of the boundary, not as a favour negotiated during an outage.

Put a price and an approval path on the boundary

Every exclusion that could plausibly appear in a normal month should have a rate and an approver. A rate can be hourly, fixed per task, or a published band, but it must be written down. The approver should be a role rather than a person, so the process survives a holiday or a staff change. Put both in the contract schedule and repeat them in the monthly report.

Set a small emergency threshold that a named manager can approve without a full change order. For example, a fix under a stated amount might proceed immediately to restore service, with the paperwork completed the next working day. This protects the site without turning every urgent request into a purchase order. The threshold should be low enough that it cannot hide a larger project.

Check accessibility and content exclusions carefully

Accessibility remediation is sometimes excluded as specialist work. That is defensible only if the contract names the standard and the escalation route. A maintenance vendor should still fix obvious regressions it introduces, such as missing alt text on a new image or a broken focus state in a reused component. Ask which accessibility issues are covered and which require a separate remediation project.

Content exclusions deserve the same test. A plan that publishes content but excludes fact-checking, legal review, or translation creates a gap between the file arriving and the page going live. The WCAG 2.2 recommendation is a useful reference when the contract mentions accessibility, because it gives both sides a shared standard to cite. Name the standard, the conformance level, and the pages in scope.

Review the list at renewal, not only at signing

Exclusions age as the site changes. A clause written before a rebuild may not mention the new CMS, the new analytics stack, or the new ecommerce flow. At renewal, compare the exclusion list with the current page inventory and the last twelve months of requests. Any category that appeared repeatedly should move into scope or get a clear add-on price.

Use the invoice reconciliation and the ticket log as evidence for that conversation. Keep the evidence in a shared renewal folder so the pattern is visible. The retainer boundary guide explains how to separate fixes from new features, and the quote assumptions audit shows what a transparent price should disclose. A contract review that ignores actual requests is just a reading exercise.

Turn the review into a one-page schedule

Finish with a one-page schedule that lists the exclusion, the reason, the rate, the approver, and the expected turnaround. Keep it beside the main agreement and update it when a clause changes. Give a copy to the person who sends maintenance requests, because the schedule is only useful if the requester can apply it without calling legal. A shared schedule prevents the slow drift from a clear contract to an ad hoc relationship.

Review the schedule once a year and after any major release. Add a note when an exclusion caused a delay, and record whether the vendor honored the stated rate. That small history is stronger renewal evidence than a satisfaction survey. It also gives the vendor a fair chance to propose a better package instead of defending a clause nobody understands.

Turn the guidance into a reviewable handoff

Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.

Plan a website production handoff

Move one website project from backlog to a reviewed handoff.

Share the pages, platform, current assets, deadline, and approval owner. We will help determine the right production lane and the decisions your team should keep.

Plan the handoff