What Should Be Included in a Website Design and Maintenance Agreement?

A website proposal can promise a modern design, hosting, optimization, and support without saying what will be built, who owns it, or what happens after launch. That ambiguity is where ordinary revisions turn into surprise invoices and where a business discovers that its own domain or administrator account belongs to someone else.

You should expect a **website design and maintenance agreement** to define scope, content, accessibility, performance, ownership, accounts, security, acceptance, ongoing work, and a complete handoff.

Define the site by pages and functions

List the page types, forms, search, ecommerce, scheduling, member features, integrations, languages, and content migration included, because a count of "ten pages" is incomplete when one page is a simple contact page and another is a product catalog with filtering and payments.

Identify who supplies copy, images, product data, legal policies, accessibility requirements, and approvals. Set a reasonable number of revision rounds and explain what makes a request a revision versus a new feature.

Establish measurable quality requirements

"Responsive" should mean the site is tested across agreed device sizes and browsers, not merely that elements become narrower. MDN defines cross-browser testing as checking that a site works across relevant browsers, devices, and assistive technologies.

The agreement should name the supported environments and critical tasks to test. These may include navigation, forms, checkout, account access, keyboard operation, error messages, and readable content.

Accessibility should be part of requirements and testing, not an optional plugin added at the end. W3C's WCAG overview explains the international standard and its testable success criteria.

Protect ownership and administrative control

Your business should control the domain registration and have appropriate administrator access to hosting, the content system, analytics, search tools, and third-party services. The agreement should state ownership of custom code, design files, written content, photography, licenses, and reusable components.

Ask whether premium themes, plugins, fonts, and media remain licensed when the maintenance relationship ends. A site can technically belong to you while depending on licenses you cannot renew.

Separate launch work from maintenance

Maintenance may include updates, backups, monitoring, security response, small content changes, support, or hosting, but those are different responsibilities, so define the schedule, limits, response times, excluded projects, and approval process for billable work.

You should know who tests backups and how restoration works. "Daily backups" says nothing about retention, off-site storage, or whether a full restore has ever succeeded.

Agree on acceptance and handoff

Before launch, test the agreed functions with realistic content and document defects. Define who approves launch, what happens to the previous site, and how domain or DNS changes can be reversed if the release fails.

The final handoff should include administrator access, source and design files when included, licenses, documentation, analytics ownership, backup instructions, training, and a list of recurring services. Also define how another qualified provider can take over.

A good website agreement does not eliminate every change. It gives changes a fair process and prevents essential ownership, security, and quality decisions from being left until the week of launch.