Website care plan

Why the care plan matters

A live website should not depend on memory, scattered messages, or one person knowing where everything lives. The care plan creates a shared record for the site: the platform, access points, support cadence, request process, known risks, and monthly priorities.

That makes support cleaner for everyone. Your team knows what is included, what needs approval, how requests are handled, and what items should be quoted separately before they turn into loose scope.

What the baseline captures

• Website platform, CMS, hosting, theme, plugin, and form notes that affect routine support.
• Primary pages, business-critical conversion paths, contact forms, booking flows, and tracking points.
• Access notes for CMS, hosting, analytics, Search Console, Tag Manager, DNS, or third-party tools when provided.
• Known update risks, fragile layouts, custom code areas, integration dependencies, and approval contacts.
• Backup, restore, staging, and rollback notes where the hosting or platform supports them.

How support cadence is defined

The care plan sets expectations before the first support request comes in. It defines how often we review the site, how monthly support hours are used, what counts as routine maintenance, and how larger work moves into a separate quote.

• Monthly priority review for routine updates, site checks, support requests, and open risks.
• Request intake rules so edits include the page, requested change, business reason, and approval owner.
• Priority levels for visible site errors, form issues, access problems, content edits, and enhancement requests.
• Clear handling for included support time, overflow work, blocked items, and items waiting on client input.
• Quarterly roadmap refresh when the site needs deeper planning beyond routine monthly upkeep.

What belongs in routine care

Routine care is meant to keep the website stable, clean, and easier to manage. It is not an unlimited rebuild plan, but it gives the team a reliable way to handle small changes and regular monitoring.

• Small copy updates, link changes, image swaps, button updates, and simple page adjustments.
• CMS, theme, plugin, dependency, or platform update coordination when safe and within scope.
• Form checks, tracking checks, broken experience review, and visible page error notes.
• Basic performance, mobile usability, and content friction observations that can be reviewed monthly.
• Documentation of open requests, completed edits, QA notes, and next-step recommendations.

What gets scoped separately

The care plan protects both sides by naming what is outside routine maintenance. If a request requires design, development, strategy, database work, deep QA, or a larger business decision, it should be quoted before work begins.

• New pages, redesigns, new page templates, new sections, or full landing page builds.
• Custom features, portals, dashboards, ecommerce changes, API work, database work, or app integrations.
• Full SEO campaigns, accessibility audits, malware cleanup, emergency recovery, or security remediation.
• Large content rewrites, new brand systems, complex analytics setups, or conversion strategy projects.
• Anything that exceeds the included monthly implementation time or changes the original support agreement.

What your team receives

The care plan is a working handoff document. It gives stakeholders a practical view of how the site will be maintained and gives the support team a consistent reference for what matters each month.

• Maintenance baseline with site notes, access notes, critical pages, and monthly support boundaries.
• Support cadence and request process so requests do not disappear into email threads or chat messages.
• Priority list for the first month of care and a record of known risks that should be watched.
• Clear notes on what is included, what needs approval, and what should move to a separate quote.
• A support record that can grow over time as the site changes, launches new pages, or adds tools.

How teams use it after launch

The care plan is especially useful after a rebuild, sprint, or launch because the site has fresh decisions that need maintenance context. It helps new stakeholders understand what exists, helps owners approve the right work, and keeps routine support from turning into a guessing game.

The goal is simple: keep the website easier to support, easier to review, and easier to improve without pretending monthly maintenance is unlimited development.