Compare supplier proposals by observable outcomes
The proposal prices a website improvement as one package, making it difficult to know what acceptance evidence is included.
The Kay & Co. resource library
Support & operations resources · page 2
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 25–48 of 111 resources, ordered by title.
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.
Complete access handover only after administrators test it
The supplier sends invitations and closes the project, but the intended administrators have not accepted or tested them.
Confirm everyday work is possible after recovery
A system is technically restored, but users cannot complete the essential workflow because permissions and a dependent integration were not checked. A…
Confirm the release reached the public domain
The hosting dashboard reports success, while the organisation's main domain still serves the previous release.
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.
Distinguish a faster test result from the experience of real visitors
A supplier reports a better synthetic performance score, but available field evidence still indicates a poor experience for part of the audience.
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…
Fix a section that keeps sending visitors round in circles
The website opens normally except for a section that continually redirects. Two routing layers may contradict each other.
Get a complete working handover from a departing supplier
A website supplier is leaving, but the handover request mentions only source code. Hosting configuration, design assets and maintenance instructions are…
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 a website move one owner across suppliers
One supplier changes the domain while another controls redirects. Neither verifies the complete incoming journey.
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 recovery a tested backup administrator
The incident owner knows which deployment to restore, but the only authorised account holder cannot be reached.
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 temporary campaign redirects an end date or trigger
A short-lived routing change remains after its campaign ends and masks the original destination. A temporary campaign rule needs an exit condition, not just…
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.
Identify which project actually serves the live website
Several similarly named repositories and hosting projects exist, and the handover does not state which one serves the public domain.
Include external settings when planning a rollback
The previous website version returns, but an external configuration still points to the new incompatible behaviour.