Practical tool

Technology health check

Turn 14 answers about access, security, resilience, data and workflows into evidence-backed actions.

← All tools
Checking local storage. Your default working copy is shown while this check completes. Nothing is sent to Coops.uk or put in the page address.

Use “unsure” until somebody checks real settings, records or a recent test. A confident guess is not evidence.

1 Does the co-op control its domain registration and recovery details?

Ownership & access

2 Do people use their own accounts rather than shared logins?

Ownership & access

3 Are important accounts protected by passkeys or two-step verification?

Security

4 Is administrator access limited and recoverable if someone leaves?

Ownership & access

5 Is there a repeatable process for leavers and role changes?

People

6 Are devices and important software kept supported and updated?

Security

7 Are important records backed up separately from everyday access?

Resilience

8 Has someone recently tested restoring a useful file or system?

Resilience

9 Are new payment details checked through a known separate channel?

Money

10 Do you know what member data is held, why and who can access it?

Data

11 Are shared files organised with access appropriate to people’s roles?

Collaboration

12 Is someone responsible for website updates, access and recovery?

Websites

13 Do automations and AI tools have owners, limits and failure checks?

Automation & AI

14 Could someone find the first steps and contacts for an incident?

Resilience

Current result

Checks and actions to take next

This is a self-reported action plan, not an audit, percentage secure or security certification. Verify each answer with evidence.

0of 14 answered
0no
0unsure
0yes
Nothing has been answered yet. Choose no or unsure to see a specific action and the evidence to check.
14 unanswered questions
  • Does the co-op control its domain registration and recovery details?
  • Do people use their own accounts rather than shared logins?
  • Are important accounts protected by passkeys or two-step verification?
  • Is administrator access limited and recoverable if someone leaves?
  • Is there a repeatable process for leavers and role changes?
  • Are devices and important software kept supported and updated?
  • Are important records backed up separately from everyday access?
  • Has someone recently tested restoring a useful file or system?
  • Are new payment details checked through a known separate channel?
  • Do you know what member data is held, why and who can access it?
  • Are shared files organised with access appropriate to people’s roles?
  • Is someone responsible for website updates, access and recovery?
  • Do automations and AI tools have owners, limits and failure checks?
  • Could someone find the first steps and contacts for an incident?

Questions still unanswered

  • Does the co-op control its domain registration and recovery details?
  • Do people use their own accounts rather than shared logins?
  • Are important accounts protected by passkeys or two-step verification?
  • Is administrator access limited and recoverable if someone leaves?
  • Is there a repeatable process for leavers and role changes?
  • Are devices and important software kept supported and updated?
  • Are important records backed up separately from everyday access?
  • Has someone recently tested restoring a useful file or system?
  • Are new payment details checked through a known separate channel?
  • Do you know what member data is held, why and who can access it?
  • Are shared files organised with access appropriate to people’s roles?
  • Is someone responsible for website updates, access and recovery?
  • Do automations and AI tools have owners, limits and failure checks?
  • Could someone find the first steps and contacts for an incident?