Website careFaith Forge Labs

Agree support before the next problem arrives

A useful support arrangement explains who handles the website's routine responsibilities and what happens when something unexpected occurs. It should make requests easier to route and decisions easier to approve.

Start with the website's condition

We review the platform, access, providers, important tasks and known issues. A site that already has broken features or unsupported software may need a stabilization stage before a recurring routine is practical. Those findings should be visible in the plan rather than absorbed into an indefinite promise of care.

The business identifies the functions it depends on and the people who can approve changes. A small site can still have a consequential enquiry or booking path. Scope should reflect those responsibilities, not only page count.

Name the included work

The arrangement can specify routine updates, selected checks, approved content changes and defined repair activities. Backup review, restore exercises and monitoring have different purposes and should be named where included. Larger development, migrations and third-party fees need their own treatment.

Agree how additional work is estimated and approved. A request described as “just adding a field” may change validation, stored information, notifications and privacy implications. A clear boundary avoids treating every visually small request as the same amount of work.

Define communication and priority

Identify the request channel, useful report details and person responsible for triage. Priority should relate to business impact and the scope of affected use. A complete failure of the enquiry path differs from a requested wording change for next month.

Acknowledgement, investigation and resolution are distinct stages. Any coverage hours, response expectations and escalation arrangements must be explicitly agreed. This service page does not create a service-level guarantee or imply that a person is continuously available.

Keep providers and owners visible

The host, domain registrar, email provider and software vendors may each control part of the service. The plan records who contacts them and who can authorize fees or account changes. Business ownership and recovery access should remain suitable for a future handover.

The responsibility sheet helps identify gaps. It is particularly useful when an employee or supplier changes, because a working editor login does not reveal every provider dependency.

Review the arrangement as the site evolves

A recurring review can identify completed activity, unresolved faults, upcoming renewals and changes that affect scope. Adding bookings, a new integration or a larger publishing schedule may change the care requirements. The plan should be revisited deliberately rather than stretch through assumptions.

Discuss support planning with the platform, main functions and current gaps. For day-to-day request habits, see using the support arrangement.