How to Run a First Coding Club Session for Beginners
Twelve people have signed up, half of them have never written a line of code, and you have 90 minutes in a borrowed room.

Twelve people have signed up, half of them have never written a line of code, and you have 90 minutes in a borrowed room. Planning a first coding club session feels harder than it should, because the first meeting decides whether anyone comes back for the second.
I have run first sessions for school clubs, library groups, and adult evening classes. The plan below is the one I keep coming back to. It is built around one idea: everyone should leave having made something that works, however small, and wanting to change it.
What a first coding club session needs to achieve
A first meeting has three jobs, and teaching syntax is not one of them. The first job is getting every person to run code on their own machine. The second is making something visible happen, like text on a screen that responds to them. The third is building a sense that this group is a friendly place to be confused.
If people leave knowing what a variable is but never got their editor working, they will not return. If they leave with a tiny guessing game they built themselves, they will, even if they could not explain half of it. Keep that order of priorities in mind when something runs late.
Before the day: setup that saves the session
Most first sessions fail in the first 20 minutes, while people fight with installs. You can remove that risk almost completely.
- Pick a browser-based editor. For a first meeting, a web editor that runs Python in the browser means nobody installs anything. Local setup can wait until week two or three.
- Test on the actual room's network. School and library networks often block sites. Visit the venue a few days early and try the editor on their wifi.
- Bring three spare devices. Someone will have a locked work laptop or a phone only. Spare machines keep them in the session.
- Print a one page sheet. Include the editor address, a sample program, and three challenge ideas. Paper is easier to glance at than a second browser tab.
- Write a starter program in advance. About 10 lines that already work. People edit faster than they write from scratch.
If you have more than eight beginners, recruit one helper for every six people. A helper does not need to be an expert. They need to be calm and willing to say "let us read the error together".
A 90 minute plan that works
Here is the timing I use. Adjust the blocks, but keep the order.
| Time | Block | What happens |
|---|---|---|
| 0 to 10 min | Welcome | Names, why each person came, one sentence each |
| 10 to 20 min | First run | Everyone opens the editor and runs print("hello") with their own name |
| 20 to 45 min | Guided build | Together, change the starter program into a number guessing game |
| 45 to 55 min | Break | Snacks, informal questions, helpers walk around |
| 55 to 80 min | Free change | Pairs pick a challenge from the sheet and modify their game |
| 80 to 90 min | Show and plan | Three volunteers show their screens, then announce next week's topic |
The guided build is where you teach, but teach through change, not explanation. Show the line that picks a random number. Ask the room to guess what happens if you change 10 to 100. Run it. That loop of predict, run, and see keeps people engaged far longer than slides.
The advice I push back on
A common suggestion is to open with a talk on what programming is, how computers work, and why coding matters. It comes from a good place. The organiser wants people to understand the big picture before they touch code. In practice it costs you the room.
Beginners at a first coding club session are often nervous that they will not be smart enough. Fifteen minutes of theory confirms the fear, because it sounds like school. Getting their name on screen in the first ten minutes does the opposite. It proves they can do this. The big picture lands much better in week four, once people have context to hang it on.
The same goes for a perfect, polished demo. Make a small mistake on purpose during the guided build, read the error aloud, and fix it. It shows the group that errors are normal and that reading them is a skill they will learn. Our guide to helping a beginner debug without fixing the bug for them covers how helpers can handle the same moment one to one.
Pairs, not solo work
In the free change block, put people in pairs with one keyboard. One person types, the other reads the sheet and suggests the next change, and they swap every ten minutes. Pairs ask fewer questions of the organiser because they solve the small problems together, and the quiet people have someone to talk to.
Pair a slightly more confident beginner with a nervous one if you can, but avoid pairing a complete beginner with someone experienced. The experienced partner tends to take the keyboard. There is more detail on this in why pair programming works differently with complete beginners.
Adjusting for kids, teens, and adults
For children under 12, cut the session to 60 minutes and use a visual starter, such as a turtle drawing program, instead of a guessing game. Shapes on screen are more rewarding than text. The approach in how to teach coding to kids without losing them in syntax fits this age group well.
Teens tend to want to make something they can show friends. A guessing game with jokes in the messages works, as does a simple quiz about their favourite game. Adults often arrive with a specific goal, like automating a spreadsheet at work. Ask about it in the welcome round and mention, honestly, which week you will get close to it.
After the session
Send a short message within 24 hours. Include the editor link, the final version of the guessing game, and one optional challenge for the week. Keep it under 100 words. Then write down for yourself what ran late and which challenge was most popular, because that tells you how to pitch the second meeting.
Frequently asked questions
How long should a first coding club session be?
Sixty to ninety minutes works for most groups. Under 12s do best with about an hour, while teens and adults can handle 90 minutes with a break in the middle. Longer than that and attention drops sharply for beginners.
What should beginners build in their first coding session?
Something small that responds to them, such as a number guessing game or a program that greets them by name. The goal is a working result they can change. Larger projects can wait until they are comfortable with the editor.
Do I need to be an expert programmer to run a coding club?
No. You need to be a step or two ahead of the group and comfortable saying "I do not know, let us find out". Preparing the starter program and testing it in advance matters more than deep expertise.
More in Teaching Code
Teaching Code
How to Teach Beginners to Read Python Documentation
I ran a small test at club last February because I was tired of a specific pattern.
Teaching Code
How to Teach the Difference Between print and return
In week five of our adult evening group, a learner called me over because her code had stopped working.
Teaching Code
How to Train Volunteer Mentors for a Coding Club
Our club recruited nine volunteers in one term. Three were still turning up by week six.