How to Set KS3 Computing Cover Work With No Computers
A checklist for writing a KS3 Computing cover lesson that works without PCs, logins or slides, plus a complete one-hour cipher lesson with an answer key that a non-specialist can run.
Computing cover often goes wrong because of the technology itself. Logins fail, the room has been swapped, the projector doesn't work, or the cover supervisor doesn't know the software. Then a class of Year 8s has 55 minutes and nothing to do.
The fix is to plan cover that never needs a computer at all. "Unplugged" computing uses paper, pencils and puzzles to teach real computing ideas such as algorithms, binary, encryption and networks. The ideas are the same ones you'd teach on screen.
This page has a checklist for setting any no-tech computing cover lesson, and then a complete lesson you can print today.
Why unplugged cover works for Computing
- Nothing to break. No passwords, no network, no software updates.
- Any room works. If the lesson moves out of the IT suite, it still runs.
- A non-specialist can deliver it. Paper tasks with a clear answer key need no computing knowledge.
- It's still on-curriculum. Algorithms, data representation and cyber security are all in KS3 Computing, and unplugged tasks cover them properly.
The checklist: setting no-computer Computing cover
Go through this before you leave cover work. If you can tick every item, the lesson should run without you there.
Before the lesson
- Choose one concept only. For example "Caesar ciphers", not "cyber security". A single idea means one clear task.
- Make it printable in one go. Students need a single worksheet, double-sided at most. Don't leave tasks that need cutting out unless you've already cut them.
- Print more copies than you need. Add a few spares for the class list.
- Leave the answer key on a separate sheet for the supervisor, not on the student copy.
- Remove any reference to screens. Look for "open", "click", "log in", "watch" or "see slide". Each one is a point where the lesson can fail.
- Write the learning objective in plain English. For example: "I can encrypt and decrypt a message using a Caesar cipher."
The supervisor sheet
- Write a minute-by-minute plan. Supervisors find a timed plan much easier to follow than a list of tasks.
- Include a script for the start. Two or three sentences they can read aloud to explain the idea. Avoid jargon, or define it in the same sentence.
- Give one worked example they can copy onto the board. This is the most useful part for a non-specialist.
- Add an extension task for fast finishers, so "I've finished" doesn't turn into chatting.
- Say what to collect. For example: "Collect all worksheets in register order and leave them on my desk."
- Add a behaviour line. Tell them which school system to use and who to call.
Making it work for every student
- Start with something easy. The first question should take under a minute, so everyone gets going.
- Make the difficulty go up. Encode, then decode, then crack an unknown code.
- Add a support aid. An alphabet strip or a reference table at the top of the sheet helps students who need it, and doesn't give away the answers.
A complete example lesson: Caesar Ciphers (Year 7-9, 60 minutes)
You can copy this lesson directly. Every answer below has been checked.
Supervisor script (read aloud at the start)
"Today's lesson is about secret codes. For thousands of years, people have hidden messages by swapping letters for other letters. One of the oldest ways is called a Caesar cipher. You move every letter forward along the alphabet by the same number, called the shift. Computers still use the same idea of turning a message into a code, called encryption, to keep information safe online. You won't need a computer today, only a pencil."
Board example (write this up for the class)
Shift of 3: A becomes D, B becomes E, C becomes F, and so on. At the end of the alphabet you go back to the start, so X becomes A, Y becomes B and Z becomes C.
HELLO with a shift of 3 becomes KHOOR.
Timings
- 0-5 min: Register, hand out sheets, read the script.
- 5-10 min: Go through the board example together.
- 10-25 min: Task 1 and Task 2.
- 25-45 min: Task 3 (code-breaking).
- 45-55 min: Task 4 (write your own) and the extension.
- 55-60 min: Collect sheets, ask the exit question.
Student worksheet
Put this alphabet strip at the top of the sheet:
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Task 1: Encrypt (shift of 3)
- CODE
- BINARY
- Your own first name
Task 2: Decrypt (shift of 3)
Move each letter back by 3.
- FRPSXWHU
- DOJRULWKP
Task 3: Crack the code (the shift is unknown)
Try different shifts until you get real words. Tip: short words like "THE" or a double letter like "LL" can give the code away.
- TFDSFU (hint: a small shift)
- MJQQT BTWQI
Task 4: Write your own
Write a secret message of at least five words, choose your own shift, and swap with a partner if the supervisor allows it. Can they crack it without being told the shift?
Extension
- How many different shifts are possible for a Caesar cipher? Explain your answer.
- Why would a Caesar cipher be a bad way to protect your bank password? Write two sentences.
Exit question (answer aloud or on the back of the sheet)
What is the difference between encrypting and decrypting?
Answer key (supervisor only)
Task 1
- CODE → FRGH
- BINARY → ELQDUB
- Answers will vary. Check that each letter has moved forward by 3.
Task 2
- FRPSXWHU → COMPUTER
- DOJRULWKP → ALGORITHM
Task 3
- TFDSFU → SECRET (shift of 1)
- MJQQT BTWQI → HELLO WORLD (shift of 5)
Extension
- 25 useful shifts. There are 26 letters, but a shift of 26 (or 0) leaves the message unchanged.
- Accept answers that mention there are only 25 possible shifts, so someone can try them all quickly by hand. A computer can try them all almost instantly.
Exit question Encrypting turns a readable message into code. Decrypting turns the code back into the readable message.
Other topics that work unplugged
If you need more than one lesson, these KS3 topics also work well on paper. Use the same structure: script, board example, tasks that get harder, then an answer key.
- Algorithms: students write step-by-step instructions for a simple task, such as drawing a shape, then a partner follows them exactly and they fix the "bugs".
- Binary and denary: convert between binary and denary using place-value columns (128, 64, 32, 16, 8, 4, 2, 1).
- Pixels and images: shade a grid from a binary code (1 = black, 0 = white) to show a hidden picture, then discuss resolution.
- Networks: draw how a message is split into packets, numbered, and put back together at the other end.
- E-safety and digital footprint: read short scenarios and write down what the person should do and why.
Common mistakes to avoid
- "Continue with your project on the shared drive." This only works if every login and file works, so it often fails.
- Video-based cover. If the screen or the internet fails, nothing is left.
- Worksheets with no answer key. The supervisor can't help students who are stuck, and marking falls back on you.
- Too many tasks. Three or four tasks that get harder keep a class busy longer than ten unrelated ones.
- Missing the "what next" line. Always say what students should do when they finish.
Quick copy-and-paste template for your cover sheet
Class: ____ Room: ____ Period: ____ Topic: ____ Learning objective: I can ____ Resources: worksheet (on desk, ___ copies), pencils, answer key (separate sheet) Read aloud at start: ____ Write on board: ____ Timings: 0-5 / 5-10 / 10-25 / 25-45 / 45-55 / 55-60 Fast finishers: ____ At the end: collect ____, leave on ____ Behaviour: use ____ system; call ____ on ext. ____
If you fill in this template once for each topic and keep the printed copies in a labelled folder, Computing cover becomes a two-minute job, even when you're off unexpectedly.
Browse the Quillwork shop