The Kay & Co. resource library
Keep your website working, know who to call when something goes wrong and make sure your practice can get back up and running.
Search a question, a task or a few words.
Search results
31 resources
Explain what your practice needs, compare quotes fairly and know what your supplier will deliver.
Inside this topicHow to explain your website or digital project to a supplier · How to compare quotes for a healthcare app
19 resources
Find out why pages feel slow and ask for improvements that help visitors complete their next step.
Inside this topicCheck how quickly important pages work on a phone · Distinguish a faster test result from the experience of real visitors
53 resources
Check a website update before it goes live and agree how to put things right if a change causes problems.
Inside this topicAgree what a software update must achieve before building it · Publish the version your practice actually approved
38 resources
Understand who looks after your website, what support includes and how problems will be noticed and handled.
Inside this topicMoving your website: questions to ask your hosting supplier · Know what your website maintenance agreement covers
The complete list
Showing 1–24 of 111 resources, ordered by title.
The same form error is repaired repeatedly, but each ticket is closed independently. Nobody investigates why the issue returns. Repeated repairs may restore…
A backup runs nightly, but the organisation has never agreed how much recent work it could lose or how long a service could be unavailable. Backup frequency…
A software update is described as improving the dashboard, but nobody has specified what a user should be able to do differently or how errors will be…
A supplier recommends a more expensive hosting plan based on a slow page score alone. Ask which part of the delay the upgrade is expected to improve.…
A supplier edits the live output directly, and the next routine release silently restores the original fault.
After a DNS change, the main website opens correctly but an important subdomain and email-related records were overlooked. A successful homepage check is…
The recovery team declares success when the root page loads, while important articles and files remain absent.
A shared dependency changes, but the sample checked for unintended effects excludes other pages using it.
A departing software supplier provides a data export that opens successfully but omits important relationships and uses undocumented identifiers. An export…
A public function fails because an external dependency is unavailable, but the team begins changing unrelated website code.
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…
An environment setting is copied into the release and public functionality points to a test service. Validate environment-specific destinations without…
The article returns successfully, but a required stylesheet or script fails and the public experience is incomplete.
Staff see quick loads because their browsers already hold assets, while a new visitor starts with an empty cache.
An update is deployed and the ticket closes immediately. No one verifies the live enquiry journey or records which version is running. A successful…
The original deployment is restored, yet some visitors continue receiving the faulty response from a cache layer.
A team backs up website files but has no recoverable copy of form configuration or the records needed to rebuild its publishing process. A backup needs to…
The recovery plan tells staff to use a messaging platform that is itself unavailable in the chosen scenario. An outage can affect the messaging tool named…
A recovery exercise assumes every administrator, system and instruction is available. It misses the obstacles that could make a real outage difficult.…
A planned website change overlaps with a major campaign launch and the only available support engineer's leave. The technical task is small but recovery…
The site depends on a licensed component whose renewal and use rights are controlled outside the organisation.
The supplier deploys a fix and marks the ticket resolved, but nobody repeats the visitor action that first failed.
The exercise succeeds, but the temporary restored copy stays accessible and begins circulating as another version of the site.
Different suppliers publish independent updates, and the later deployment removes changes accepted in the earlier one.
