Technical Anshu
Tutorials Blog
📢 Staff Briefing

Announce the Programme Not the Date the Honest Way to Brief Staff

The ethical pattern used by mature programmes is simple to say and easy to get wrong: tell everyone the programme exists, teach them the skill, and keep only the timing quiet. This page gives you the briefing, in the order it should happen.

✍️ Technical Anshu📢 Staff Briefing⏱️ Fifteen minutes, once a year
🎥 Watch the full video - the phishing simulation setup shown step by step

Surprise is a tool with exactly one legitimate use in this programme - the day of the test. Surprise about the programme's existence, its rules or its consequences is not realism; it is an ambush, and ambushed staff learn resentment instead of security. Brief first, and the simulation becomes what it was approved to be: practice.

The pre-brief - what every member of staff hears first
✔ Simulations will run during this quarter - dates stay unannounced
✔ The report button: where it is, and a live demonstration
✔ If you click: a short lesson page appears - nobody is punished
✔ Reporting a real suspicious email works exactly the same way
✔ New joiners get this briefing at induction, before any test
Five sentences carry the whole fairness of the programme. If your staff could not repeat them back, the briefing has not happened yet.
1

Announce the programme, not the date

One short all-staff message or meeting segment covers it: the company runs simulated phishing as training; tests will arrive sometime this quarter without further warning; the purpose is practice; clicking brings a lesson, never trouble; reporting is the skill being built. That framing is not a leak that ruins the test - it is what makes the test legitimate, and a quarter is a wide enough window that nobody can simply stay alert for a week and relax.

2

Teach the report button before the first test

A simulation that tests a skill nobody was taught measures nothing but luck. Before round one, show every employee the exact reporting route in your mail system - the Report Phish style button in their client, or the shared security mailbox if that is your process - and let them try it on a sample message. The campaign then practises a known skill under mild pressure, which is what training means.

3

Give managers their three lines

Team leads will be asked questions you cannot predict, so equip them: this is training agreed by management and HR; nobody is disciplined for a click; if your team member is upset, send them to the programme owner, not to a group chat. A manager who improvises a threat - however jokingly - can undo the programme's trust in one sentence, so the lines are worth writing down and circulating with the approval.

4

Cover the edges - joiners, returners, leadership

New joiners hear the briefing at induction and are only included from the following round. Staff returning from long leave get the same catch-up. And leadership is inside the audience, not above it: senior inboxes are the most valuable phishing targets in the building, managers click in real incidents every week, and a programme that exempts the top quietly tells everyone it is theatre.

🔴 Nobody is tested before they were briefed - that is the fairness line. It costs one round of patience for new joiners, and it is what lets you answer any complaint with a straight face and a clean document.

🎥 Watch the Complete Video

Watch the video build the campaign that goes out after the briefing is done.

▶️ Watch Full Video
❓ Common Questions (FAQ)

If we announce it, will staff just stay careful for a while?

The announced window is a whole quarter, not a week - nobody sustains test-mode alertness for three months. What the announcement really changes is the meaning of a click: practice they agreed to, not a trap they resent.

Should we tell staff after each round finishes?

Yes - a short note when the window closes: the totals, the lesson the email taught, and thanks to the reporters. Closing the loop keeps the programme visible as training rather than as silent surveillance.

Can we skip the briefing for a surprise baseline test?

That is the one shortcut this programme refuses. An unannounced baseline measures people who were never taught the skill or told the rules, and the resentment it creates costs more than the data is worth.

This guide is based on the phishing simulation video by Technical Anshu • Stuck on a step? Ask in the video comments - you will get an answer there 🙏