Necessary
Always activeSupports security, form reliability and remembering your privacy choice. It is not used for advertising.
Routine updates, backup checks, health reviews and an agreed contact route help your website stay manageable. Build a care plan around your actual platform and responsibilities—not vague unlimited support.
Maintenance cadence, reporting, support hours and escalation terms are specified in the agreed plan. No unverified uptime or response promise.
Concept only · Coverage and scheduling are confirmed in writing
The table describes planning categories, not an automatic entitlement. Each task, frequency and owner is confirmed for your website.
| Area | Care-plan option | Needs separate agreement |
|---|---|---|
| Software updates | Agreed WordPress, theme and plugin updates with compatibility review | Major custom-code refactoring or paid-license renewals |
| Backup readiness | Check backup ownership, schedule and available restore path | Unplanned disaster recovery or a full data migration |
| Website health | Defined functional, security and availability checks | Guaranteed monitoring coverage, penetration testing or emergency SLA |
| Communication | Agreed maintenance notes, issues and decision points | Unlimited revisions, new features or campaign delivery |
Care works best when updates, hosting, licenses, content changes and issue approvals have clear responsibilities. We confirm the access model before recurring work begins.
Carry out scoped technical checks, document observed issues and recommend approved changes.
Authorize access and major changes, maintain relevant licenses and confirm business priorities.
Hosting, domain, payment and external tools retain their own support and service terms.
The care proposal lists tasks, frequency, exclusions, reporting and out-of-scope work authorization.
We assess the website's condition and dependencies before agreeing a maintainable recurring service.
Confirm website stack, access roles, vendors and licenses.
Identify pending maintenance, known defects and backup conditions.
Define cadence, responsibilities, approvals and reporting terms.
Run approved tasks and propose any work outside the plan separately.
Helpful details
Practical answers before requesting a scope.
No. Recurring maintenance and new feature or design work have different scopes. The plan states any included change allowance explicitly.
Only if a written support agreement specifies coverage and response terms. No response time is guaranteed by this page.
Third-party fees and ownership are identified during planning and remain separate unless a written agreement says otherwise.
We first confirm the hosting and backup strategy, available restores and the changes planned. Backup/restore duties and frequency are defined in the plan.
Define a sensible care plan
Tell us about your CMS, providers, current update process and what recurring help your team needs. We will propose realistic coverage.
Scope and next steps are agreed before implementation.