Scope & preparation
When this is useful
Maintenance is useful when a website is already live but updates, fixes and ownership are unclear. A small content change and an urgent service failure need different processes. A baseline assessment helps identify what can be maintained safely and what needs a separate repair or rebuild.
How ADPR can help
ADPR can discuss maintenance around the existing stack and required coverage. Backups, staging, deployment access and rollback responsibilities should be established before changes. Response times, included work and third-party costs must be set in the support agreement.
A typical process
Assess the site, access arrangements and known issues.
Agree update categories, checks and support boundaries.
Apply changes through a reviewable process and record the outcome.
What to prepare
- Site URL and technology details if known
- Current hosting and administrator ownership
- Issue list and desired support coverage
Possible scope outputs
- Maintenance baseline and scope
- Agreed updates or fixes
- Change log and handover records
The proposal will confirm what is included, who is responsible and the applicable timeline. These are scope examples, not a fixed package.
Questions worth asking
Does maintenance mean permanent uptime?
No. Availability depends on several systems and providers. Support coverage and incident responsibilities should be defined explicitly.
Can updates be made directly on the live site?
The process should use appropriate backups, verification and rollback arrangements. A staging environment is useful where the stack supports it.