Keep the website useful with a support scope you understand.

Maintenance includes more than changing text or installing an available update. The support team needs to know which pages and functions matter, what the site depends on and who can approve a change. A business website, store and signed-in application have different operating requirements.

We can review a site built by another team, subject to access, documentation and its current condition. Onboarding identifies the platform, hosting, domain, code or CMS, external connections and known issues. That baseline informs the work that can sensibly be included and any separate investigation or repair needed before routine support begins.

The agreement should explain how requests arrive, who prioritises them and what evidence accompanies a completed task. Record the work that remains with a host, domain provider or other account owner. Coverage, urgency and response expectations should be stated rather than inferred from a general promise of support.

Inspect what the current backup and release arrangements actually contain. A database copy may not include uploaded files, configuration or the version of the code needed for the same working state. The scope should state which parts are covered and how an appropriate restore check can be conducted.

Also agree when a change should be held, repaired or reversed and who makes that decision. Service hours, escalation contacts and response targets need to fit the platform and the support arrangement. Maintenance does not imply unlimited changes, uninterrupted availability or a guaranteed repair time. Those expectations require explicit review of the actual dependencies and agreed coverage.

Imagine a website publishing a revised public resource. The file is replaced on one page while another page still links to the older edition. The maintenance request should identify the approved new file, its related links and the intended treatment of an earlier shared address. Review that visitor journey and the agreed recovery option before closing the task. This is a planning example, not a Toronto maintenance incident or a claim that a particular client uses this arrangement.