Include leaflets and downloads in a website move
Webpage redirects work after a migration, while old brochure addresses fail. The move inventory omitted files.
The Kay & Co. resource library
Support & operations resources · page 3
Keep your website working, know who to call when something goes wrong and make sure your practice can get back up and running.
Find an answer
Search a question, a task or a few words.
Search results
Matching resources
The complete list
Support & operations resources
Showing 49–72 of 111 resources, ordered by title.
Include old bookmarks in every page-address change
A new page address works, but the release checklist never tests previously shared links. Treat compatibility as part of the rename rather than a later SEO…
Include separately stored documents in the recovery plan
The website code restores correctly, but linked documents lived in a separate service outside the backup scope.
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 analytics access when an agency relationship ends
The dashboard belongs to an agency-controlled account, and the practice cannot review its own website evidence independently.
Keep branch-specific booking links from being replaced by defaults
A branch page should use its own booking destination, but a shared website setting replaces it with the default practice link. The local value still looks…
Keep campaign information intact when links move
A campaign link reaches the correct guide, but its source information disappears in transit. The redirect should preserve only the query information the…
Keep control of the old domain after a website move
The new site works, but old bookmarks rely on a domain nobody plans to renew. Redirect continuity depends on ownership.
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 recovery rehearsals from sending real messages or requests
A recovery exercise starts an old website copy whose scheduled jobs or outgoing hooks could affect live systems.
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…
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…
Know who controls your domain and its renewal
A clinic's domain is registered through a former supplier, and the organisation does not know which account controls renewal or DNS changes. Your domain is…
Make a performance fix reach the whole affected page family
The supplier optimises one article but similar pages still use the older implementation. Ask whether the repaired behaviour comes from shared code or a…
Make monitoring detect a guide sent to the wrong page
A broken guide redirects to the homepage, and the monitoring service treats the final successful response as healthy.
Make new pages and their supporting files work together
The new published page is public, but visitors receive an older script or stylesheet and see inconsistent behaviour.
Make publishing work without one developer's laptop
The developer's preview works, but production lacks resources created by an unrecorded local step. Ask the supplier to rebuild from the shared project using…
Make recovery possible when the usual administrator is away
The person who normally manages backups is unavailable, and the only recovery instructions depend on an account they alone control. Recovery becomes harder…
Make sure someone can pause a faulty release
The publication process continues after a critical check fails because release ownership is unclear. Agree a concrete stop condition and an authorised…
Measure recovery from a meaningful start to a verified finish
A supplier reports a fast restore, but timing excludes access preparation and stops before public validation.
Measure the delay your team actually reported
A manager reports a specific slow action, while the supplier focuses on improving an unrelated headline score.