Website maintenance: scope, costs and responsibilities
Maintenance may mean ongoing care, a single update or fault repair. Define the site, covered features and who responds to problems. A good agreement clearly separates these tasks.
What should maintenance cover?
Separate technical upkeep from new content and redesign. Updates, backups and checking existing features differ from new pages, design or integrations. A package should state which services are included.
Plan updates with a recovery path
An update can change interactions between the site, extensions and hosting. Plan backups, testing and recovery for important changes. Afterwards test actual tasks such as contact, login or ordering rather than only opening the homepage.
Assign responsibility for evaluating and promptly applying security patches. Automatic updates can help but do not replace ownership of faults and tests. An unsupported extension can need more than a routine update.
Distinguish backup from recovery
A complete backup may require files and database. Agree on coverage, retention and recovery testing. An existing backup file does not prove that the site can be restored from it.
For shops and booking systems, consider losing new orders or appointments. Discuss acceptable data loss and downtime. This turns “backups included” into a verifiable scope.
Separate faults and security incidents
Display faults, outages and suspected attacks need different investigation. Describe symptoms and approximate onset. For a suspected attack, investigate how access occurred; restoring an old backup alone may not be enough.
Agree on coverage and responsibilities
Response time means agreed initial handling, not necessarily complete repair. Clarify contact channels, coverage hours and responsibilities across host, agency and your team. For an urgent outage use existing support; a quote request does not promise immediate emergency help.
| Agreement | Specify |
|---|---|
| Updates | Owner, testing and recovery |
| Fault | Reporting, hours and first response |
| Backup | Scope, retention and recovery |
Compare package and extra work
Compare tasks, included hours and extra charges. An information site and an integrated shop need not require the same care. Outdated technology, diagnosis and initial takeover may be separate; hosting fees do not automatically cover them.
| Cost item | Check |
|---|---|
| Takeover | Initial assessment and corrections |
| Support | Services and included time |
| Extras | Repairs, changes and emergencies |
| Licences | Renewal, ownership and termination |
Prepare takeover and future transfer
List domain, hosting, system and contracts. The new provider will need appropriate access later, not passwords in your public request. Agree on account and licence ownership and handover of documentation and backups at termination.
Frequently asked questions
Is maintenance included in hosting?
Not automatically. Check whether the site, updates, backups and tests are covered.
Can I order a one-time update?
Yes. Agree on backup, compatibility and checks of important features.
Do updates guarantee a secure site?
No. Access, extensions and other components matter too. Maintenance reduces some risks, not every risk.
How do response and repair differ?
Initial handling is not a guarantee that every fault is fixed by then. Agree on both points explicitly.
Must I know the website system?
No. The address and your objective help initial assessment. Technical details can be checked later.
Is the request free?
Your Quoti request is free. Maintenance and extra work are agreed with your chosen provider.
