Getting started

AI for Educators: A Practical Starting Guide

What AI is actually good at in a classroom, where it still fails, and the three jobs worth handing over first — for teachers told to "use AI".

October 31, 2026· LessonCraft Editorial5 min read
AI for Educators: A Practical Starting Guide

Most teachers have already tried AI once. They opened a chatbot, typed "lesson plan for fractions", got a wall of earnest text that would not survive contact with a real class, and closed the tab.

That result is not a verdict on AI in education. It is a verdict on the interface. A general chatbot asks you to be a prompt engineer at nine o'clock on a Sunday, which is not the job you were trained for and not the job you are paid for.

What follows is the version of AI for educators that survives a Tuesday morning: narrow tools, short forms, and a document at the end instead of a conversation.

Start with the paperwork, not the teaching

The useful split is not "AI teaches, the teacher supervises". It is:

  • AI drafts the artifact. A plan skeleton, a quiz, a set of feedback comments.
  • You supply the judgement. Whether the pacing fits this class, whether the question is fair, whether the comment sounds like you.

Drafting is where the hours go. A lesson plan written from scratch takes forty minutes; the same plan rebuilt from a decent draft takes eight to ten. That difference, repeated three times a week, is the whole return on investment.

Notice what stays out of scope: grading decisions, behaviour calls, parent conversations, anything a student would be hurt by if the model were wrong. Those are not drafting tasks. They are judgement tasks, and judgement stays with you.

What an AI teacher assistant is genuinely good at

Three categories hold up in practice.

Structure. Models are good at turning a topic into a timed sequence with objectives, activities, and an exit ticket. The structure is what takes you time to assemble, not the ideas.

Volume with variety. Ten multiple-choice questions at three difficulty levels, or six versions of the same feedback sentence so thirty students do not all receive identical comments.

First drafts of prose. The paragraph explaining a lab safety rule, the note home about a missed assignment, the rubric descriptor for "approaching standard". You will edit every one of them. Editing is still faster than staring at a blank page.

Where they are weak is equally predictable: anything requiring knowledge of your specific students, your school's history, or the unwritten rules of your department.

Where it still fails — and the three checks that catch it

Generated classroom material fails in repeatable ways. Three checks catch most of it before a student sees anything.

Check the standard, not just the label. A plan can say "aligned to CCSS.MATH.CONTENT.4.NF.A.1" while the activities quietly teach something else. Open your standards document, read the actual standard, and confirm the assessment measures it. This takes ninety seconds and is the single highest-value check.

Check the arithmetic and the reading level. Quiz questions occasionally have two defensible answers, or an answer key that disagrees with the question. Solve the questions yourself once. For reading level, read the first question aloud — if it needs a second pass, your students will need three.

Check the tone of feedback. Models default to praise-heavy comments ("Great effort! Keep practising!") that tell a student nothing. If a comment could be pasted onto any other student's paper, it is not feedback yet.

None of these checks require technical skill. They require the professional judgement you already apply to a colleague's worksheet.

A first week that does not collapse

Do not convert your whole workflow at once. Pick one artifact and run it for a week.

  1. Monday: choose the task you dread most — usually the weekly plan or the Friday quiz.
  2. Tuesday: generate a draft with your real constraints: grade, topic, duration, standard, and the two or three students who change how you teach the lesson.
  3. Wednesday: edit the draft against the three checks above. Note what you changed; that list is your prompt, written in your own language.
  4. Thursday: teach it. Keep the edits you made visible on the desk.
  5. Friday: decide whether the draft saved time. If it did not, try a different tool rather than a different prompt.

Most teachers find the plan tool pays back immediately and the grading tool takes longer, because feedback quality depends on a rubric you have to write first.

Choosing tools without wasting a term

The AI tools for teachers market is crowded with wrappers around the same handful of models. Judge them on four things:

  • Does it ask for your constraints? Grade level, duration, standard, class profile. A tool that only takes a topic is a chatbot with a form glued on.
  • Does it produce an artifact you can hand out? Print, .docx, or copy-as-markdown. If the output lives only in a chat window, you will spend the saved time reformatting it.
  • Does it show what it used? A model name and token count is not glamorous, but it tells you whether a cheap model is being resold at a premium.
  • What happens to student work? Anything you paste into a grading tool should be discarded after processing, not retained for training.

Price matters less than fit. A free tier that caps you at three generations a month is enough to test whether the structure suits your subject; a subscription is worth it only after the free tier has already saved you an evening.

Frequently asked questions

Is AI allowed in schools?

Policy varies by district and country, and it is usually about student use rather than teacher planning. Check your district's acceptable-use policy before pasting student work into any tool. Teacher-side planning with no student data attached is the lower-risk starting point.

Will students be able to tell the plan was drafted with AI?

They will notice if the activities do not fit the room. They will not notice a well-edited plan, because what they experience is your pacing and your questions. The tell is generic tasks, not the tool.

Do I need to learn prompting?

You need to learn to state constraints: grade, duration, standard, class profile, what went wrong last time. That is closer to writing a good brief for a colleague than to prompt engineering, and it transfers between tools.

Bottom line

AI for educators works when it is scoped to drafting and you keep the judgement. Pick one artifact, run the three checks, and measure the minutes you get back. If a tool cannot survive that test, it is not saving you anything — it is just moving the work to a different screen.

Put this into practice in the next ten minutes

The lesson plan generator does the drafting so you can spend your time on the judgement call.