Technical updates
Review and install necessary changes to the platform and components included in the service.
WEB/008Website maintenance
A published website.
A job that continues.
We maintain your website through agreed updates, checks and content changes. You have a channel for reporting issues and a clear plan of what is reviewed, when and with what coverage.
Look after the foundations.
Support the changes.
Publishing does not stop content, platform or business needs from changing. A defined maintenance service makes clear what gets checked and who to contact when action is needed.
Functionality checks
Review important pages and actions, such as forms, navigation or the purchase process.
Content changes
Add changes and new elements within an agreed time allocation or scope.
Issue management
A channel and process for assessing errors and organising their resolution.
Your website in use.
Ongoing care, agreed.
We first review the website and its access. The proposal defines tasks, response times and which work requires an additional quote.
Starting point
- Web
- Components
- Needs
MaintenanceOutcome
- Updates
- Reviews
- Improvements
A maintenance plan.
Defined coverage.
These are the elements we define in the proposal. The final scope depends on your starting point and business priorities.
/001Initial review
We identify the platform, dependencies and outstanding problems before taking on maintenance.
/002Work plan
We agree on updates, backups, checks and their frequency according to the type of website.
/003Incident channel
We define how to report a problem, which information to provide and the response times covered by the agreement.
/004Work log
We record the work done and the recommendations that require another phase.
/005Handover and continuity
We hand over the access, documentation and guidance covered by the agreed scope. Follow-up or maintenance is defined separately if commissioned.
Review the foundations.
Support daily use.
(4)Review the existing website
We check the platform, access, licences and outstanding problems before taking on maintenance.
Agree the plan
We define tasks, frequency, backups and incident coverage, distinguishing content changes.
Maintain and check
We carry out the agreed work and check forms, navigation or other affected features.
Record and prioritise
We record completed work and assess improvements that need a separate task or quote.
Thoughtfully built.
Ready to continue.
Your content
We agree on who prepares the copy, photography, translations and brand materials. The website should explain your business using information you can validate.
Access and ownership
We define domain, hosting, accounts and tools so you know where each piece is and who manages it.
Continuity
We distinguish the initial delivery from updates, licences and future improvements. Further development has a defined scope and an owner.
Before we start.
(5)Does this include 24-hour support?
Service hours, response times and issue coverage are defined explicitly. The service must fit the project's scale and needs.
Can you maintain a website you didn't build?
We can assess this after a technical review. We need access and information about licences and components. Any initial remedial work is quoted separately.
Does it include new pages or features?
Included changes are set out in the plan. A new section, integration or feature may need its own scope and quote.
Which costs are separate?
The proposal distinguishes maintenance from domain, hosting, licence and external service costs, so you know what each charge covers and who manages it.
How do I report an issue?
We agree the channel and the information needed to investigate a problem, alongside the contracted hours and response times.
Engineering × Design.
For the next step.