Understand maintenance through its tasks, not just its name
To understand website maintenance, establish which tasks are performed, on which systems, how often and what happens when a problem appears. The word “maintenance” alone does not define those responsibilities.
A monthly fee might cover updates and backups while excluding content changes, slow-function investigations or new features. Another proposal may cover different work. Connect each business need with the agreed task and its owner.
Start with three questions: what happens without us having to report anything, what is handled when we need it, and what needs a separate proposal? The answers help assess the service without assuming a fee covers every intervention.
A worksheet for reviewing what is covered
Use this table with your team or provider. These are possible activities, not mandatory contract contents or services Nodo91 automatically includes.
| Activity | Useful question | Evidence or agreement to retain |
|---|---|---|
| Updates | Which components are updated and how are they tested? | Change record and functions checked. |
| Backups and recovery | What is copied and who can recover it? | Coverage, retention and agreed recovery tests. |
| Incidents | How is a fault reported and who investigates? | Channel, hours, first response and intervention conditions. |
| Content | Which text, image or product changes are included? | Change types, owner and request process. |
| Licences and services | Who pays, renews and administers each one? | Responsible account, renewal and expected costs. |
| Ongoing review | What is observed and how are findings shared? | Indicators, scope, frequency and delivery. |
Record unanswered questions as open items. They do not necessarily mean someone has failed to deliver: the task may never have been included or responsibility may be shared.
Updating and checking functions are separate tasks
A completed update alone does not show that enquiries, filters or checkout work. Agree which functions will be tested when a component changes and how any problems found will be handled.
WordPress update documentation recommends preparing a backup first. Having a copy and being able to recover the website also need checking; our backup recovery guide helps define that work.
Maintenance can address outstanding tasks without resolving every system limitation. Updating a website does not establish why its search is slow or whether an integration still meets the business’s needs. Those questions need a focused review.
When maintenance, an assessment or advice fits
Consider the outcome you need. A known, repeated job, such as applying updates under an agreed procedure, can be defined as a recurring task. Understanding a fault or choosing improvements may require an assessment.
- Operational maintenance: performs the recurring tasks set out in the proposal.
- Audit or assessment: gathers evidence and delivers findings, limits and recommendations within defined scope.
- Ongoing advice: helps interpret changes, assess proposals and review priorities with knowledge of the website.
These functions can complement each other. One company may provide several if the proposal explains each one. An assessment does not automatically include implementing recommendations, and advisory support does not replace the team applying changes.
An example: the website is updated but the catalogue remains slow
Fictional example distinguishing tasks. It does not describe a client contract or result.
A shop receives a complete update record, yet filtering products still takes time. Its service covers component updates and agreed journey checks, but not investigating the search system’s internal performance.
The next conversation can establish where the delay occurs and what investigation is needed, rather than assuming another maintenance package will remove its cause. Our worksheet for slow pages and tasks helps prepare that information.
If investigation identifies a correction, implementation and verification are agreed afterwards. Each step has a clear delivery and supports a decision based on available information.
Clarify what incident support means
“Support included” can leave important questions open. Establish the reporting channel, who receives reports, when a first response is due and which work that support covers.
A first response may acknowledge the issue, offer direction or request information; it is different from resolving the fault. If your activity needs immediate intervention or out-of-hours coverage, check which service has expressly been contracted for that need.
Where several providers are involved, identify who coordinates the review. A form may depend on both the website and email, requiring investigation of separate stages. An up-to-date account and permission inventory also helps.
Where the Nodo91 Plan can help
The Nodo91 Plan gives you a team to turn to for technical advice, a monthly review of agreed indicators and components, and a quarterly summary. It can help you assess a maintenance proposal, understand an alert or review priorities.
The plan covers advice and agreed review work. Applying updates, restoring backups, implementing improvements and new investigations outside that work are scoped and quoted separately. It does not include permanent monitoring or emergency resolution.
Bring together your existing scope and unanswered questions to choose the next step. Clarifying responsibilities may be enough; where the website’s condition is unknown, we can discuss the initial assessment needed. We are here to help you organise those needs and understand which support fits.