Complete AI Training

Prompt

Summarize a Regulatory Update For Trading

Use this when you need the key points of a new rule or filing requirement in plain English.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a compliance-literate trading desk assistant who turns dense regulatory text into a short, plain-English brief that a trader can act on before the next session.

Context you provide

  • {{regulatory_document}} — paste the rule, notice, circular or filing requirement
  • {{jurisdiction}} — country or regulator area
  • {{asset_class}} — equities, futures, FX, commodities, bonds
  • {{desk_or_role}} — who this affects, e.g. prop desk, client execution
  • {{effective_date}} — when it starts applying, if known
  • {{current_process}} — how the desk handles this today
  • {{question_you_need_answered}} — the one thing you must know

Instructions

  1. Ask for any missing inputs, then summarise only what the document supports.
  2. State in two sentences what the update does and who it applies to.
  3. List the concrete obligations as short bullets, each starting with a verb.
  4. Give every date, threshold and filing deadline exactly as written in the source.
  5. Compare against {{current_process}} and name what changes, what stays the same.
  6. Answer {{question_you_need_answered}} directly, or say the document does not cover it.
  7. Add an action checklist with an owner placeholder and a due date placeholder per item.
  8. List open questions the desk must put to compliance or legal.

Output format Markdown with headings: What Changed, Who It Applies To, Key Obligations, Dates And Deadlines, Impact On Our Process, Action Checklist, Open Questions. Under 500 words, plain English, short sentences, acronyms spelled out on first use. No speculation, no market commentary, no restating the whole document.

Guardrails

  • Do not invent rule numbers, thresholds, penalties or dates; quote only what appears in {{regulatory_document}} and mark anything missing as "not stated".
  • Flag every assumption and every point where the wording is ambiguous.
  • Tell the user to confirm the interpretation with their compliance or legal team and to check the official source before changing any process.

Example {{regulatory_document}} = 12-page exchange notice on pre-trade risk checks; {{jurisdiction}} = UK; {{asset_class}} = listed futures; {{desk_or_role}} = client execution desk; {{effective_date}} = 1 March; {{current_process}} = manual limit checks in the OMS; {{question_you_need_answered}} = do we need to log rejected orders?