Know who is looking after your website.
Maintenance should have a clear scope, request route and record of work. We start by understanding your current site, then define the updates, checks and support that are actually included.
Updates and content changes named in the plan.
A clear route to report, assess and prioritize problems.
What changed, what remains open and what comes next.
Make every recurring task explicit.
We do not assume every task is included. The proposal states the platform, number of sites, frequency, allowance, limits and responsible party for each selected service.
Automated monitoring, human availability, a first response and a resolution estimate are different commitments. We define them separately rather than treating an alert as a completed fix.
Eight ways to care for a live site.
Choose a specific task or combine services in a tailored arrangement.
A reported problem needs an owner and a next step.
The exact support hours and targets are set in the agreement. This explains the process without implying 24/7 coverage.
- 01Avoid sending passwords in a public form.
Report
Share the affected URL, symptoms, timing and impact through the agreed support route.
- 02First-response targets apply only if agreed.
Triage
We assess severity, access needed and whether the issue falls within the plan.
- 03Resolution timing depends on the cause.
Act
We investigate and make the agreed fix or recommend a separately scoped change.
- 04Reporting frequency is part of the plan.
Record
We note what changed, check relevant pages and identify any follow-up.
A backup is useful when it can be restored.
Before including backups, we define what is copied, where it is stored, who controls access, how long it is kept and who can request a restore. Restore testing, if required, needs its own agreed process and frequency.
A backup does not replace a launch plan or solve every incident. We also identify which content or transactions may change between the last backup and a restore.
- Files, database and connected data in scope
- Storage location and retention period
- Backup and restore frequency
- Who approves a restore
- Whether restore tests are included
A report should help you decide what happens next.
This sample lists the fields a maintenance report could contain. It is not a record of work performed or a promise that reporting is included in every plan.
- Work completed
- Tasks performed during the agreed period.
- Issues identified
- Problems discovered and their impact.
- Actions taken
- Changes made and pages checked afterward.
- Backup status
- Last backup and any restore-test result, if in scope.
- Open issues
- Unresolved items, owners and next steps.
- Recommendations
- Work to consider for the next period or a separate quote.
Start with a baseline, not assumptions.
We review the platform, hosting, connected services, current issues and safe access process. The assessment identifies what can be supported immediately and what needs remediation first. Coverage begins on the agreed date after access and scope are confirmed.
- 01Initial assessment
Inventory the site and its dependencies.
- 02Secure access setup
Agree on account ownership and appropriate permissions.
- 03Baseline review
Record existing issues and the important visitor journeys.
- 04Coverage agreement
Confirm included work and separately scoped remediation.
Know what needs a separate quote.
A new page template, major redesign, new feature, complex integration, malware recovery or large content migration may require its own scope. The support plan should say how such requests are estimated and approved.
Agree on the terms before coverage starts.
Recurring fee, billing period, payment terms, cancellation notice and any transition work are stated in the agreement. No plan price or service-level target is assumed here.
Before handing over a live site.
Can you maintain a site built by another team?
Often, yes. We assess its platform, access, code and dependencies before agreeing on coverage.
Are updates and backups included every month?
Only when the plan lists them. We state the frequency, scope and limits of each recurring task.
What if the site has an existing problem?
We identify it during onboarding and decide whether it is covered, needs remediation first or requires a separate quote.
Do monitoring alerts mean someone is always available?
No. Automated alerts and human support hours are separate terms, with any first-response target stated in the agreement.
How do we stop or change a plan?
The billing period, cancellation notice and any transition arrangements are set in the service agreement.
Tell us about the website you run.
Share the platform, recurring tasks and issues you want help with. We will review the request and discuss coverage before a plan is agreed.
Do not send passwords through this form.
Tell us what your website needs
Share the platform, recurring work and any current issues. Please do not send passwords.