How to Run a Coding Workshop for 100+ Students

A practical guide for schools on running a coding workshop for 100+ students: format, logins and Wi-Fi, a 60-90 minute plan, helpers, safeguarding and impact.

How to Run a Coding Workshop for 100+ Students

By Yuness, qualified Computer Science teacher and former Head of KS5 Computer Science · Last reviewed 21 November 2026

To run a coding workshop for 100+ students, decide on one clear goal, split the cohort into groups of class size with a teacher in each room, and use a browser-based tool so there is nothing to install, testing logins and Wi-Fi at full scale before the day. Run a tightly timed 60–90 minute session: a short hook, a live-coded demo, paired practice with tiered extension tasks, and a show-and-tell at the end. Do the visitor safeguarding checks early, keep the pre/post survey to a handful of questions, and give every student a way to keep coding afterwards.

This guide for CS teachers, STEM and careers leads and outreach coordinators draws on published guidance from the Raspberry Pi Foundation, Code Club, STEM Learning, the NSPCC and the Department for Education (DfE). Shuttle has delivered five coding workshops in schools so far. The most recent was at Ada, the National College for Digital Skills, a sixth form college and apprenticeship provider, where 100+ students took part in London. That session ran on our free browser-based Python platform. The advice below is general professional guidance, not a write-up of any one event.

Workshop planning at a glance

WhenWhat to sort outWho owns it
4–6 weeks beforeGoal, year group, format (one hall or several rooms), date, visitor safeguarding checksSTEM/careers lead and host teacher
2–3 weeks beforeRooms, devices, student logins, the tool, a Wi-Fi test at full scale, helper briefing, SEND informationHost teacher and IT support
The week beforeDry run on a school device, printed backup sheets, pre-survey, the extension task ladderFacilitator and host teacher
On the dayArrive early, sign in, test one device per room, run the 60–90 minute planEveryone
Within 1–2 weeksPost-survey, share links so students can keep coding, debrief with staffHost teacher and facilitator

Start with one goal, then choose the format

Big workshops can lose focus when they try to inspire, teach syntax, promote GCSE options and tick a careers benchmark all at once. Pick one primary goal.

  • Confidence and enjoyment (often Year 7–9): every student should leave having written and run working code.
  • Options and pathways (Year 8–9, before GCSE choices): show what Computer Science involves and who it is for.
  • Stretch (GCSE or sixth form): a harder problem that links to the course. See our GCSE Computer Science hub and OCR A Level hub for topic links.
  • Careers: if a careers lead wants the session to count as an employer encounter, design it to fit the statutory criteria (see below).

Format options for 100+ students

  • Parallel rooms: four or five computer rooms run the same session at the same time. Each has a teacher, and the facilitator moves between rooms or runs the demo on a shared screen. This is often the easiest to manage.
  • Carousel: groups rotate through one computer room over a morning or day. Fewer device and Wi-Fi problems, but more timetable disruption.
  • Hall with laptops: the most energy, but the hardest for Wi-Fi, sound and getting help to stuck students. Only choose it if the network has been tested at that load.

Safeguarding for external visitors

If someone from outside the school is leading the workshop, sort this out first. As of November 2026, the DfE's statutory guidance Keeping children safe in education 2026 has been in force since 1 September 2026. Its section on visitors says the following:

  • Schools receive many kinds of visitors, including "educational visitors like guest speakers or performers".
  • For visitors who come in a professional capacity, schools should check ID and be assured that the visitor has had the appropriate DBS check. They can rely on the visitor's employer confirming checks rather than asking to see the certificate.
  • Where a visitor will have no contact with children, a DBS check is unlikely to be required.
  • Headteachers and principals should use their professional judgement on whether visitors need to be escorted or supervised.
  • Schools should think carefully about whether external organisations that provide speakers or resources are suitable. Safeguarding policies may include an assessment of the educational value and age appropriateness of what will be delivered.

The NSPCC's guidance on school visitors adds the practical side. Check and log visitors' ID on arrival, make sure they wear a visible visitor badge, and tell every visitor how to report a concern and who the child protection lead is. Visitors should only be alone with children if the school has given permission. The simplest arrangement is for a member of staff to stay in every room for the whole session. Do not take photos of students without the school's prior permission.

If you use volunteers through STEM Learning, the STEM Ambassadors handbook for educators says all Ambassadors hold an enhanced DBS (or PVG in Scotland) certificate and volunteer for free. It also asks schools to give clear activity details well in advance.

Logistics: rooms, devices, logins and Wi-Fi

A large workshop can lose its first ten minutes if 100 people try to log in at once and something goes wrong.

Browser-based tools vs installed software

Installing Python or an IDE on school machines means IT tickets, admin rights and version mismatches. A browser-based tool avoids that. Check three things in advance: the site is not blocked by the school's web filter, it works in the browser version on school devices, and it works on whatever students will actually use (desktops, laptops or tablets). If you are comparing options, see our sibling guide to free Python platforms for schools.

Logins

  • Decide early whether students need an account at all. If they do, create accounts in advance and print login slips, one per student, sorted by group.
  • Avoid "sign up with your school email" on the day. Forgotten passwords, verification emails and filtering can eat a large part of a short session.
  • Keep a spare set of guest logins or a no-login fallback activity for each room.

Wi-Fi and devices

The DfE's wireless network core standard says school networks should support all devices logging on and being used at the same time. Schools should be working towards meeting the standard by 2030, so many networks may not meet it yet. Ask IT for a test: as many devices as you will use, in the actual rooms, loading the actual tool, at the same time of day. Also:

  • Count working devices per room the week before, including chargers for laptops.
  • If devices are short, plan for pairs. Code Club's guidance suggests pair programming when there are not enough computers.
  • Have the demo projector, sound and a large font checked in each room.
  • Print a one-page backup with the task, starter code and extension challenges in case the network drops.

Structure of a 60–90 minute session

The plan below combines Code Club's advice on starting a session with the Raspberry Pi Foundation's computing pedagogy principles, especially PRIMM (Predict, Run, Investigate, Modify, Make). Stretch or compress the practice blocks to fit 60 or 90 minutes.

Time (90 min)PhaseWhat happens
0–10HookShow the finished project working. Give a one-sentence goal. Explain the "how to get help" routine.
10–20Predict and runStudents get working starter code, predict in pairs what it will do, then run it.
20–30Live-coded demoThe facilitator builds the tricky part live, thinking aloud and making one planned mistake.
30–65Paired practiceModify the starter code through a ladder of tasks. Driver and navigator swap regularly.
65–80Make and extendStudents personalise their project. Fast finishers take on extension challenges.
80–90Show and tell, then exit surveyShow two or three student projects on screen, give next steps, and run a two-minute post-survey.

Why this order works

  • Show the finished product first. Code Club recommends showcasing a completed project so students have a clear goal, and demonstrating a tricky section before independent work.
  • Start from working code, not a blank screen. The Raspberry Pi Foundation's PRIMM quick read recommends giving students working starter programs to run rather than a blank editor, to reduce anxiety and frustration with syntax errors. It also recommends keeping predictions low-stakes.
  • Live code, don't paste. The live coding quick read advises narrating your thinking, asking students to predict before running, making deliberate mistakes linked to common misconceptions, and using the largest font that still shows a full line of code. In a big room, the font size matters more than you would expect.
  • Pair up. The pair programming quick read describes a driver (keyboard) and a navigator (aims, errors, instructions) who swap roughly every 5 to 10 minutes. It cites a study that found a significant increase in confidence among women who were paired, while noting that the evidence is limited. It also warns you to stop one partner dominating.

Roles for helpers

With 100+ students, the facilitator cannot answer every question. Give each adult one clear job.

  • Lead facilitator: runs the timings, the demo and the transitions. They should not get stuck at one desk for long.
  • Host teacher in every room: knows the students, applies the school's behaviour policy, and is the safeguarding presence. External visitors should not be managing behaviour on their own.
  • Roaming helpers (staff, sixth formers, STEM Ambassadors): answer questions using a "hands off the keyboard" rule. Code Club's top tips advise helpers to keep their hands off the mouse and keyboard and ask questions so students can fix their own errors.
  • Tech lead: someone from IT or a confident teacher who sorts out logins and connection problems, so content helpers can keep helping.

Brief helpers for ten minutes beforehand: the task ladder, the three most likely errors, the help routine, and who to tell about a safeguarding concern. For classroom routines that cut down on hands-up queues, see our guide to debugging routines for Python lessons.

A help routine that scales

Code Club suggests agreeing in advance what students do when stuck, and offers the motto "Ask three, then me" to encourage them to try solving problems on their own before asking an adult. Trying a partner or a neighbour first fits naturally with paired work. Add a visible signal, such as a card on the monitor, so helpers can see who has been waiting longest.

Differentiation and extension tasks

In a group of 100, some students will never have written code and some will finish the core task in ten minutes. Plan for both with a single ladder that every student can climb.

  1. Entry: run the starter code and change one value (a message, a number, a colour).
  2. Core: modify the code to add one feature, with a hint sheet.
  3. Stretch: add a condition or loop that the demo did not show.
  4. Extension: an open challenge with no hints. For example, make the program handle bad input, or design your own version for something you care about.

The Raspberry Pi Foundation's Universal Design for Learning quick read suggests offering multiple entry points: remixing code, fixing buggy code, Parsons problems or extension challenges. Parsons problems (putting jumbled lines of code back in order) are useful in workshops because you can adjust their difficulty. Structural cues such as indentation make them easier, while extra "distractor" lines stretch confident students. The same quick read cautions that distractors can add unnecessary cognitive load, and cites research finding they reduced learning efficiency for young novice programmers, so save them for the extension tier.

Accessibility and SEND

  • Ask the host school's SENCo, before the day, about students who need adjustments: seating, screen readers or zoom, printed instructions, or a quieter room.
  • Give instructions in more than one form: spoken, on screen and on paper. This is the "multiple means of representation" principle in UDL.
  • Keep starter code short and well spaced, and do not rely on colour alone to show errors in your slides.

Engagement, behaviour and underrepresented groups

Use the host school's behaviour routines rather than inventing your own. Agree an attention signal with staff before the start. Code Club recommends setting a few shared rules and celebrating work through show-and-tell.

If one aim is to widen participation, look at the evidence from the DfE-commissioned Gender Balance in Computing programme. The Raspberry Pi Foundation led it as part of the National Centre for Computing Education between 2019 and 2022, with more than 14,500 pupils. The main findings:

  • Fewer secondary pupils than primary pupils reported intending to study computing. The gap was larger for girls, and intent dropped sharply among girls aged 12 to 13. That makes Years 7–9 a sensible target for workshops.
  • Girls valued collaboration and teamwork, which supports the case for paired work.
  • In the relevance study, Year 8 pupils designed an app for a community they belonged to and made a paper prototype before coding. Girls valued the creative expression, and the prototyping lessons were particularly popular with them.
  • The trials found no quick fix. Most showed positive effects that fell just short of statistical significance, and the authors recommend combining several approaches. A one-off workshop works best as one part of a wider plan.

In practice, that means letting students choose the context for their final "make" task, and building in some design or creative choice, not just correct output.

Careers links: meeting Gatsby Benchmark 5

For careers leads: the DfE's statutory careers guidance (updated 23 June 2026) expects schools to give every pupil at least one meaningful encounter with an employer each year from age 11. A meaningful encounter is one where pupils learn what work is like, what skills are valued and what it takes to succeed. It also needs two-way interaction, a clear purpose shared with the employer and the young person, and time afterwards to reflect. If you want a workshop to contribute, include a short Q&A with the visitor and a reflection question in your post-survey. Check with your careers leader how your school records encounters.

Measuring impact with simple pre/post questions

Keep measurement light, or nobody will finish the survey. Ask the same 3–5 questions at the start and the end, using the same wording and scale. For example:

  • "I can write a short program in Python" (1–5 agree scale).
  • "I could fix an error in my code without help" (1–5).
  • "People like me can be good at programming" (1–5).
  • "Which of these subjects might you choose for GCSE?" (a tick-list that includes Computer Science).

That last format is deliberate. In the Gender Balance relevance study, a yes/no question about choosing GCSE Computer Science found no significant difference between groups. A question asking pupils to select from a list of subjects did find one for girls. Add one open question at the end, such as "What would you want to make next?", and record attendance by year group.

Be honest about what the results mean. The Centre for Transforming Access and Student Outcomes (TASO) classes pre/post designs without a comparison group as Level 1 (Monitor) evidence. They show whether outcomes changed for participants, but they assume nothing else changed in between, which TASO calls "not very plausible". Report them as "students' self-rated confidence rose from X to Y", not "the workshop caused Y". Follow your school's data protection rules: anonymous forms, or matching by a non-identifying code, are usually enough.

Follow-up: what happens after the workshop

A single session changes little unless it leads somewhere. Before the day, decide on these:

Where Shuttle's free Python platform fits

Yuness built Shuttle's platform for his own students first. Students write real Python in the browser, with nothing to install. Every answer is marked as soon as it is submitted, with feedback that points to the exact mistake and suggests a next step. That can ease the hands-up queue when 100 students are coding at once. A "Summarise" button shows the teacher the most common mistakes and where each student got stuck, which is useful both during the session and for the follow-up. It covers GCSE, A Level and IB content and is free for schools. Schools are onboarded one at a time through the form on our schools page.

FAQ

How many helpers do I need for a 100-student coding workshop?

At minimum, have one member of school staff in every room for the whole session for safeguarding and behaviour, plus the lead facilitator. Add roaming helpers until no student waits more than a few minutes for help. Paired work and "Ask three, then me" can reduce the demand.

Do external workshop leaders need a DBS check?

It depends on the activity. Keeping children safe in education 2026 says schools should check professional visitors' ID and be assured they have had the appropriate DBS check, which can rest on the employer's confirmation. Headteachers decide on supervision. Ask the host school's designated safeguarding lead early.

Should students install Python for a one-off workshop?

Usually not. Installing software across 100 school devices is slow and needs IT access. A browser-based tool avoids it, but you must check it is not blocked by the school's web filter and works on the devices students will actually use.

What year group is best for an outreach coding workshop?

It depends on your goal. If you want to influence GCSE choices, the Gender Balance in Computing findings suggest Years 7–9, because intent to study computing drops in secondary school, especially among girls aged 12 to 13.

How do I show the workshop made a difference?

Use 3–5 matched pre/post questions, including a subject-choice tick-list, and report the change honestly as monitoring evidence, not proof of cause. Follow up a few weeks later by checking who joined a club or carried on coding.

If you are planning a workshop, or just want a browser-based Python tool your students can use straight away, take a look at our schools page, where you can register your school for the free platform.