---
title: "Prompt: ten operational AI risks to check before you scale"
slug: checklist-riesgos-ia-operacion
lang: en
updated: 2026-10-19
---

# Prompt: ten operational AI risks to check before you scale

How to use it: copy the block, paste it into ChatGPT, Claude or Gemini and replace the fields in brackets. It works best if you also paste the pilot description, vendor terms or your AI policy. Do not paste confidential data unless your company has approved it.

```text
Act as an operational risk manager with 15 years of experience who reviews tool expansions before they reach a committee and accepts only documents or figures as evidence.

Context I am giving you:
- Company / area: [ ]
- AI tool and what it is used for today: [ ]
- Pilot result (who, how long, what was measured): [ ]
- Scale it is meant to reach (people, volume, clients): [ ]
- Which data goes into the tool: [ ]
- What I know about the vendor's contract and pricing model: [ ]

What I need: produce the one-page checklist with exactly these ten items, grouped as follows:
1. Data and confidentiality: (1) which data goes in and whether it leaves the company; (2) whether the vendor uses or stores the data.
2. Quality and errors: (3) who reviews what goes out to the client; (4) error rate and the threshold that stops usage.
3. Vendor dependency and variable cost: (5) cost at twice the volume; (6) ability to switch tools.
4. People and authority: (7) who may use it and what they may approve; (8) whether the people affected know what changes.
5. Continuity: (9) what happens if the tool fails for a full day.
6. Compliance: (10) legal or compliance review at the new scale. Label this group "check with your legal team; this is not legal advice".

For each item: a `- [ ]` box, status based on what I gave you (met / not met / no evidence), "what good looks like" and the next action with an owner.

Output format: the grouped list and, at the end, one line saying whether the expansion can go ahead or should wait. Maximum 450 words. No introduction.

Rules:
- Do not invent figures or contract clauses. If data is missing, write [DATA PENDING] and tell me how to get it.
- If there is no evidence for an item, mark it "no evidence", never "met".
- Do not give a legal opinion; say what to ask the legal team.
- If critical information is missing, ask me at most 3 questions before answering.
- Answer in plain, direct business English, with no sales adjectives.
```

What to check in the answer:

- Did it mark "no evidence" where you gave no document or figure, or did it treat items as met by assumption?
- Does the continuity item propose a concrete manual fallback?
- Did the compliance group stay as a question for your legal team, with no legal opinion?