Who Is Liable When Your AI Makes a Mistake?
The answer is more complicated than most AI vendors will tell you — and your contracts, your design choices, and your deployment model all contribute to where liability lands.

An AI system can make a decision that harms someone. It may deny a loan to a person who qualified. It may screen out a strong job candidate. It may send a patient to the wrong level of care. When that happens, someone is liable. The question is who. This is the heart of ai liability for any business. Most AI vendors avoid the answer. In most cases, the business that runs the system is liable. The vendor that built the model is not.
This is not a far-off worry. AI now drives high-stakes choices. It touches credit, jobs, healthcare, insurance, and housing. The law around AI liability is still taking shape. Some businesses learn the rules before a claim hits. They stand in a far better spot than those who learn after.
The deployer bears primary exposure
One rule guides product liability law. It places blame on the party that sells a product and profits from it. For AI, that party is usually the "deployer." The deployer is the business that uses the AI to judge customers, staff, or applicants. The model vendor only supplies a tool. That could be OpenAI, Google, or a specialized AI firm. The deployer sets it up. It trains the tool on its own data. It builds the workflow. It controls how the results get used. Courts and regulators now tend to hold the deployer to account.
This shapes how you buy. Say a business licenses an AI system. Then it uses that system to make choices that affect other people. The vendor's terms will almost always disclaim blame for how you use the output. So read those terms with care. You are buying a tool. You are not buying protection from liability.
Three liability pathways every business deploying AI should understand
Discrimination and disparate impact
An AI system can hurt a protected class more than others. This can happen with no intent to discriminate. Even then, the deployer may face liability under anti-discrimination law. Lawyers call this the "disparate impact" theory. It can apply when the bias is on purpose. It can also apply when the training data causes it by accident. Responsible AI for fintech and lending and responsible AI for hiring cover the specific legal frameworks in those industries. The main point is simple. "The algorithm did it" is not a defense.
Negligence in high-stakes decisions
Some sectors carry extra weight, like healthcare and finance. A business there may use AI to guide or make big decisions. If so, it owes a duty of care to the people those decisions affect. A negligence claim can follow in a few cases. It can follow if the AI was poorly tested. It can follow if known flaws went unfixed. It can also follow if the system ran outside its tested scope. The test asks one thing. Did the deployer act as a careful, prudent operator would? More and more, that means running bias audits before launch. It means keeping human review on high-stakes calls. And it means writing down why each choice was made.
Consumer protection and unfair practices
Regulators have sent a clear signal. The FTC is one of them. A business may use AI to make choices about consumers. That can cross a line in a few ways. It can lack clear disclosure. It can offer no way to appeal. Or it can prey on weak spots. Any of these may count as an unfair or deceptive practice. The disclosure obligations for businesses using AI are growing. And enforcement actions are no longer just a theory.
Contracts don't protect you as much as you think
Many businesses lean on a strong vendor contract. It may hold indemnity clauses, liability caps, and warranty disclaimers. They assume it shifts all AI risk to the vendor. That is true for a few narrow types of failure. It is mostly false for the types that matter most. Harmed people bring third-party claims. Those claims do not follow your B2B contract. A user hurt by your AI choice can sue you straight away. Your deal with the vendor will not decide that case.
The businesses that cut AI liability are not the ones with the best contracts. They are the ones with the best governance. That means documented choices and tested systems. It also means real oversight and open processes.
What defensible AI deployment looks like
A legal standard is taking shape across many places. It rewards businesses that can show clear proof. They weighed the risk before launch. They tested the system against the people it would affect. They built human review into big decision types. They told affected people about the AI's role. And they gave people a way to contest automated choices. These are exactly the questions responsible business leaders ask before deploying AI.
At Through The Glass Creatives, the team builds AI with this liability landscape in mind. That focus shapes every project. TTGC does more than build capable AI systems. The studio documents the reasoning behind each one. It keeps pre-launch testing records. It builds governance frameworks a client's legal team can stand behind. That helps if a deployment choice is ever challenged. This is not a nice-to-have. For AI in high-stakes work, it can mark the line between defensible and exposed.
Deploying AI in a high-stakes context? Talk to TTGC about building accountability and legal defensibility into your system from the start.
Book a free Brand and Growth Assessment and see exactly how Through The Glass Creatives would approach it.
Sources
- U.S. Equal Employment Opportunity Commission - "The Americans with Disabilities Act and the Use of Software, Algorithms, and Artificial Intelligence to Assess Job Applicants and Employees" (2022).
- U.S. Federal Trade Commission - "Aiming for Truth, Fairness, and Equity in Your Company's Use of AI" (2021).
- European Parliament - "EU AI Act: Liability Framework for AI Systems" (2024).
- Brookings Institution - "Algorithmic Discrimination and the Law" (2022). Analysis of disparate impact doctrine applied to AI systems.
- Stanford Law Review - "Who Is Responsible When AI Harms People?" (2023). Legal scholarship on AI product liability frameworks.









