Monitor important downloads as well as the homepage
The monitor checks only the homepage response, so an important public document can disappear without an alert.
The Kay & Co. resource library
Support & operations resources · page 4
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 73–96 of 111 resources, ordered by title.
Monitor whether visitors can complete an enquiry
An uptime monitor reports success whenever the homepage responds, while the enquiry form has been failing since a dependency changed. A homepage…
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…
Plan ahead when a software platform approaches end of support
A business application depends on a platform approaching end of support, yet replacement planning has not been assigned or budgeted. A platform approaching…
Plan domain-setting changes around all affected services
A website move requires changes to the domain settings, but the team has not recorded the existing arrangement or identified which settings support email…
Preserve the useful section in an old bookmark
A retired guide points to its replacement, but a bookmarked section no longer exists. Visitors land far from the needed explanation.
Prioritise slow pages by the task they interrupt
A rarely visited archive scores worse than a heavily used service page with a different practical delay. Prioritise with the affected task, audience and…
Prioritise technical improvements by the problems they solve
The team has a long list of code improvements, but business owners cannot tell which reduce service risk or support planned features. A long list of…
Prove that an incoming supplier can restore the backup
The organisation receives a backup file, but the incoming maintainer cannot identify its format or required tooling.
Publish the version your practice actually approved
The practice approves one preview, but the supplier publishes a later build containing additional unreviewed changes.
Recognise failures in the website journeys that matter
A form stops accepting enquiries, but the initial ticket is treated as a minor content request because the homepage still loads. A homepage loading does not…
Remove unnecessary detours from old website links
A bookmarked resource passes through several historical addresses before reaching the current guide. Repeated reorganisations can leave a trail of addresses…
Require a fair before-and-after performance comparison
The before test uses a slow mobile profile while the after test uses a different device and network setup.
Require a working publishing handover, not just a folder
The incoming maintainer receives source files but cannot produce the current public website from them. Ask for a reproducible publishing demonstration from…
Restore a known acceptable version, not merely the previous one
The team chooses the immediately previous deployment even though that version was never confirmed healthy.
Restore compatible website code and content together
An older site version expects a content structure that the current editing system export no longer supplies.
Review automated publishing access as well as named users
Named user accounts are removed, but an automation credential can still publish changes to the website. Inventory non-human access alongside people. Ask the…
Review software updates with their service impact in mind
An application has accumulated library updates, but the team cannot distinguish security-relevant fixes from changes that may alter behaviour. Software…
Review supplier access when the work ends
A supplier finishes its work, but its team members remain on several administrative accounts because access was granted through different systems. Access…
Review support results beyond closed-ticket counts
A monthly support report counts closed tickets but does not show repeat faults, ageing work or missed updates. High activity may conceal unresolved service…
Review the cost of additions after the website launches
The website meets its initial target, but later marketing additions accumulate without any release review of their cost.
Send old guide links to a genuinely useful replacement
Old guide links all land on the homepage after a redesign. Visitors lose the specific explanation they expected.
Send website alerts to people who can act
Several systems send alerts to a shared mailbox, but messages contain no affected service, severity or next step. Staff begin ignoring them. Alerts lose…
Send website alerts to people who can act on them
The technical check detects failures, but its notification destination belongs to an absent worker or retired supplier.