Website Management: A Small Business Plan

Website management responsibility plan

Open a task that someone can finish.

Example change record: replace the contact number on Contact, the footer and the mobile call action. The business owner supplies and approves the new number. The publisher records the affected URLs and checks whether structured contact information or an external business listing also needs a separately owned update. This is an illustrative task, not a reported incident.

Acceptance means the displayed number and phone-link destination agree, the call action opens correctly on a phone and the owner confirms the intended line receives calls. A screenshot alone does not establish call delivery.

Use the responsibility table to separate approval from execution.

The table above identifies recurring workstreams. For each actual task, add the approver, executor, reviewer, due date and evidence needed to close it. One person may hold several roles, but the record should still distinguish their decisions.

For a failed enquiry route, the sales owner confirms the intended inbox and the technical owner investigates delivery. Send a test submission and verify receipt separately from the visitor confirmation. Escalate to the named owner when either side fails.

Write the operating plan for the platform you actually use.

Record domain and hosting owners, renewals, administrative access, integrations and the recovery method. Specify which updates the provider performs and what must be tested afterward. A managed platform and a self-hosted CMS have different operating responsibilities.

For backups, state what is covered, who can restore it and how restoration is checked. Do not list a backup as verified merely because a scheduled job exists. Keep the recovery plan usable when the usual publisher is unavailable.

Review changes through the customer task.

After a content or component change, check the affected page and its next action on the relevant devices. New forms require labels, keyboard use, understandable errors and a received-record test; new images require appropriate alternatives and delivery sizes.

Use performance diagnostics and real-user data where available to investigate regressions. Record the page and date so the reviewer can reproduce the observation. A green homepage score does not verify a changed booking or download path.

Close the review with decisions, not a generic report.

At the agreed review interval, list completed changes, unresolved failures, owners and next dates. Review access after a staff or supplier change and confirm renewal contacts before accounts expire. Set the cadence around actual business changes and technical responsibilities.

Report search visibility, visits and received enquiries separately. A new landing-page programme, redesign or integration should have its own scope when it falls outside recurring maintenance. Keep the task record and acceptance evidence with the handover material.