Service hub

Keep the useful parts working.

Defined website care for the updates, checks and small improvements that need attention after launch.

01 / Service hub

Agree what “care” means

Care can involve routine content changes, platform updates or agreed checks, depending on the supported site. It needs a task list rather than a broad promise to handle everything.

Content upkeep: Agree which pages and materials can change, who supplies the facts and how requests are reviewed.
Technical upkeep: Define the supported platform, update process, test environment and what happens when an update fails.
Useful improvements: Group bounded usability or presentation tasks into a capacity that both sides understand.

02 / Service hub

Response is different from resolution

A response acknowledges and assesses a request. Resolution depends on cause, access, third-party systems and scope. Working windows and escalation arrangements need agreement before recurring support begins; no response-time promise is published here.

03 / Service hub

Specify a service schedule

Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.

Care schedule to agree; no frequency or service level is promised
Task	Frequency to agree	Responsible role	Completion evidence
Approved content edit	As requested within the agreed task limits	Business supplies facts; editor applies approved change	Dated change and live page check.
Platform update	Supported platform/cadence to agree	Maintenance operator	Backup/checkpoint, staging or suitable test and task regression record.
Form-path check	Agreed cadence and authorized test destination	Intake and site owners	Submission, receipt, notification and follow-up states distinguished.
Backup / restore	Scope, cadence and retention to agree	Recovery owner	Files/database inventory and actual restoration test.

Choosing website support that fits

04 / Service hub

Distinguish status from a service promise

Hypothetical planning specimen. It explains the decisions and checks to agree; it is not a completed customer deliverable or a fixed offer.

Illustrative support events, not response commitments
Event	Illustrative status	What remains
Monday 09:00 request	Received in an agreed support channel	No diagnosis or resolution yet.
Monday 11:00 review	Reproduction and dependency identified	Fix scope and authorization may still be required.
After approved change and retest	Resolution evidence recorded	Production verification, known limits and handover.

Website fixes and improvements

05 / Service hub

Agree the plan limits and exit

Use this local worksheet to record the scope and unresolved decisions. Use roles and fictional examples, without credentials or private records.

Use roles and hypothetical examples. These fields stay in this page; no information is submitted or saved.

Task-size rule, allowance and rollover

Do not assume unlimited edits or carryover.

Coverage hours, severity and escalation

Separate acknowledgment, diagnosis and resolution; identify excluded emergencies.

Backup scope, retention, restore test and recovery owner

Possessing a file is not tested recovery.

Cancellation, billing, export and license continuity

Name accounts, files and expiring dependencies.

Scope and pricing

06 / Service hub

Backups need a recovery plan

If backup work is included, specify what is backed up, who controls it, retention, restoration steps and how recovery is tested. A file existing somewhere is not evidence that a restore will work.

To include restoration and known limits in acceptance: Agree the evidence and release checkpoints

07 / Service hub

Keep the limits visible

A redesign, full migration, malware incident or checkout change can require separate investigation and specialist help. This scope does not imply emergency recovery, unlimited development or round-the-clock cover.

08 / Service hub

One fix can stay one fix

A bounded issue can be investigated and quoted as a one-off job. Recurring care is an option when there is a repeatable need and available capacity, not a condition for getting a repair.

Website fixes and improvements

09 / Service hub

Agree the inputs, effort and boundary

Use these work variables to compare a written scope. They are not a price list, payment policy or authorization to purchase tools, media or services.

Scope preparation and cost drivers
Buyer question	Scope answer to agree
What will I receive?	A defined recurring task schedule and completion record
What do I need to supply?	Supported platform, task examples, content/access owner and current recovery arrangements
What changes the effort and cost?	Task size and frequency, staging/update risk, agreed checks, backup/restore responsibility and reporting
What needs separate scope or is excluded?	Unlimited edits, emergency incident recovery, a redesign and unapproved response promises
How will completion and support be defined?	Identify the reviewer, actual test evidence, known limits and handover. Any recurring allowance, fees, cancellation and response arrangement need their own written terms.

To keep the deliverable and finish line reviewable: Review the acceptance and handover checkpoints

Scope and pricing

10 / Service hub

Know how to leave

Agree cancellation, handover, access removal and any final exports. Account ownership and documentation should keep the exit practical.

Choosing website support that fits