Free template
Website Maintenance Agreement Template – Washington
Draft your custom agreement in seconds with AI Lawyer
Download template
Website Maintenance Agreement Template
1. Change Control and Maintenance Model
The Parties will separate routine maintenance from changes that alter functionality or design.
Routine maintenance includes updates, monitoring, backups, and bug fixes required to keep the Website operating normally.
Changes and enhancements require an approved change request before work begins, except for urgent security patches where delay would materially increase risk.
2. Parties and Website
This Website Maintenance Agreement ("Agreement") is made on [Effective Date: March 5, 2026] by and between:
Client: [Client: Cascadia Tech Co-op; Address: 701 5th Ave, Suite 4200, Seattle, WA 98104; Email: [email protected]; Phone: (206) 555-0118]
Service Provider: [Service Provider: Puget Sound Site Reliability LLC; Address: 1201 3rd Ave, Suite 2200, Seattle, WA 98101; Email: [email protected]; Phone: (206) 555-0169]
Covered website: [Website URL: https://www.cascadiatech.coop] on [Platform: Next.js site + headless CMS].
3. Scope of Services
The Service Provider will provide routine maintenance services, including dependency updates, security monitoring, backups, uptime monitoring, bug fixing, and performance optimization.
Minor content updates are included up to 60 minutes per month; additional work is billed at $175 per hour.
Work that adds features, changes information architecture, or modifies checkout, authentication, or integrations is treated as a change request.
4. Change Request Table
Approved change requests may include third-party costs, and the Service Provider may require a deposit for changes exceeding $1,000.
Request | Description | Estimate | Approval | Deploy Window | Rollback Plan |
[CR-014: Checkout optimization] | Improve checkout speed and reduce cart abandonment | [Estimate: $750] | Client approver email confirmation | Tue-Thu 20:00-22:00 Pacific Time | Revert to prior release within 30 minutes |
Routine security patch | Apply urgent dependency patch | Included if routine | Post-deploy notice to Client | Next available maintenance window | Rollback if error rate increases materially |
5. Support Channels and Response Targets
Support hours are Mon-Fri 9:00-17:00 Pacific Time.
Emergency Issues will be acknowledged within 1 hour during support hours and within 3 hours outside support hours.
Standard requests will be acknowledged within 1 business day and targeted for resolution within 3 business days where commercially reasonable.
The Client will designate an approver for change requests: [Client Approver: Alex Nguyen, [email protected]].
6. Security Baseline and Incident Handling
The Service Provider will maintain a baseline of reasonable security practices for the Website, including monitoring, timely patching, and least-privilege access where feasible.
If the Service Provider detects an active compromise, the Service Provider may take protective actions to limit impact, including disabling affected components or restricting administrative access.
The Service Provider will provide an incident summary including timeline, actions taken, and recommendations for preventing recurrence.
7. Backups, Rollback, and Restoration
The Service Provider will perform daily backups with 30-day retention and will maintain a basic rollback approach for deployments performed by the Service Provider.
One restoration per quarter is included; additional restorations are billed at $175 per hour.
8. Term and Renewal
This Agreement begins on the Effective Date and continues for an initial 12-month term.
After the initial term, this Agreement renews automatically on a month-to-month basis unless either Party provides 30 days' written notice of non-renewal.
9. Fees and Payment
Monthly fee: [Monthly Fee: $1,800], billed in advance on the first calendar day of each month via [Payment Method: ACH transfer].
Amounts not paid within 10 days after the due date may result in suspension of non-emergency work until the account is current.
10. Client Responsibilities
The Client will provide timely access, maintain third-party vendor accounts, and avoid uncoordinated changes outside the change request process.
The Client is responsible for the accuracy and legality of Client content and for compliance obligations related to the Client's business operations.
11. Confidentiality
Each Party will keep the other Party's confidential information confidential and will use it only to perform obligations under this Agreement.
The Service Provider may disclose confidential information to subcontractors who have a need to know and are bound by confidentiality obligations.
12. Termination, Liability, Governing Law, and Entire Agreement
Either Party may terminate for convenience with 30 days' written notice, or for material breach if not cured within 10 days after written notice.
Upon termination, the Service Provider will deliver the most recent backup and a configuration summary within 7 business days and will remove administrative access upon request.
Neither Party is liable for indirect, incidental, special, or consequential damages.
The Service Provider's total liability is limited to the total fees paid by the Client in the 3 months immediately preceding the event giving rise to the claim.
The Parties will attempt good-faith resolution by business representatives, and if not resolved within 15 days, the Parties may pursue binding arbitration in [Venue City: Seattle, Washington] unless both Parties agree to litigate in court.
This Agreement is governed by the laws of Washington.
This Agreement is the entire agreement between the Parties regarding website maintenance and supersedes all prior discussions or agreements on that subject.
Signatures
IN WITNESS WHEREOF, the Parties execute this Agreement as of the Effective Date.
Client Authorized Signer: [Client Signer Block: Alex Nguyen, Operations Manager; Signature Alex Nguyen; Date March 5, 2026]
Release Approver (Acknowledgment): [Client Release Acknowledgment: Jordan Kim, Product Owner; Signature Jordan Kim; Date March 5, 2026]
Service Provider Authorized Signer: [Provider Signer Block: Casey Wu, Managing Member; Signature Casey Wu; Date March 5, 2026]
Security Lead (Acknowledgment): [Provider Security Acknowledgment: Morgan Chen, Security Lead; Signature Morgan Chen; Date March 5, 2026]
No time to fill it up? Generate your custom agreement with AI Lawyer in seconds
Details
Learn more about
Website Maintenance Agreement Template – Washington
Washington Website Maintenance Agreement Template FAQ
How does the Washington version separate routine maintenance from change requests?
Routine maintenance covers the work needed to keep the site operating normally, such as patching, monitoring, and bug fixes. Anything that changes functionality, integrations, or design is routed through a change request so scope, timing, and approval are explicit.
What fields should be captured in the change request table?
A useful change request record includes a clear description, a cost and time estimate, an approval signal, a deploy window, and a rollback plan. Capturing these fields helps both sides treat changes like a controlled release rather than an informal favor.
What security baseline is reasonable for a small business website?
Most sites benefit from timely patching, access control, monitoring for common indicators of compromise, and reliable backups. The template frames security as a set of practical process commitments rather than promises of perfect prevention.
How are rollbacks handled if an update breaks the site?
The agreement pairs backups with a basic rollback approach for deployments performed by the provider. If an update causes material errors, the provider can revert to the prior release while investigating a safer fix.
Can notices and requests be sent through a ticketing system or chat tool?
Yes, the template is compatible with modern workflows as long as the parties agree on the channel and the approver. What matters is that requests are traceable and approvals are unambiguous.
What happens if a platform upgrade requires downtime?
Upgrades can be scheduled into a maintenance window with advance notice and a rollback plan. The change request structure makes planned downtime a managed event rather than an unexpected outage.
Where does AI Lawyer fit if we need a faster approval workflow?
AI Lawyer can help you standardize how approvals are captured and how change requests are described, so the contract supports a clean release process without adding unnecessary legal complexity.
Similar templates
