Website Maintenance & Managed Support

Establish the supported baseline

We record the website platform, hosting environment, current versions, connected services and approved source baseline. Access should match the responsibilities agreed for the project. Existing suppliers and third-party subscriptions remain separate unless a specific transfer is authorized. Unknown dependencies or unsupported code are identified for review.

Monitor the important journeys

Useful checks include public availability, HTTPS, selected security headers, form gateway readiness and source integrity where supported. Monitoring needs a clear owner and an escalation path. A successful homepage response does not prove every customer journey works, and monitoring running on the same host cannot independently confirm a total outage of that host.

Update with a recovery plan

Runtime and dependency updates are assessed for compatibility, tested in an appropriate environment and backed up before release. Changes to payment, enquiry or customer systems require checks of their real workflow. A scheduled update check is not the same as permission to install arbitrary new code or change security-sensitive access.

Use bounded automatic recovery

Where appropriate, a recovery mechanism can restore specifically approved public files from a verified release. It should retain preimages, avoid recently edited or unknown releases, verify the result and stop when evidence is uncertain. Recovery is not a substitute for incident investigation, isolated hosting, protected credentials or an independently tested disaster-restoration plan.

Agree coverage and support

The scope states covered components, working hours, response expectations, update responsibilities and how requests are prioritized. New features, content production, major platform migration and third-party charges are considered separately. We retain the distinction between an observed healthy check, a completed repair and a guarantee: no maintenance plan can promise permanent security or uninterrupted service.

Common questions

Discuss your requirements

Tell us what needs to work, who will use it and which systems are involved. Scope, delivery responsibilities and support are agreed for your project.