Faith Forge LabsWebsite Maintenance
4 MIN READ

What does your website care plan actually cover?

Check which repairs, edits, backups, and provider costs are included before comparing the monthly price.

When comparing proposals, ask what each plan delivers and what your organization still needs to do. A narrower plan can be entirely suitable if the boundary is clear. The difficulty is an assumption that becomes visible only when a task fails.

Existing faults versus future routine

A new support arrangement doesn’t automatically repair every historical problem. The site may have outdated components, broken integrations or missing access that require initial work. Ask how the provider assesses the starting condition and records exclusions.

If stabilization is separate, identify its scope and decision point. Otherwise the business may believe an old enquiry fault is being repaired while the maintainer believes the plan begins with routine updates only. Neither a long checklist nor a recurring invoice resolves that misunderstanding.

“Content changes” can mean different responsibilities

A plan might include publishing approved text but exclude writing it, checking professional claims or revising a downloadable document. Those distinctions matter. A request to change collection instructions can involve several pages, an attachment and a notification template.

Ask how included edits are defined and how related material is identified. The business should retain factual approval, while the implementation scope should state what presentation and link checks accompany the change. Count the complete visitor path rather than just the number of edited words.

Backup storage versus recovery work

Keeping copies and proving they can restore a usable website are different activities. Ask what material is included, how long copies remain available, who can retrieve them and whether a restoration exercise is included.

Also clarify the work involved in an actual recovery. Choosing a snapshot, protecting newer records, preparing an environment and verifying the result can require decisions beyond pressing a restore control. The plan shouldn’t imply that every such responsibility is included merely because backup jobs run.

Alerts versus staffed response

Monitoring configuration can produce notifications without providing continuous review or repair. Ask who receives an alert, what happens outside the agreed coverage and how the issue is prioritized. A provider's availability metric isn’t the same as a service-level commitment from the maintainer.

Different response stages should be distinguishable: acknowledging a request, beginning investigation, applying a workaround and completing a repair. A promise about one stage shouldn’t be interpreted as a guarantee about all of them.

Licenses, providers and access

Hosting, paid plugins, monitoring tools and storage can create continuing charges. Identify who owns each subscription, who receives renewal notices and what happens if a license isn’t renewed. Some update or support capabilities may depend on the provider arrangement.

Business ownership also has practical value. If a change of supplier requires reconstructing access to every account, the handover can become a substantial project. Named permissions and a maintained provider inventory reduce that uncertainty without requiring all credentials to be shared in ordinary documents.

The cost of unclear approval

Several people may request changes, but someone must decide which information is authoritative and which expenditure is approved. Conflicting instructions create rework and can publish the wrong version even when the technical edit is correct.

A support plan should identify request and approval responsibilities. For a small organization, the process can remain simple. The useful part is knowing whose decision completes the request, particularly when the usual contact is absent.

Review the evidence of care

Ask what the report contains. A list of completed software installations doesn’t show whether selected tasks were checked. A report that repeats unresolved issues without a next owner can make a problem appear managed while no decision advances.

Choose an arrangement whose records help your team act: what changed, what was verified, what remains open and who decides next. The total cost includes the work still required inside the business, not just the provider's fee.

See scope and budget, the maintenance guide and support planning.