Eleven questions that will make you seem wise, or save your company
The most available opportunity in this book is a set of questions that almost nobody in your organisation can currently ask, about a rule that's already in force.
On 2 August 2026, a set of obligations in European law began applying to AI systems used to make decisions about people. Hiring. Credit. Education. Access to essential services.
They apply to organisations using those systems, not only to the companies that built them.
I would like you to go and ask three people in your business whether that affects you. My prediction is that all three will say it's somebody else's department, and that not one of them will be able to name the department.
That gap is the subject of this chapter. Not because you're going to become a lawyer. Because the questions that matter here aren't legal questions. They are management questions with legal consequences, and the people who can ask them are almost nowhere.
I am not a lawyer, none of this is advice about your situation, and every question below exists to send you to somebody who can answer it properly rather than to replace them. That isn't a disclaimer bolted on the front. It is the actual claim of the chapter. The value is in asking, not in knowing.
For most of the last decade, the assumption was that AI regulation would land on the technology companies. They build it, they're enormous, they can afford it, and they're where the headlines point.
That assumption is now wrong, and being wrong about it is expensive.
The law has moved towards the deployer. The organisation that takes a system somebody else built and points it at a real decision about a real person; that is your employer. It is possibly your team. In one European framework the obligations on a deployer sit in their own article, separate from the builder's, and they include running an impact assessment on people's fundamental rights before you switch it on.
Nobody is going to send your company a letter about this.
Read that clause again slowly. Your organisation can buy a tool, use it exactly as instructed, and be the party carrying the obligation. The vendor's compliance isn't your compliance. It never was, and now it's written down.
I am going to give you the shape rather than the detail, because the detail changes and the shape doesn't.
Europe built a single law and phased it in. Prohibited uses and a staff-competence duty first. Then general-purpose models. Then the high-risk categories, which is where most ordinary businesses actually live. Penalties at the top run to thirty-five million euro or seven per cent of worldwide annual turnover, whichever is greater.
Seven per cent of turnover. Not profit. Turnover.
The United States built no single law and is producing dozens. The National Conference of State Legislatures, which counts these, records that in the 2025 session thirty-eight states adopted around a hundred AI measures out of roughly twelve hundred bills introduced. By March of 2026, on the same count, forty-five states had introduced 1,561 AI bills. Already past the total for all of 2024, before the year was half done.
They don't agree with each other. One state gives you an affirmative defence if you've adopted a recognised risk framework. Another gives individuals a private right of action, which means you aren't waiting for a regulator, you're waiting for a plaintiff.
Australia looked at a dedicated AI Act and decided against it. In December 2025 the government formally abandoned mandatory AI guardrails in favour of a technology-neutral approach: clarify the existing law, add guidance, fund a safety institute.
Everyone read that as the light-touch option. It is the opposite. A dedicated AI Act gives you a checklist. Technology-neutral means every existing law applies to your AI the same way it applies to everything else. Consumer protection, misleading conduct, discrimination, privacy, directors' duties. And there's no single document to read.
The United Kingdom has no AI Act either, and works through five principles applied by existing regulators within their own remits. No single AI regulator to call.
There was a proposed European directive dealing specifically with AI liability. It was withdrawn in early 2025.
That sounds like good news. It is not.
What happened instead is that the general product liability regime was revised to bring software, AI systems and digital services inside the definition of a product. Which means strict liability, disclosure obligations, and; this is the part to hold on to. Rebuttable presumptions of defectiveness and causation for complex AI products.
In plain English: for a system nobody can fully explain, the law has started shifting the burden of proof towards the people who deployed it.
The specialist law that would have been complicated to comply with was dropped. The general law that's much harder to argue with swallowed AI instead.
Here is a prediction. I'm marking it as mine so you can hold me to it.
There's a job that is going to exist in a few years and doesn't have a name yet. When a business uses AI, is that business legally responsible for what its AI does under its own name, or is nobody responsible? Today the honest answer is that it depends who you ask, which is another way of saying it hasn't been decided.
We have solved this before, in industries where the consequences arrived earlier than they did here.
In financial services, a named individual carries personal accountability for the way a firm conducts itself. On licensed premises, a named person is responsible for what happens inside the building. Not the company in the abstract. A person, named on a document, who can be asked.
I think that arrives for AI, and sooner than the people running businesses expect. Somebody in each company becomes the nominated person for whether AI is being used responsibly inside it, and they will have signed something saying so.
Companies will hate it at first. They should want it anyway, because the alternative is exactly where we are standing now, where the exposure is real and nobody has been told it is theirs. Most of the mistakes and the failures and the public embarrassments between here and there will happen for that one reason.
Which points at a better question, and it's one you can ask this week rather than in three years.
If that role existed in your organisation tomorrow, whose name would be on it?
Ask it and watch what happens. Most people go quiet. Then they say a name. Then they say, “but I don't think they know.”
You aren't going to read any of that. Nor should you.
Here is what transfers, in three lines.
The law is not converging and waiting for clarity is not a strategy. There is no moment coming where this settles and somebody circulates the summary. The organisations that do well will be the ones that built a defensible way of working before anybody made them.
Contract is the main tool, precisely because the substantive law is unsettled. When nobody is certain who is liable, the allocation that matters is the one you wrote down with your supplier. Warranties, indemnities, what happens on a breach, who carries what. That isn't legal exotica. That is a procurement conversation, and procurement conversations are had by ordinary managers every week.
Adopting a recognised framework is not box-ticking. In at least one jurisdiction it is literally a defence. There is an American state statute under which adopting a specific national risk-management framework functions as an affirmative defence. The framework is voluntary. Using it's a legal shield. Almost nobody in a non-technical role knows that sentence exists, and it is the single most useful thing you can say in a governance meeting.
None of these is a legal question. Every one can be asked by somebody with no legal training, and asking three of them in the right meeting will change how you're seen for a year.
1. Are we the builder or the user of this, and do we know which obligations follow from that? The answer is almost always user, and almost nobody has checked what that means. It is the question the rest depend on.
2. Does anything we use touch a decision about a person? Hiring, promotion, pay, credit, insurance, housing, education, access to a service, or who gets contacted and who doesn't. That is the boundary that turns ordinary software into the regulated category, in every regime, everywhere. If the answer is yes anywhere in your business, everything else on this list becomes urgent.
3. Whose law reaches us? Not where your office is. Where your customers, your staff and your data are. A company in one country with users in another is subject to the second one's rules, and the map of your obligations looks nothing like the map of your buildings.
4. Can we show a human was involved, and that they could actually have changed the outcome? Human oversight is not a person on an org chart. If the human sees the output after it has gone, or has no realistic ability to override it, the oversight is decorative and will be read as decorative.
5. Do we tell people? When someone is dealing with an AI rather than a person, when content was machine-generated, when a decision about them was substantially automated. Transparency duties are the most common feature across every regime I've looked at, and the cheapest to comply with, and the most commonly missed.
6. Have we adopted a recognised framework, and can we evidence it? Not do we have a policy. Can we show the assessments, the decisions and the dates. A framework you adopted and never evidenced is worth nothing when it matters, which is the exact moment it was for.
7. What do our contracts say about who carries this? With every vendor whose system touches a decision. If nobody can answer, the answer is you.
8. If we had to produce the record, could we? Which system, which version, which question, which output, who reviewed it, when. Not because a regulator will definitely ask. Because you can't defend a decision you can't reconstruct, and reconstruction is not something you can retrofit after the letter arrives.
9. Who signed this off, and do they know they did? In most organisations, a tool arrived, somebody sensible started using it, it spread, and no one ever made a decision. There is a name at the top of an accountability chain and quite often that person has never been told.
10. What is our plan for the day this changes? Not if. The volume of legislation above means something relevant to you will change inside twelve months. Is there a person whose job includes noticing, or is your plan to read about it in the press?
11. If this went wrong publicly tomorrow, what would the first line of the news story be?
That last one is the one to ask out loud.
It is not a legal question at all and it does more work than the other ten combined, because everyone in the room can answer it instantly and nobody can pretend they can't. Company uses AI to reject applicants and can't explain how. Firm's chatbot gives wrong advice for six months. Staff pasted client records into a public tool.
If the sentence comes easily, you've found the thing to fix. And you found it in a meeting, using no expertise, at a cost of about four seconds.
I have given you eleven questions and no picture of what happens when one gets asked, so here is question two doing its work. Does anything we use touch a decision about a person?
My prediction is that the first answer you get will be no. It will come back quickly and confidently, from somebody senior enough that everybody else in the room relaxes — no AI in HR, no algorithmic hiring, nothing anywhere that decides anything about anybody.
Then somebody near the end of the table says: what about the sift?
The company had been getting more applications than it could read. So a manager · not IT, not HR, a manager with a problem and a deadline · had started pasting batches of CVs into a general-purpose tool with an instruction that amounted to which five of these best match this job description. She then read those five properly. She was doing it in good faith, she was doing it on top of her actual job, and she had told her own director, who thought it sounded sensible and efficient, because it is.
Now walk it through the list.
Question two. It touches a decision about a person. Hiring is named explicitly in every regime anybody has written.
Question one. They are the deployer, not the builder. The obligations that follow are theirs, and the tool's terms of service protect the tool's maker.
Question four. Can they show a human was involved and could have changed the outcome? A human read the five. Nobody read the other sixty, and the five were chosen by something nobody in the building could explain. The oversight is real and it sits entirely on the wrong side of the filter.
Question eight. Could they reconstruct it? Which version answered, what the instruction said that week, which sixty were rejected and why. No. It happened in a chat window on one person's account.
Question nine. Who signed this off? Nobody. A manager solved a problem she had been left with, and every person above her who heard about it thought it sounded efficient.
Five of the eleven, and not one of them needed a lawyer to ask. The whole thing surfaced in under four minutes, in a meeting that had opened with a confident no.
And now the part I care about more than the finding. Nobody in that story did anything wrong in the ordinary sense. I do not think there is a villain in it, and I have never found one in any version of it I have come across. There is a person who was handed more applications than a person can read, was handed nothing else, and reached for the tool her whole industry reached for that year.
That is what this exposure looks like from the inside, and it is why I keep saying the question has to be asked out loud by somebody. It will never announce itself. It looks like somebody coping.
Be direct about the mechanics, because that's what this book is for.
Senior people are genuinely uneasy about this and almost nobody brings it to them in a form they can act on. What reaches them is either a vendor selling reassurance or a technical briefing about how the model works, and neither answers the question they are actually holding, which is what happens to us if this goes wrong.
Walk in with question two and question eleven. Does anything we use touch a decision about a person? And if it went wrong publicly tomorrow, what is the first line of the story?
You have claimed no expertise. You do not need any. You have asked the two questions the room has been circling for a year, and you'll be in the next conversation about it, which is a room you were not previously in.
There is a version of this that goes wrong, and I want to name it so you avoid it. Do not walk in as the person who has found a problem. Walk in as the person who has found the question, and let them own the answer. The first is a threat. The second is help.
Take question two. Does anything we use touch a decision about a person?
Ask it about your own team first, quietly, before you ask it in a meeting. Hiring, or who gets contacted, or who gets flagged, or how work is allocated. You may find nothing. You may find something that has been running for eight months.
Then, whichever it's, you know something about your own organisation that almost nobody else in it knows.
Which is a useful position to be in, and a completely useless one, until somebody other than you can see it.