For Fraud Examiner / Financial Investigators ·
What you'll accomplish
Red-flag training gets rebuilt every quarter: new scenarios, new discussion questions, a fresh quiz, because last quarter's answers are already circulating. You will set up one ChatGPT Project per training program, give it your own red-flag outline and a firm rule to use invented schemes only, and then ask for new scenarios, discussion questions and a 10-question quiz with an answer key whenever a session comes up. Your outline stays in one place, each session gets new examples, and you review every item against your unit's guidance before anyone sees it.
What you'll need
Data note. This workflow needs no case material, so keep it that way. The outline should describe red flags in general terms, the instructions should require invented schemes and invented companies, and nothing from a real case, real person or real institution should go into the project. If an example from a real matter comes to mind, leave it out. Also check your account's data controls to see whether chats and uploaded files are kept and whether they may be used for model training, since the outline may be your unit's own work product.
What you should see: a one- to three-page outline that reads like teaching notes. Troubleshooting: If your unit already has a training deck, copy the red-flag slides into a plain document. Text files are easier for the project to use than slide layouts.
OpenAI's help page says projects group chats and hold uploaded reference files and custom instructions.
What you should see: a project page with your file listed and a place for instructions. Troubleshooting: Menus and plan features change. If you cannot find projects in your account, check OpenAI's current help pages for your plan. Do not move case material into a workaround.
Look for the project's instructions area and paste the text below.
You help a fraud examiner build training material for staff.
Rules:
1. Use the attached outline as the source of red flags. Do not add red flags that are not in the outline.
2. All scenarios must be invented. Use invented companies ("Company X"), coded people ("Employee A", "Vendor V-12") and no real case, person, institution or product. Do not describe anything that looks like a real matter.
3. Leave out currency symbols. Write amounts as plain numbers or placeholders.
4. Never state or imply that a coded person committed fraud or intended anything. Describe what the records show and what a trainee should notice.
5. Produce what is asked and no more: scenarios, discussion questions, a quiz, an answer key.
6. For every quiz question, tie the answer to a specific item in the outline. Mark any question you cannot tie to the outline with [NOT IN OUTLINE].
7. Do not state what any law or regulation requires. If a question touches that, mark it [REFER TO COUNSEL OR COMPLIANCE].
8. All output is a draft for the examiner to review before use.
Open a new chat inside the project and send:
Write a short invented scenario, about 250 words, about the accounts payable team at Company X. It should include five of the red flags from the outline, without naming them. After the scenario, give a facilitator answer key that lists each red flag, where it appears in the scenario, and the outline item it comes from.
What you should see: a short scenario in everyday language, followed by an answer key of five rows. Troubleshooting: If the scenario reads like a verdict ("Employee A clearly committed fraud"), ask for a rewrite that describes only what the records show.
Send:
Using the same scenario, write four discussion questions for a 20-minute group session. Then write a 10-question multiple-choice quiz on the red flags in the outline. Give four answer options per question and mark the correct one in a separate answer key. Next to each answer, name the outline item it comes from.
What you should see: four open questions, ten multiple-choice items and a key with outline references. Troubleshooting: If a question has two defensible answers, rewrite or drop it. If the key cites an outline item that does not support the answer, drop the question.
What you should see: a reviewed set that you would be comfortable presenting under your own name. Troubleshooting: If several questions fail, tighten the outline. Vague outlines produce vague quizzes.
Harder version for experienced staff:
Rewrite the scenario so only two red flags are obvious and three are subtle. Update the answer key and mark which flags are subtle.
Short pre-session check:
Write a five-question true/false warm-up on the outline. Include the answer key with the outline item for each answer.
Role-play prompts:
What you should see: the instructions saved with the project. Troubleshooting: If a later output ignores a rule, name the rule in the chat ("Rule 2: all names must be invented") and then make that rule more specific in the instructions.
Write three short role-play prompts where a staff member notices a red flag from the outline and needs to raise it with a supervisor. Do not script what the supervisor decides.
Quiz review:
Here is my quiz: [paste]. Mark any question with more than one defensible answer, and any answer not supported by the outline.