← Day 2
Day 2 · Facilitator Demo Guide
Instructor Only · Live Demo Script

The demos, ready to run.

Everything you run from the front of the room on Day 2 — Excel, PowerPoint, and Security & Ethics — then wrapping up. Each demo uses its own data and prompts, deliberately different from the trainee lab, so your live run never hands out the answers. Tap any prompt to copy it.

⚠ All fictional sample data — no real customers, accounts, or figures. Never paste real data into a prompt.
This page is for the facilitator. Trainees work from day-2-branch-transactions-TRAINEE.xlsx and the Day 2 lab; you demo from day-2-branch-transactions-DEMO.xlsx and the recap below. Same skills, different data — so the room can't just copy you.
Facilitator demo workbookday-2-branch-transactions-DEMO.xlsx · 905 rows · H1 2026 Trainee practice workbookday-2-branch-transactions-TRAINEE.xlsx · 736 rows · H2 2025 Facilitator messy deckday-2-messy-deck-DEMO.pptx · Digital Channels · for the restructure demo Earnings release (doc→deck)burgan-fy25-earnings-release.pdf · shared with trainees
1

Excel — analyse the worksheet · 5 branches · Jan–Jun 2026

Differs from trainees Trainees analyse 4 branches over Jul–Dec 2025; you demo 5 branches over Jan–Jun 2026. Open the demo workbook and click into the table before you start.

Run this

tap to copyLive demo promptAnalyze this table of branch transactions. What are the top 3 trends by month and by branch? Which branch had the sharpest single-month drop, and in which month? Add a column for month-over-month growth per branch, and chart the top 5 branches by total volume.
You already know the answer — so you can check Copilot

The data has a planted story: Salmiya drops ~29% in March (branch renovation) then recovers by May; Fahaheel grows every month (Jan ≈ 4,076 → Jun ≈ 5,293, about +30% over the half). If Copilot names Salmiya + March as the sharpest drop, it read the table correctly. If it says anything else, open a PivotTable and show the room the truth.

Teaching beat — the verify habit

Open the growth column's formula out loud: "could you defend this number to Finance?" That single move — reading the working — is the whole point of the Excel session. An answer you can't check is a spell, not analysis.

2

PowerPoint — report to deck · create · generate · restructure

Differs from trainees Trainees restructure the Branch Network Review deck; you demo on a different mess — the Digital Channels deck — so your live fix doesn't hand out their answer. Doc→deck reuses the shared earnings release.

Move 1 · Create — document → deck

tap to copyRun in PowerPoint (source: earnings release)Create a presentation from the Burgan FY25 earnings release: a 6-slide management summary — headline results, key financials, segment performance, outlook, risks, and a closing 'so what'. Keep every figure traceable to the source and add speaker notes.

Move 2 · Generate — a new slide from a prompt

tap to copyGenerate one fresh slideAdd one slide on 'what this means for our branch teams', with 3 bullets in plain language and a one-line takeaway.

Move 3 · Restructure — fix the messy deck

tap to copyRun on day-2-messy-deck-DEMO.pptxThis presentation is disorganised. Reorganise it into a logical flow (title → agenda → findings → recommendations → next steps), merge the duplicate outage slide, tighten each text wall to 3–4 bullets, and list exactly what you changed.
What to show the room

The demo deck has planted messes: the agenda slide is in the wrong place, the summary sits at the top instead of the end, and there's a duplicate outage slide. A correct restructure moves the agenda to slide 2, the summary to the end, and merges the outage duplicate. If Copilot misses the duplicate, catch it live — that's the teaching beat.

Teaching beat — polish is not proof

On Move 1, open one generated slide against the earnings PDF and check a number aloud. A deck inherits the document's facts only if a human verifies them. Never let a slick-looking slide ship an unchecked figure.

3

Bank-safe use, security & ethics · the three lines

Differs from trainees Trainees fix an unsafe prompt in the lab; you run both prompts live so the room sees the boundary before they practise it. Run the safe one for real; read the unsafe one aloud and stop before you paste.

Run this — safe

tap to copySafe · grounded, verifiableSummarise our remote-working policy and quote the exact clause on approved devices. Link the source document so I can open it.

Read aloud — never run

tap to copyUnsafe · stop before you pasteHere is customer 8842's full statement and Civil ID — draft a letter explaining why their loan was declined.
Land these three lines
  • The boundary — Copilot is grounded in your permitted M365 content under Enterprise Data Protection; it stays in Burgan's tenant and never trains the public model.
  • The data rule — follow the bank's classification before you paste. Real customer data, Civil IDs, account numbers → never in a prompt. In doubt, don't.
  • Human accountable — a model can draft the words, but a person owns the decision, checks it for fairness, and signs off.
The ethics beat

The unsafe prompt fails twice: it leaks real customer data and it lets a model shape a lending decision. Ask the room: "who is accountable if that letter is wrong or unfair?" The answer is always a human — that's the line Copilot never crosses.

4

Wrapping up — the close · assessment, then survey

Facilitator role This is a close, not a demo — you're steering the room through two links, not running a prompt. Put both on screen and give the room quiet time to do each one before you send them off.

1 · Post-workshop skills-map assessment

Point the room to the Wrap up exercise in the Day 2 lab (or share the link). It's the same skills map they took on Day 1, so it measures the shift across the two days — frame it as a measure, not a test.

tap to copyPost-workshop assessment linkhttps://portal.joincoded.com/sv/microsoft-365-copilot-skills-map-burgan-bank-post

2 · Workshop feedback survey

Once the assessment is in, move the room to the feedback survey — a few minutes while the two days are still fresh. Say plainly that it shapes the next cohort's workshop.

tap to copyWorkshop feedback survey linkhttps://portal.joincoded.com/sv/burgan-workshop-microsoft-copilot-for-productivity-survey
The close

Land the two-day arc: Copilot went from an icon they scrolled past to a tool they can drive — bank-safe, with a human accountable. Confirm both the assessment and the survey are submitted before anyone leaves the room.