Most businesses check a web developer's portfolio and references before hiring them. Far fewer check whether that developer is actually insured, registered for data protection, or has any plan for what happens if they become unavailable. Those questions matter more than they might seem, especially for a site that handles customer data, payments, or anything the business depends on daily.
ICO registration and data protection
Anyone handling data connected to your users, contact forms, account details, order history, is legally required to register with the Information Commissioner's Office under UK data protection law. It costs very little and takes minutes to set up, so a developer who hasn't done it either doesn't know the requirement exists or hasn't taken it seriously. The ICO register is public and searchable, so this is one of the easiest things to check independently rather than take someone's word for it.
Professional indemnity and cyber insurance
Two types of cover matter for anyone doing technical work on your site. Professional indemnity covers mistakes and oversights in the work itself. Cyber insurance covers incidents involving data: a breach, a hack, exposed customer records. Without either, a mistake or a security incident becomes the business's problem to pay for, not the developer's.
It's worth asking for the actual policy limits, not just confirmation that insurance exists. £50,000 of cover and £1,000,000 of cover are both technically "having insurance," but they cover very different scales of problem.
What happens if they become unavailable
Ask what happens to the business if the developer is unreachable for a month, whether that's illness, a family emergency, or simply moving on to something else. Is there documentation another developer could pick up from? Is there anyone else who has ever touched the codebase? A single point of failure isn't unusual for a smaller supplier, but it's worth knowing about before signing rather than discovering it during an emergency.
How to actually verify each one
Checking these things properly takes a few minutes. Search the ICO register directly instead of relying on what a supplier tells you. Ask for a certificate of insurance instead of a verbal confirmation. If they mention documentation or a backup plan for unavailability, ask to see an example.
If you're evaluating a developer or agency and want a second opinion on what to ask, get in touch with Karl.