Everything from the two days, on one page. Each card: what it is, the everyday thing it's like, and the one tell that makes it click. Keep this open while you work.
CTFT
context · task · format · tone
Like a recipe card — four ingredients, one dish.
Context (the situation, incl. any role for Copilot) · Task (what to do) · Format (length, structure) · Tone (the voice). You rarely need all four spelled out.
10-year customer, card delayed, our error → apology email → under 120 words + a number to call → warm, professional, no compensation promised.
The tell: a wrong result = a missing ingredient. Find it, add it, re-run.
Iterate
the first answer is a first draft
Like a tailor's first fitting — pins, not the final suit.
Talk back to the draft instead of rewriting by hand: shorter, warmer, as a table, for management. Nobody nails it in one shot — that's the method, not failure.
"Make it 20% shorter and a bit more formal."
The tell: you steer with follow-ups.
Role & Example
the builder extras
Like telling the intern who to be — and showing one finished sample.
Give Copilot a role inside your Context, and optionally an example to imitate. One example changes structure and voice (that's few-shot prompting).
"You are a corporate credit analyst at Burgan Bank… match the structure of our last review note: [paste]."
The tell: Role lives inside Context; Example is optional, not required.
Context · Task · Format · Tone — and when the result comes back wrong, the recipe tells you which ingredient is missing.
Word
draft · rewrite · ground
Like a sous-chef — does the chopping, you plate it.
Draft from a prompt, rewrite tone or length, summarise a long document — and refer to a file so the draft is grounded in real content.
"Draft a customer letter from these bullet points…" → "Rewrite it to match the tone of the branch letter."
The tell: iterate, don't hand-edit — the rewrite move is the skill.
Outlook
inbox triage
Like the colleague who takes perfect minutes.
Summarise the messy thread — issue, promises, outstanding — then draft the reply in your tone, and catch up after time away.
"Summarise this thread — what's promised, what's outstanding? Draft a warm reply under 120 words."
The tell: separate promised from outstanding before you reply.
Excel & PowerPoint
day 2 territory
Like an analyst and a designer, on call.
Excel: ask your data questions and get working you can check. PowerPoint: a document becomes a deck in minutes. Both go deep on Day 2.
"What are the top 3 trends in this table?" · "Create a presentation from this document."
The tell: same CTFT recipe — pointed at numbers and slides.
Word drafts, Outlook triages, Excel answers, PowerPoint presents — one recipe steering all of them.
Sample Data Only
nothing real in a prompt
Like the branch lobby — on speakerphone.
In training, nothing real or confidential ever goes into a prompt. At work, follow the bank's data rules before you paste anything.
A real customer's figures stay in the core system — never in a chat box.
The tell: pause before paste.
The Copilot Boundary
why a bank can use it
Like an intern with a badge — sees only the rooms you can enter.
Grounded in your permitted content via Microsoft Graph; respects your existing permissions; Enterprise Data Protection — your data stays in the tenant and never trains the model.
A public chatbot can't see your work. Copilot can — within your permissions, inside the bank's walls.
The tell: same kind of engine as public AI; very different boundaries.
The Verify Habit
fluent ≠ correct
Like maker-checker — nothing ships unchecked.
AI predicts plausible text, so gaps get filled with confident guesses — and summaries can misplace a number. Check before it leaves your hands.
"Show me the exact sentence in the report where the [X] figure comes from." → then read it yourself.
The tell: the one-minute check is the difference between a tool and a liability.
Sample data in training, boundaries understood, everything verified — that's bank-safe.