INTERACTIVE TOOL // DIGITAL DEPENDENCY
AI Dependency Score
How much of your life still works if the cloud, apps and automated services stop helping — or stop being trustworthy? Score ten everyday dependencies and find the offline fallback gaps hidden inside a normal day.
The lights are on, but the smart lock is offline. Your bank app requires an authentication service that is failing. Work files are cloud-only. The car expects online navigation. Family numbers live inside a phone you cannot unlock because account recovery is down. Nothing looks like the end of civilisation — until you count how many basic actions depend on systems outside your control.
Score your dependency
Your AI / digital dependency result
Complete the ten dependency checks to reveal how much of the household relies on connected systems.
This score is about dependency, not whether technology is bad
Connected services are useful precisely because they remove friction. The problem appears when the removed friction becomes a forgotten skill or missing fallback. Contact lists disappear into phones. Documents move into cloud drives. Authentication depends on a single handset. Payment becomes a tap. Navigation becomes a blue line. Each change is convenient until several dependencies are unavailable together.
The score therefore does not reward rejecting technology. It rewards redundancy. A household can use online banking every day and still keep a modest cash fallback. It can use cloud storage while maintaining offline copies of essential information. It can use navigation apps while keeping an offline map and knowing two routes home. Resilience means preserving options rather than living permanently disconnected.
What an AI-controlled information layer could change
Our fictional end-game goes beyond an ordinary outage. Imagine connected services are available but manipulated. Search results are flooded with convincing false instructions. Customer-service agents are synthetic and impossible to distinguish from compromised ones. Smart-home services respond, but nobody knows whether commands are being logged or altered. Digital identity becomes a battleground because every recovery process assumes the network itself is trustworthy.
That is why the highest-risk dependency is often not a gadget but a chain. You need the phone to access the email account, the email account to reset the bank, the bank to pay for transport and transport to reach family. Break one link and inconvenience begins. Break several and an apparently well-equipped household can lose options very quickly.
Reduce single points of failure first
Start with dependencies that block multiple other actions. Write down important numbers. Keep recovery codes securely offline. Store essential documents in more than one form. Have a non-app route for local navigation. Know how you would receive official information during an internet outage. Make sure doors, heating, lighting and other essentials retain safe manual operation where possible.
Then look at work and income. If an outage of one platform would immediately stop you earning, identify which parts of your work can continue locally and what records you need. The objective is not to recreate modern life without technology. It is to make sure a temporary failure does not instantly turn into total household paralysis.
Use the score to find concentration
The purpose of the dependency score is not to label technology as good or bad. It highlights where too many important functions rely on the same device, account, platform or network. A high score in one area suggests that losing that system would remove several options at once.
Look for clusters such as communication, payments, documents and home access all depending on one phone or cloud account.
Reduce one dependency at a time
A useful response may be printing contacts, adding a physical key, keeping an offline document copy or setting up a second legitimate payment route. The goal is not to abandon digital tools; it is to preserve a fallback when one layer fails.
Choose the easiest high-impact dependency first rather than trying to redesign the whole household in one weekend.
Re-score after improvements
Run the tool again after making changes and compare the categories rather than chasing one perfect overall number. Some dependence is unavoidable and often convenient; what matters is whether critical functions still have another route.
The score becomes useful when it tracks progress rather than fear.
Look for single points of digital failure
High AI or digital dependency is most useful when it reveals where one service has quietly become a single point of failure. Think about banking, navigation, work logins, password recovery, cloud files, smart-home controls and communication. If one account lockout or network outage would stop several parts of daily life at once, that dependency deserves attention.
The practical response is not to abandon useful technology. It is to keep a small manual fallback for the few functions that would matter during a disruption. Written contact numbers, offline copies of key documents, a non-smart way to control essential equipment and more than one way to receive information can reduce the impact of a temporary outage without changing how you live every day.
Separate convenience from necessity
Some digital systems are merely convenient while others support income, health, access to money or household safety. Rank dependencies by consequence rather than by how often you use them. A rarely used prescription portal may matter more in a crisis than an app opened dozens of times a day.
Continue from here
Build this topic into a wider plan, then see how the same dependency could fail in an AI-collapse scenario.
Offline-planning baseline
UK Prepare recommends paper phone numbers, household plans, important documents and other offline arrangements that remain accessible during power or communications disruption.