Skip to content
TECHOPS / RECURRING WEBSITE CARE

Keep your site maintained. Know what is covered.

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.

Coverage clarity

What a maintenance plan can cover.

The table describes planning categories, not an automatic entitlement. Each task, frequency and owner is confirmed for your website.

Website care planning matrix — final responsibilities confirmed in your plan
AreaCare-plan optionNeeds separate agreement
Software updatesAgreed WordPress, theme and plugin updates with compatibility reviewMajor custom-code refactoring or paid-license renewals
Backup readinessCheck backup ownership, schedule and available restore pathUnplanned disaster recovery or a full data migration
Website healthDefined functional, security and availability checksGuaranteed monitoring coverage, penetration testing or emergency SLA
CommunicationAgreed maintenance notes, issues and decision pointsUnlimited revisions, new features or campaign delivery
Shared responsibility

A good plan has named owners.

Care works best when updates, hosting, licenses, content changes and issue approvals have clear responsibilities. We confirm the access model before recurring work begins.

MONO / AS AGREED

Maintenance operator

Carry out scoped technical checks, document observed issues and recommend approved changes.

CLIENT / OWNER

Website decision maker

Authorize access and major changes, maintain relevant licenses and confirm business priorities.

THIRD PARTIES

Infrastructure providers

Hosting, domain, payment and external tools retain their own support and service terms.

Plan boundaries

Preventive care is not unlimited development.

The care proposal lists tasks, frequency, exclusions, reporting and out-of-scope work authorization.

In scope

  • Website and hosting ownership review at onboarding
  • Agreed WordPress/plugin/theme maintenance tasks
  • Backup responsibility and restore-path verification as scoped
  • Defined functional/security/health check schedule
  • Issue notes, maintenance summary and escalation routing
  • A consultation on plan fit, cadence and service boundaries

Defined separately

  • New pages, campaigns, redesigns or feature implementation
  • Unlimited incident response, emergency SLA or zero-downtime guarantee
  • License, hosting, domain and third-party subscription fees
  • Full breach response, malware eradication or disaster recovery without separate scope
  • Content production, SEO campaigns or paid advertising management
Onboarding / Scope first

Build a plan your team can operate.

We assess the website's condition and dependencies before agreeing a maintainable recurring service.

  1. 01

    Inventory

    Confirm website stack, access roles, vendors and licenses.

  2. 02

    Baseline review

    Identify pending maintenance, known defects and backup conditions.

  3. 03

    Agree coverage

    Define cadence, responsibilities, approvals and reporting terms.

  4. 04

    Operate & reassess

    Run approved tasks and propose any work outside the plan separately.

Helpful details

Before choosing ongoing website care.

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

A maintained website starts with clear ownership.

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.