Teaching outside your specialism? Start with the spec, not the slides

If you have just started teaching a subject you did not train in, or you are an ECT in your first term, you have probably inherited a folder. It has a scheme of work, a few dozen slide decks in three different fonts, and a worksheet called "Unit 3 FINAL v2". Nobody can tell you when it was last checked against the specification.

That folder is worth using. It just needs checking before you trust it, and the checking is quicker than most people assume. Below is how I would go about it, where the time really goes, and where a tool can help without doing your thinking for you.

Why inherited resources drift

Department resources rarely start out wrong. They drift. Specifications get revised and the slides do not. A colleague who taught a different exam board leaves a few decks behind. Someone adds a lesson on a topic they love that has not been examined for years, while a spec point that turns up every summer gets a single slide at the end of a busy week.

A specialist tends to notice this without trying. If you are new to the subject, you are in a harder position: you cannot see a gap in content you have never been taught yourself. That is not a criticism of you. It is the reason to check against the source document rather than against the folder.

A 20-minute spec audit you can do this week

Pick one unit, the one you are teaching next, and do this before you plan anything new.

1. Download the current specification from the exam board's website. Not the copy on the shared drive. Check the version number and date on the front cover.
2. Put the scheme of work next to it. Against each lesson, write the specification reference it covers. Most boards number their content (OCR's A Level Computer Science uses references such as 1.4.1), which makes this quick.
3. Highlight every spec point with no lesson against it. Those are your gaps, and they are the ones that cost students marks.
4. Mark every lesson with no spec reference. It may be there for a good reason, such as prior knowledge or a practical skill, but you should know what that reason is.
5. Read the latest examiners' report for that unit. It tells you where candidates lost marks last time, which is often exactly where the resources are thinnest.
6. Look at the command words. If the specification says "describe" and your worksheet asks students to "evaluate", or the other way round, the depth is off.

Twenty minutes per unit is realistic once you have done the first one. You do not need to audit the whole course in October half-term.

Where the planning time actually goes

Once you know your gaps, you have to fill them. For each missing lesson that usually means four things: a plan, a slide deck, a worksheet and a set of answers.

The answers are the part most often skipped, and for a new teacher they matter most. Working through your own worksheet is where you find out whether you understand the topic well enough to teach it. Skip that step and you find out in front of thirty students instead.

Building all four from a blank page, for a topic you are learning yourself, is where the evenings disappear. That is the part worth speeding up. The audit above is not.

Where Lesson Studio fits

This is the part where I mention something I built, so weigh it accordingly. I teach Computing, and I made Teacher Task Manager to deal with my own workload. Its newest feature, Lesson Studio, came out of exactly the problem above.

You start by choosing the specification points you want to cover, not a topic name. From those, it produces a lesson plan, a slide deck and a worksheet with answers.

Starting from spec points rather than a vague title matters more than it sounds. It keeps you in the habit the audit builds: every lesson traced back to a line in the specification. What you get is a first draft anchored to what the board lists, which is a far better starting point than a blank slide or a resource from a stranger's website that may be built for a different course.

The honest part: checking a draft when the subject is new to you

Any generated resource can be wrong, and if you are new to a subject you are the person least likely to notice. I would rather say that plainly than pretend otherwise. It does not mean avoiding these tools. It means changing how you use them.

• Do the worksheet yourself before you read the answers. If you disagree with an answer, settle it before the lesson.
• Check terminology against the specification's own wording. Mark schemes reward the board's language, so a slide that uses a near-synonym can quietly teach the wrong phrase.
• Check depth against the command words, the same way you did in the audit.
• Verify anything you are unsure of against the board's own material: the specification, specimen papers and examiners' reports. Not a random revision site.
• Ask your mentor or head of department to look at one pack early. Ten minutes from a specialist will catch more than an hour of you rereading.

There is a side benefit. Reviewing a pack critically, spec in hand, is good subject knowledge development in its own right. You learn the topic by checking it.

What it will not do

It does not know your class. It cannot see what they learned last year, which students need adapted materials, or how your department sequences the course. It will not replace your scheme of work, and it will not turn you into a specialist overnight.

What it does is remove the blank page and hand you something spec-referenced to check, adapt and make your own. For someone teaching an unfamiliar topic for the first time, that is usually where the time goes.

If you want to see what a pack looks like before signing up for anything, there is a free sample on the https://taskmanager.teacheradmin.com/ocr-h446-a-level-computer-science-lessons. If you would rather try it on your own spec points, new accounts get a 7-day trial with no card required, including three Lesson Studio packs.

Whatever you use, do the audit first. It is the twenty minutes that makes every other hour count.