Shared · Opening01 / 07

Why this training exists

AI Use-Case Assessor — Workforce Training · Submitter track

01
“Have you trained and informed the employees using AI?” is becoming an audit question.
02
This training and the assessor are how the organization answers yes.
03
Governance names the controls. This is where they reach the people who build and buy AI.

REF AI-ASS-SHARED-01SHARED · CONFIDENTIAL — INTERNAL

SHARED 1 · Narration

Every AI governance program eventually meets one question in an audit: can you show your people know what to do. Policy on a shelf does not answer it. This short training does. By the end you will know what counts as an AI use case, why we need to know about it, and how to run it through our assessor before it goes live.

Shared · Definition02 / 07

What is an AI use case?

01
Any system that uses AI or automated decision-making to predict, score, classify, generate, recommend, or decide.
02
If you are building, buying, or turning on a tool that does any of these, it is an AI use case — even if a vendor runs it.
03
Examples: scoring job applicants, a customer chatbot, flagging transactions, drafting documents.

REF AI-ASS-SHARED-02SHARED · CONFIDENTIAL — INTERNAL

SHARED 2 · Narration

The skill that matters most is recognizing one, and you do not need to be technical to have it. If a tool predicts, scores, classifies, generates, recommends, or decides, especially if it touches people, it is an AI use case we need to know about. Bought from a vendor still counts. When in doubt, submit it.

Shared · The tool03 / 07

What the assessor gives you

01
A preliminary risk tier, with the reasoning.
02
An explicit list of what your description did not say: the gaps.
03
The governance frameworks and obligations that likely apply.
04
It is advisory. A human reviewer confirms the outcome.

REF AI-ASS-SHARED-03SHARED · CONFIDENTIAL — INTERNAL

SHARED 3 · Narration

The assessor is not a gatekeeper to fear. You describe your use case and it returns a preliminary tier and why, the frameworks that likely apply, and, importantly, a plain list of what it could not tell from your description. That gap list is a to-do, not a failure. It tells you what to go find out.

Submitter track · Practice04 / 07

How to submit

01
Go to https://www.mercedesedwards.com/assess.
02
Describe your use case in plain language, or fill the short form.
03
Answer honestly. “Not sure” is a valid, useful answer. Do not guess.
04
Describe the system, not the data. No confidential, personal, or client-identifying details.
05
Click Assess.

REF AI-ASS-SUB-04SUBMITTER TRACK · CONFIDENTIAL — INTERNAL

SUBMITTER 4 · Narration

Submitting takes a few minutes. Open the assessor and either type a plain description or fill the short form. Answer honestly, and if you do not know something, say “not sure”. The tool is built to flag unknowns, so an honest “I don't know” is more useful than a guess. Keep it about the system, not sensitive data.

Submitter track · Outcome05 / 07

Reading your result

01
The tier tells you how much scrutiny it needs, not whether you can proceed.
02
The reasoning shows why.
03
The gaps are your next steps: the questions to answer before review.
04
A reviewer will follow up. Have the gap answers ready.

REF AI-ASS-SUB-05SUBMITTER TRACK · CONFIDENTIAL — INTERNAL

SUBMITTER 5 · Narration

Your result opens with a tier and a short reason. A higher tier does not mean stop; it means a reviewer looks more closely. The most useful part is the gap list: those are the questions to answer before your review. Bring those answers and the review goes faster.

Shared · Accountability06 / 07

Your responsibility

01
Submit before you build, buy, or turn it on — not after.
02
Keep it honest. Flag what you do not know.
03
Re-assess when the use case materially changes.
04
The assessment starts the record; it does not end your accountability.

REF AI-ASS-SHARED-06SHARED · CONFIDENTIAL — INTERNAL

SHARED 6 · Narration

Two rules. Submit early, before the thing is live, when governance can still shape it. And keep it honest, because the tool and the reviewer both rely on what you tell them. If the use case changes materially later, run it again.

Shared · Close07 / 07

Why this matters

01
Using the assessor and completing this training is how the organization shows its AI is governed — to a regulator, an auditor, or a customer.
02
Trained employees plus a record of every use case equals a defensible program.
03
Governance named the controls. You are how they operate.

REF AI-ASS-SHARED-07SHARED · CONFIDENTIAL — INTERNAL

SHARED 7 · Narration

When an auditor asks whether our people are trained and whether we know what AI we run, this training and this tool are the answer. You completing it, and submitting your use cases, is what turns our governance from a document into something we can stand behind. That is the whole point.