January INSET can easily become a collision between ambition and fatigue. Staff return needing clarity, not another abstract presentation about the future of AI. If this session is going to land well, it should focus on practical adoption: one shared structure, one low-risk starting point, and one realistic expectation for what staff will try in the first half-term.
That matters because most schools are no longer asking whether AI exists or whether pupils know about it. The more useful question is how teachers, heads of department and support teams can use it safely in day-to-day work. If your school is still deciding on core protocols, it may help to pair this workshop with a lighter governance review such as an annual acceptable use policy refresh. But the INSET itself should not become a policy marathon.
A strong January workshop looks different from a policy sprint or a generic AI awareness talk. It gives staff something to do, not just something to hear. It also avoids the trap of treating every department as identical. Science, languages, pastoral teams and office staff all need different examples, but they can still work within one shared framework.
The simplest model is a 90-minute session built around a common low-risk task, followed by differentiated pathways. This keeps whole-school consistency while respecting confidence levels. If you want a companion structure for follow-up routines, this three-micro-routines workshop model can support what happens after the initial session.
For most schools, the free-tier tool stack needs to be boring in the best sense: available, stable and easy to explain. In the UK and Sweden, that usually means schools are working with a mix of browser-based AI assistants and the tools already sitting inside Google or Microsoft ecosystems. Access will vary by local procurement and age restrictions, so the workshop should be framed around categories rather than a single branded solution.
In practice, staff can usually work with a mainstream chatbot for drafting and summarising, their existing productivity suite for document handling, and a shared prompt sheet approved by leaders. If your school uses Google Workspace, it is worth checking current admin controls before the session; this Google Classroom and Workspace update guide is useful for that groundwork. The same principle applies in Microsoft environments, where permissions and rollout settings matter more than the headline features.
Before anyone opens a tool, set four non-negotiables. First, no personal data. Staff should not paste pupil names, safeguarding details, contact information or identifiable assessment records into public tools. Secondly, no confidential staff information. Thirdly, all outputs must be checked by a human before use. Finally, AI should support professional judgement, not replace it.
These rules need to be visible in the room, printed on tables and repeated during facilitation. That may sound basic, but it creates the confidence reluctant staff need. It also protects the school from the common mistake of treating AI as a shortcut before data rules are clear. If leaders need a quick pre-INSET audit, this privacy checklist offers a sensible starting point.
The run sheet should feel brisk and achievable. In the opening ten minutes, explain the aim: every department leaves with one agreed workflow it can trial safely this half-term. Then spend ten minutes on safeguards and minimum-data rules. After that, move into one shared low-risk task that every adult in the room can complete, regardless of role.
The middle of the session is where differentiation matters. Give staff two pathways: a confidence-building route for reluctant users and a workflow-design route for confident users. Then bring departments together for breakouts, where they adapt what they have done to subject, pastoral or admin contexts. The final section should produce tangible artefacts and a simple implementation plan.
The best opening activity is something every department already does and nobody sees as high risk. A strong example is turning a short block of generic curriculum text into three versions: a parent-friendly summary, a pupil-friendly explanation and a staff briefing note. No names are involved, the source material is school-owned, and the output can be checked quickly.
A maths department might use a unit overview on algebra. Humanities might use a topic description for migration. Pastoral teams might use a generic attendance reminder. Admin teams could use a routine letter template. The point is not the brilliance of the output. The point is that everyone experiences the same simple pattern: give clear input, ask for a defined transformation, then edit the response critically.
For tech-reluctant staff, success should be deliberately modest. Ask them to complete two or three micro-wins. One could be rewriting a worksheet instruction for a lower reading age. Another could be generating five quiz questions from a short teacher-written paragraph. A third could be turning meeting notes into a tidy action list.
These tasks matter because they are small enough to feel safe. They also build the habit of checking quality rather than accepting the first answer. Staff who are nervous about AI often become more open once they see it as a drafting assistant rather than a mysterious machine. If needed, give them pre-written prompts on paper so they are not starting from a blank screen.
For more confident staff, the challenge should be workflow design rather than tool exploration. Instead of asking, “What can this do?”, ask, “Where in your weekly routine is there repeatable friction?” That might be lesson adaptation, parent communication drafting, revision resource creation or meeting summary production.
Here, staff can map a fuller process: source material, prompt pattern, output format, quality check and storage location. A head of department, for instance, might build a simple routine for turning curriculum plans into retrieval questions and homework options. A pastoral leader might design a workflow for converting anonymised case themes into parent communication drafts. This is also the right moment to discuss audit trails and consistency, especially if teams are already using AI for reports or feedback drafting. This comparison of report-writing assistants can help frame those conversations carefully.
Ready to Revolutionise Your Teaching Experience?
Discover the power of Automated Education by joining out community of educators who are reclaiming their time whilst enriching their classrooms. With our intuitive platform, you can automate administrative tasks, personalise student learning, and engage with your class like never before.
Don’t let administrative tasks overshadow your passion for teaching. Sign up today and transform your educational environment with Automated Education.
Once both pathways have had time to work, departments should regroup and choose use cases that fit their real workload. Classroom teams might focus on explanation, differentiation and quiz generation. Pastoral teams might work on communication drafting, assembly outlines or anonymised trend summaries. Admin teams may prefer document redrafting, FAQ creation or event communication.
Subject-specific examples make the session feel credible. In English, staff could turn an extract into scaffolded comprehension questions at three levels. In science, they might create a practical safety reminder in simpler language. In languages, they could generate short model dialogues with controlled vocabulary. In art, they might ask for critique sentence stems. The key is to keep all examples low-risk and rooted in materials staff already use.
By the end of the workshop, every department should have produced the same small set of artefacts. This is what turns an interesting INSET into a consistent whole-school model. Each team should leave with one agreed workflow, one shared prompt bank, one list of approved use cases and one short note on what data must never be entered.
This does not need to be polished. A one-page department sheet is enough. In fact, keeping it light increases the chance that staff will actually use it. Schools that over-design at this stage often create paperwork rather than change.
The final ten minutes should not be a showcase of clever outputs. Instead, each department should answer three questions: what will we trial, who will try it first and how will we know it helped? That keeps the focus on implementation rather than enthusiasm.
A good agreed workflow is narrow and repeatable. “Use AI better” is not a workflow. “Use our department prompt template to create three differentiated explanations from existing lesson notes” is a workflow. The narrower the first step, the easier it is to embed by half-term. If school leaders also want to review the bigger picture of changing practice, this overview of what actually changed in schools during 2025 offers helpful context.
January adoption works best when the first half-term is structured. In week one, departments run the agreed workflow once. In week two, they share one example and one caution. In week three, they refine the prompt or process. In week four, leaders gather brief feedback. By half-term, each team decides whether to continue, adapt or stop.
This approach prevents AI from becoming a one-off INSET memory. It also avoids burdening staff with extra evidence demands. A simple shared log, a five-minute check-in during line management, or one example at a department meeting is usually enough. If you want a broader rollout model, this minimum viable AI toolkit guide aligns well with a 30-day implementation cycle.
Leaders should evaluate adoption by looking for usefulness, safety and consistency, not volume. The questions are straightforward. Did the workflow save time? Did it improve clarity or quality? Were privacy rules followed? Are staff using a shared method rather than inventing risky shortcuts?
Brief qualitative evidence is often enough. A department might report that a prompt bank reduced planning time for retrieval tasks, but that outputs needed tighter subject vocabulary. Another might find that parent-letter drafting was faster, but still needed careful tone editing. That kind of feedback is far more valuable than counting log-ins.
To make the session easy to run, prepare a simple appendix pack. Include sample prompts for summarising, redrafting and question generation. Add facilitation notes with model wording for the privacy briefing. Provide printable checklists for staff on what they can enter, what they must not enter and how to quality-check outputs.
The most effective January INSET sessions are rarely the flashiest. They work because they give every department a safe first step, enough structure to build confidence and a realistic path from the training room to the classroom. That is what turns AI from a talking point into an organised school routine.
Here’s to a calm, useful and consistent start to the term.
The Automated Education Team
Microsoft Build 2026 brought a fresh wave of Copilot announcements, but …
Summer term is often the last realistic window for school leaders and AI …
Schools do not need a whole-school AI rollout to learn what works. In many …
Once the papers are marked, many departments want feedback that is sharper …
Primary assessment week can feel intense, especially when SATs and spring …
Exam week often creates pressure to do more, faster, with less time to …
Many school AI rules still rely on vague disclosures such as “I only used …
AI voice tools for modern foreign languages have improved sharply by 2026, …
Spring assessment season puts pressure on teachers, pupils and families to …
Jaanuar on õige hetk viia kooli AI-koolitus üldiselt teadlikkuselt praktilise ja madala riskiga …
Januari är rätt tidpunkt att flytta skolans AI-fortbildning från bred medvetenhet till praktisk …
Tammikuu on oikea hetki siirtää koulun AI-koulutus yleisestä tietoisuudesta käytännölliseen, …