Inclusion of Social Media Simulators in Teaching: Making the Case

Most teachers who use a social media simulator found it themselves, used it for one lesson, and never told anyone. That is a reasonable way to start and a poor way to keep going, because the moment the exercise is worth repeating it needs to survive a curriculum review, a safeguarding lead and an IT policy.

This is about that second stage: the case for putting simulated social media into a scheme of work rather than beside it. If you are after specific exercises, the companion piece on eight lessons that work covers those.

What a simulator actually replaces

The case is easier to make once it is clear what the alternatives are, because every one of them has a cost that a simulator removes.

Instead of	The problem
A real screenshot	Shows a real person’s words and account to a room; may breach their privacy and your safeguarding policy
A live class account	Needs a platform account, age checks, a risk assessment and somebody to own it afterwards
A real misinformation post	Hands the post a new audience and a name worth searching
A hand-drawn slide	Looks wrong enough that students argue with the artwork rather than the content
Nothing	The commonest choice, and it leaves the topic taught abstractly

That last row is the honest comparison. In most schemes of work the realistic alternative to a simulated post is not a better example — it is a bullet point about online safety that nobody remembers.

Where it fits in a curriculum

Simulated social media is not a subject. It is a teaching material, and it fits wherever the subject already is:

• Computing and digital literacy — source evaluation, verification, how platforms signal trust.
• PSHE and citizenship — online safety, consent, coercion, the difference between a screenshot and evidence.
• English and media studies — register, audience, how format shapes a message.
• Business and marketing — campaign planning without a live account or a budget.
• Journalism and higher education — verification practice, where students need to handle plausible material rather than obvious fakes.

The marketing case is the one most often made in further education, where courses have to produce students who can plan a campaign without a department having to hand teenagers the keys to a real brand account. Published accounts of simulator use in college marketing modules tend to report the same motivation: the assessment needs realistic artefacts, and a live platform cannot safely supply them.

The objections, and what to say

“Are we teaching them to make fakes?”

This is the first question and the fair one. Three answers.

The skill is not scarce. A convincing chat mockup takes two minutes with a free tool, and any student motivated to make one will find one. What is scarce is the understanding that a screenshot proves nothing — and that is taught most effectively by making one.

Second, the good tools make their output identifiable. Every chat mockup from Zeoob carries a visible “Not an original screenshot” line that cannot be switched off, and every image carries a hidden origin mark the verification tool reads back from the original file. A class that knows this — including that resizing an image destroys the hidden mark — learns something true about provenance.

Third, the exercise where students build a fake and then watch their classmates believe it is the one they remember. Reading about misinformation produces agreement; making a piece of it produces caution.

“Is this safe for pupils to use?”

The generators run in the browser. No account, no sign-in, no post reaches any platform. The finished image is sent to the server once, when a student presses download, so it can be watermarked and signed. What is kept is set out in the privacy policy, and there is a summary for schools on the teachers page.

“What stops a pupil misusing it?”

Nothing stops a determined pupil making an image, any more than anything stops them using a photo editor. What the tooling changes is traceability: a chat carries a visible line, and the file carries a hidden mark that lasts until somebody resizes or re-encodes it. Neither is proof against a determined pupil, and both are a better position than the one you are in when a pupil uses a tool with no watermark at all, which is the realistic alternative.

Tell the class it is traceable. It is a deterrent and a lesson at the same time.

“We have no budget.”

There is nothing to buy. No licence, no per-seat cost, no account.

“Will it work on school machines?”

It needs a browser. If your network blocks third-party scripts, the tools still work — that only affects advertising and analytics.

What to put in a scheme of work

Three things make the difference between an exercise that survives review and one that gets quietly dropped:

1. Name the learning objective, not the tool. “Students can explain why a screenshot is not evidence” survives a curriculum review. “Students use Zeoob” does not.
2. Write the labelling rule into the task. Every artefact a student produces carries the word “mockup” on it. Make that a marked criterion and the safeguarding conversation becomes much shorter.
3. Keep the artefacts. Student mockups make better exam-prep material than anything you can buy, and they are already pitched at the right level.

The honest limitation

A simulator shows you a platform’s surface. It cannot show a feed’s behaviour — the ordering, the recommendation, the way one post leads to another, which is where a lot of the actual harm lives. A lesson built only on static mockups teaches students to assess individual posts, not systems.

Worth saying out loud when you propose it, because somebody will say it eventually and it is better coming from you.

Where to start

One lesson, one tool. The WhatsApp chat generator for an online-safety session, or the tweet generator for media literacy. Run it once, keep what the students make, and propose the scheme of work with their work as the evidence.

The eight exercises are a reasonable place to pick the first one from.