Level 100: How AI works: AI at work and in life · Module 100.R

Three coworkers gather around notebooks at a wooden café table.
Bring your work.

AI in your job (role tracks) · Standard gear

Reviewed and published, version 1.0.0. As of 16 November 2026. Big Widget Company and its people are made up. Every real organization and case below is real and cited. Where the course's source checker has not yet opened a source, this gear says "not checked". The role tracks, the three yeses, the four gate answers and the get-to-yes questions are this course's own practice, not a law or a standard.

What this module does

Air Canada’s chatbot gave fare advice that contradicted the policy; a customer relied on it, and the tribunal held the company responsible.
In the Air Canada case, the chatbot’s advice conflicted with the written policy; a customer relied on it, and the tribunal held the company responsible for what its chatbot said (s3).
Figure data as text

Where it landed

  1. The Air Canada chatbot gives fare advice that contradicts the written policy. [s3]
  2. A customer relies on the chatbot’s advice. [s3]
  3. The tribunal holds the company responsible for what its chatbot said. [s3]

Objective: 100.R-b. Text equivalent of figures/where-it-landed.svg.

Modules 100.1 to 100.9 taught what generative AI is, why it works, where it breaks, and the three yeses:

This module puts those ideas into your own job.

Big Widget Company has seventeen tracks: one for home and everyday life, fifteen for its teams, and one for leaders. You take the track for your own team, or the home track if you use AI only at home. Then you take one other team's track, because AI mistakes often land in someone else's department.

By the end you will be able to:

Two beliefs this module corrects:

One good use, one bad use, one question

Every track has the same three parts.

PartWhat it isExample (Big Widget Company, made up)
Good useAI doing a job it is good at, with safe information, checked by a named person who owns the resultSam in customer service gets a suggested reply and decides what to send
Bad useThe same tool on a job it is bad at, or with secrets it should not see, or with nobody checking, or used to fool peopleA chatbot answers customers alone and makes up a policy
Get-to-yes questionThe one question, asked before you start, that targets the check this job is most likely to fail"Can it only quote our written policy, and can every customer reach a person?"

The get-to-yes question is a focused check, not a permission slip. A yes to it is necessary but not sufficient. The use is on the good side only when all four checks from 100.9 pass:

  1. the task fits the tool;
  2. the data is allowed;
  3. a named person owns the result;
  4. a written rule allows the action.

People answer these checks. The AI does not approve its own use.

A gate gives one of four answers: go ahead (allow), only this far (constrain), wait for a person (hold) or no (deny). A no, or "we don't know yet", on any check means hold. The use waits until a named person fixes the gap or decides. Write down who that person is: "a human in the loop" is not enough if nobody knows who can release the hold. A hold is not a quiet yes. If nobody decides, the answer is no.

The rows below often differ in more than one way. The question names the difference that matters most for that team, not the only one.

The good use and the bad use are often the same tool. What separates them is a choice people make before the AI acts. That is why the question belongs to your team and not only to IT: you know which facts are secret in your job, what a wrong answer would cost, and who should check.

Getting to yes once is not the end. Staying at yes means asking the question again when the tool, the data or the people change.

Six documented cases behind the tracks

Each case below is real and documented by a court or tribunal, a regulator, a company's own filing or release, or a research paper. They are not all the same kind of evidence:

Case 2's source was checked 18 Nov 2026.

For each one: what happened, the good or bad use, the question that separates them, and where the mistake landed or could land.

1. Customer service: an AI helper that made new agents better (a good use)

Researchers used data on 5,179 customer-support agents at one company while a generative AI assistant was introduced in stages, comparing work with and without access to it.5 With access, agents resolved 14% more issues per hour on average.5 The gain was 34% for novice and low-skilled workers, with minimal impact on experienced and highly skilled workers.5 The researchers report suggestive evidence that the assistant spread the best practices of more able workers and helped newer workers move down the experience curve, that is, get better faster.5

2. Customer service, sales and legal: the company answers for its chatbot (a bad use)

Source checked 18 Nov 2026.

In November 2022, after their grandmother died, Mr. Moffatt used the chatbot on Air Canada's website to ask about bereavement fares.1 The chatbot told them they could apply for the reduced fare after travelling, within 90 days of the date their ticket was issued.1 The airline's own bereavement-travel page, which the chatbot's answer linked to, said the policy did not apply to travel that had already happened.1

Air Canada argued that it could not be held liable for what its chatbot said.1 In a decision dated 14 February 2024, British Columbia's Civil Resolution Tribunal held that the chatbot is part of Air Canada's website and that Air Canada is responsible for all the information on its website, including what its chatbot says.1 It found negligent misrepresentation and ordered Air Canada to pay Mr. Moffatt C$650.88 in damages, plus interest and tribunal fees.1

The lesson travels to any team that lets AI speak for the company: sales and dealers quoting prices and terms, customer service, and legal, who will have to defend the answer. A chat window is not a limit on what the AI may say. The limit has to be a rule a person set and owns.

3. Manufacturing and engineering: a vendor's claims for an AI engineering assistant

On 24 October 2024, Siemens said that over 100 companies, including Schaeffler and thyssenkrupp Automation Engineering, were using its Siemens Industrial Copilot, a generative AI assistant used with its TIA Portal engineering software.4 Siemens said the assistant can "generate code that requires only 20% adaptation", and that its chat function gives answers that remove the need for lengthy searches.4

The press release does not say how the code is checked or who approves it.4 That is exactly the part your team has to decide.

4. HR: hiring software that turned older people away

In 2023, iTutorGroup agreed to pay $365,000 to settle a lawsuit brought by the US Equal Employment Opportunity Commission (EEOC).2 According to the EEOC's lawsuit, iTutorGroup programmed its tutor application software to automatically reject female applicants aged 55 or older and male applicants aged 60 or older.2 The EEOC said more than 200 qualified applicants in the United States were rejected because of their age, and the $365,000 is to be distributed to applicants who were automatically rejected because of their age.2

The EEOC describes software that was programmed to reject applicants by age.2 Its release does not mention AI and does not describe how the software was built, so this case gives no evidence that generative AI caused the rejections. It belongs in this module because the question is the same for any software that makes decisions about people.

5. Marketing: fake or misleading customer reviews

The US Federal Trade Commission (FTC) published a rule on consumer reviews and testimonials on 22 August 2024, effective 21 October 2024.6 It says it is an unfair or deceptive practice for a business to write, create or sell a consumer review or testimonial that materially misrepresents any one or more of: that the reviewer exists; that the reviewer used or otherwise had experience with the product, service or business; or what that experience was.6

The FTC says AI-generated reviews are covered by the rule.6 The rule turns on whether the review misrepresents, not on who or what wrote it. A "customer" review about a customer who does not exist, or an experience that never happened, is covered whether a person or an AI wrote it. A real customer's accurate review is not made unlawful by AI help with the wording alone, though other rules may still apply. This is the course's reading of the rule, not legal advice. Rules change, so check what is in force today with your legal team.

6. Safety and quality: automation that let people stop watching

Tesla's recall report describes Autosteer, part of Autopilot, as a feature that can provide steering, braking and acceleration support to the driver under certain limited conditions.3 That is driver assistance, not generative AI. It is here for one lesson: what happens when people trust automation and stop paying attention.

The same report to the US National Highway Traffic Safety Administration (NHTSA) says the driver remains responsible for the vehicle, "with their hands on the steering wheel at all times".3 It says the prominence and scope of the feature's controls "may not be sufficient to prevent driver misuse", and that this could raise the risk of a collision.3 On 5 December 2023, while not agreeing with the agency's analysis, Tesla decided to voluntarily recall 2,031,220 vehicles.3 The report says the affected vehicles would receive an over-the-air software update, at no cost to customers, with additional controls and alerts to further encourage drivers to keep their hands on the wheel and pay attention.3

In this course's terms this is a Stay at Yes problem: a system that needs people to keep watching has to keep checking that they do. The report describes a planned fix.3 It does not show that the fix worked, so this module does not call it a completed recovery.

The seventeen tracks

Each row is one track. The good and bad uses are made-up Big Widget Company examples, written as course guidance. Where a real case sits behind a row, the row cites it or names the module that teaches it. Rows without a cited case in this module rest on the earlier modules named in the last column.

TrackGood useBad useGet-to-yes questionCase or module
Home and everyday lifePlan a trip or compare offers, then check the facts with the companyTrusting a chatbot's word on a refund or fare without checking the written policyDid I check this against the company's own written rules?Air Canada1
ManufacturingExplain a machine fault from the manuals; draft machine code an engineer reviewsAn unchecked fix goes onto a live lineHas a qualified person checked it before it touches a machine?Siemens' claims4; 100.6
QualitySummarize thousands of warranty comments to surface candidate patterns, while serious reports still reach a person by the normal routeTreating the summary as complete; a rare, serious defect it left out is never seenWhat did the AI leave out, and how do rare, serious reports still reach a person?100.4 (jagged frontier)
Engineering and designFirst drafts of code and test plansShipping code nobody reviewed or testedWho reviews it, and how do we measure the time saved?Siemens' claims4; 100.4, 100.5
Supply chain and procurementAn agent negotiates small contracts inside firm limitsSupplier prices pasted into a public chatbotWhat may it offer, and what data may it see?100.6 (agents), 100.7 (secrets)
Forecasting and planningForecasts for products with years of history, with an honest rangeOne confident number for a brand-new widget with no historyWhat did it learn from, and how sure is it?100.2 (training data)
Sales and dealersAnswers from approved price lists and specsA chatbot promises a price or term the company never offeredCan it only quote approved terms?Air Canada1
Customer serviceA helper suggests answers; the agent decidesA bot invents a policy, and there is no way to reach a personCan every customer reach a person?Support agents study5; Air Canada1
MarketingCampaign ideas that people shape and approveFabricated or misrepresented "customer" reviews, whoever or whatever wrote themIs every review and quote real, accurate, and used with the customer's permission?FTC review rule6; 100.8
Brand and communicationsFirst drafts, fact-checked before anything goes publicA wrong fact or a tone-deaf AI message in publicWho checks facts and tone before it goes out?100.1, 100.3 (confident and wrong); 100.8
LegalSummarize contracts and find clauses; a lawyer checksFilings with citations nobody openedHas a lawyer read every source cited?Air Canada1; 100.8
ITHelp writing and fixing code; agents in a safe test area with backupsAn agent that can delete live dataWhat can it change, and can we undo it?100.6 (agents)
CybersecuritySort alerts and spot phishing fasterAn assistant that obeys instructions hidden in outside emailWhat outside content can it read, and what can it do after reading it?100.7 (hidden instructions, deepfakes)
SafetyFind patterns in near-miss reportsPeople trust automation and stop watchingHow does the system keep people paying attention?Tesla recall3; 100.9
HRDraft job posts; answer policy questions with links to the policyAutomated screening that treats people unfairlyHas it been tested for fairness, and can a person review every rejection?iTutorGroup2; 100.7
FinanceExplain variances and draft close notes, with every number tracedPaying on a request that looks and sounds realIs every number traced, and does every unusual payment get a call-back?100.7 (deepfakes), 100.8
LeadersStart with clear jobs, measure results, scale what worksPilots with no measure of successHow will we know it worked, and who owns it?Support agents study5; Air Canada1; 100.4

Two course rules run through every row. First, the AI never approves its own use: a named person does. Second, anything the AI cannot undo, such as a payment, a public post or a change to live data, stops and waits for a person.

For leaders, the two cited cases make two points. Gains from the same AI helper differed sharply by who used it, so measure rather than assume.5 And the organization answers for what its AI tells people, so every AI use needs a named owner.1

How someone else's AI mistake lands on you

The cases above show four routes by which an AI or automation mistake made somewhere else can reach a person who had no part in it. Three rows are documented incidents; the shopper row is a possible harm described by a rule, not a recorded episode.

RouteYou are...CaseWhat it cost, or could cost
Through a company you deal withA customerAir Canada's chatbot gave a grieving customer a wrong answer1Mr. Moffatt had to take the airline to a tribunal to be paid1
Through a decision about youAn applicant or employeeThe EEOC said iTutorGroup's software rejected older applicants automatically2More than 200 qualified people were turned away because of their age2
Through what you readA shopperThe FTC rule bans reviews that misrepresent whether the reviewer exists, whether they had experience with the product, service or business, or what that experience was6Possible harm: you could choose on the strength of an experience that never happened
Through a product you useAn owner or userTesla's driver-attention controls might not prevent misuse32,031,220 vehicles were included in the recall3

Inside Big Widget Company the same routes run between teams. Some made-up examples:

This is why each learner takes a second team's track. The question to ask about another team's AI is the same as for your own: if this goes wrong, where does it land, and who would I tell?

Some uses really are sealed off from you. If you look and find no route, say so and say why, rather than inventing one. "I don't know yet" is also an honest answer, as long as you name who you will ask.

Your track exercise

Every track ends with the same short exercise. Bring it to the capstone (100.P).

  1. Pick one row from your own track, or write a new row for your team or household.
  2. Write its good use, its bad use and its get-to-yes question in your own words.
  3. Write it as a rule with the 100.9 template: This AI may [do what] for [whom] only when [condition]. Otherwise it [falls back to what: only this far, wait for a person, or no]. [Named person] owns it. We keep [this receipt].
  4. One documented route (everyone does this). Pick one of the four routes in the table above. Take the role it names: customer, applicant, shopper or owner. Explain how the mistake travelled: whose AI or automation made it, what output carried it, who it reached, and who should be told. You are explaining how it could land on someone in that role. Do not claim it happened to you.
  5. One other team. Read one other team's track. Name one way an AI mistake there could land on you, and who you would tell. If you look and find no route, say so and say why. Do not invent one.

What the receipt holds. A receipt records the decision, not the content: what was asked to run, the gate's answer, who owns it, and when. It never holds prompts, AI answers, customer details or other personal data. If your workplace allows you to keep notes on the prompt, the answer and your check, keep them in a separate work record that your workplace controls. Do not paste them into anything you share.

At 100.P, a person reviews your rule. An AI does not.

What this module does not claim

Words to know

Sources

  1. s3 Christopher C. Rivers, British Columbia Civil Resolution Tribunal (2024). Moffatt v. Air Canada, 2024 BCCRT 149. Record. Checked 2026-11-18 by source-checker agent (Devin session 0b04bfd2, separate from the writer, red team and item writer), round 4, 18 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  2. s2 U.S. Equal Employment Opportunity Commission (2023). iTutorGroup to Pay $365,000 to Settle EEOC Discriminatory Hiring Suit. Record. Checked 2026-11-17 by source-checker agent (Claude, separate session from the writer), round 3 re-check 17 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  3. s4 Tesla, Inc. (submitted to the National Highway Traffic Safety Administration) (2023). Part 573 Safety Recall Report 23V-838. Record. Checked 2026-11-17 by source-checker agent (Claude, separate session from the writer), round 3 re-check 17 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  4. s1 Siemens AG (2024). Siemens and Microsoft scale industrial AI. Official doc. Checked 2026-11-17 by source-checker agent (Claude, separate session from the writer), round 3 re-check 17 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  5. s6 Erik Brynjolfsson, Danielle Li, and Lindsey R. Raymond (2023). Generative AI at Work (NBER Working Paper 31161). Paper. Checked 2026-11-17 by source-checker agent (Claude, separate session from the writer), round 3 re-check 17 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩
  6. s5 Federal Trade Commission (2024). Trade Regulation Rule on the Use of Consumer Reviews and Testimonials. Standard. Checked 2026-11-17 by source-checker agent (Claude, separate session from the writer), round 3 re-check 17 Nov 2026. ↩ ↩ ↩ ↩ ↩ ↩ ↩ ↩

Next: the quiz