Website review
An initial assessment of the platform, extensions, current issues, access, and maintenance requirements.
Website Maintenance
Keep your website useful after launch.
Broken forms, outdated pages, and uncertain updates can get in the way after launch. We handle agreed checks, fixes, and content changes so your team has a defined plan for keeping the website useful.
Know what needs attention and who handles it.
Maintenance becomes difficult when nobody knows which updates are safe, when backups last ran, or who should investigate a broken form. We review the current setup and agree the responsibilities, access, and priorities before taking on the work.
What we can help with
Updates and routine checks
Agreed software updates and checks of important pages and functions, with compatibility considered before changes.
Backup and recovery arrangements
A review or setup of agreed backup procedures, storage responsibilities, and recovery checks appropriate to the environment.
Fixes and content changes
An agreed allowance or project scope for resolving website issues and keeping published information current.
Illustrative example
An enquiry form can look fine while failing to deliver messages. Including a form check in the maintenance routine gives you a way to test the whole path, from a visitor submitting a request to the intended recipient receiving it.
How the work moves forward
Review the current setup
Identify the platform, known issues, available backups, and the people responsible for hosting and third-party services.
Set the maintenance scope
Agree the work, schedule, reporting, response expectations, and how requests outside the scope will be handled.
Maintain and report
Carry out the agreed work, check the affected functions, and record completed changes and outstanding issues.
Agree the scope before the work starts.
Maintenance coverage depends on the agreed platform, access, and support arrangement. A redesign, major new feature, extensive recovery, or third-party service failure may need separate work. Backup frequency, retention, restoration testing, and support hours must be explicitly agreed. Maintenance cannot eliminate every security issue or outage.
Questions before you start
Can you maintain a website built by someone else?
We can assess it first. We need enough access and information to understand the platform, licences, custom code, hosting, and any existing problems before confirming support.
Does maintenance include content updates?
It can. Agree the type and volume of updates in the scope so routine edits and larger content projects are handled clearly.
What if an update causes a problem?
The change plan should include suitable backups and a recovery approach. Depending on the website, testing in a separate environment may be appropriate before applying an update to production.
Is emergency or round-the-clock support included?
Support hours, response expectations, and emergency coverage depend on the agreed arrangement. They should be confirmed before you rely on them.
Give your website a clear maintenance plan.
Send your website address, platform if known, and the issues or recurring tasks you need help with. We can assess the support it needs.