Moving your website: questions to ask your hosting supplier
Hosting is the service that makes your website available online. A hosting move should keep the site and its important functions working, with clear…
The Kay & Co. resource library
Hosting & website support
Understand who looks after your website, what support includes and how problems will be noticed and handled.
Find an answer
Search a question, a task or a few words.
Search results
Matching resources
A useful starting point
Start here
Know what your website maintenance agreement covers
A support agreement names the main website but omits its forms, document library and third-party booking link. When a journey fails, responsibility is…
Give suppliers a reproducible fault report
The supplier cannot reproduce a fault because the report omits the affected address, action and conditions.
The complete list
All hosting & website support resources
Showing 1–24 of 38 resources, ordered by title.
Address website faults that keep coming back
The same form error is repaired repeatedly, but each ticket is closed independently. Nobody investigates why the issue returns. Repeated repairs may restore…
Check connected services after changing domain settings
After a DNS change, the main website opens correctly but an important subdomain and email-related records were overlooked. A successful homepage check is…
Check external dependencies before changing unrelated website code
A public function fails because an external dependency is unavailable, but the team begins changing unrelated website code.
Check important booking and information links
A key external booking destination changes while the clinic website itself stays unchanged. Its prominent call to action now leads to an error. Your site…
Check the essential files behind an apparently working page
The article returns successfully, but a required stylesheet or script fails and the public experience is incomplete.
Close an incident by repeating the visitor's original task
The supplier deploys a fix and marks the ticket resolved, but nobody repeats the visitor action that first failed.
Compare support quotes against the whole website journey
The maintenance proposal covers website hosting, but important downloadable assets live in a separate account outside its scope.
Distinguish a blocked monitor from a public website outage
The alert reports an outage even though ordinary visitors can reach the site. The probe receives a security challenge.
Do not close an intermittent fault after one successful attempt
A page works when support checks it, so the incident is dismissed despite repeated failures under specific conditions.
Document the settings needed to rebuild your service
A working application relies on undocumented settings changed during earlier incidents. Rebuilding from source alone would not reproduce its behaviour. A…
Give a website incident one clear coordinator
Several suppliers join a fault investigation and each assumes another is coordinating it. Updates conflict and key decisions are not recorded. Several…
Give certificate renewal problems a clear owner
A certificate renews automatically until a configuration change breaks renewal. No one notices because the site still works before the expiry date. A…
Give certificate warnings a clear technical owner
The monitoring tool warns about a certificate, but staff do not know whether the host renews it or someone must act.
Give cross-supplier faults one coordinated route
The host and website developer each say a fault belongs to the other, leaving the practice to coordinate technical diagnosis.
Give software renewals a service and budget owner
Several software subscriptions renew automatically, but the budget holder and day-to-day owner are recorded only in old emails. Subscriptions can renew…
Give suppliers a reproducible fault report
The supplier cannot reproduce a fault because the report omits the affected address, action and conditions.
Give your maintainer a clear brief for small changes
A support inbox receives small edits without screenshots, URLs or approved wording. The maintainer spends more time clarifying requests than making them.…
Group related alerts without hiding separate problems
One shared dependency fails and produces dozens of near-identical messages, overwhelming the practice's support channel.
Keep a useful list of your digital services and their owners
The organisation has a list of laptops but no maintained record of websites, domains, software subscriptions and integration owners. A useful digital…
Keep active, retiring and archived services distinct
An old patient information microsite remains listed as active even though its content owner has retired it. The register does not distinguish live, retiring…
Keep domain renewals from being overlooked
A domain renewal notice goes to an unattended mailbox. The website remains online today, but nobody is checking the next renewal deadline. A site can work…
Keep staff informed with useful outage updates
An outage message says only that the team is looking into it. Staff cannot tell which services are affected or what they should do meanwhile. During an…
Keep website facts current as services change
Technical updates run regularly, but nobody checks whether the website still shows the correct team members and service arrangements. A technically healthy…
Keep your digital service register current
A detailed inventory was created during a project, but new services have since been purchased without being added. The register is becoming unreliable. A…