Free-SchoolAI

A free prompt library for school staff.

655 jobs for the people who write the drafts: teachers, leaders, SENCOs, early years, exams, cover, the office and the board. Fill in your school once, find the job, copy the prompt. No sign-in, no subscription.

  1. 1Find the job. Search, browse a shelf, or start from a moment in the school year.
  2. 2Fill in what you know. Your school is saved in this browser. Anything you leave blank, the model is told to ask about, not invent.
  3. 3Run it, then check it. Use a model your school allows. A person with the right role reads the draft before it goes anywhere.
Install on your staff intranetFree download for your IT team, set up once for your school.
Fill in your school onceThen every prompt you copy starts filled in. It stays in this browser.

Saved in this browser only. This page sends none of it anywhere. No pupil or staff names here.

Any day

Every job

655 jobs

  • School improvement

    Long-range school plan

    Produce a 3 to 5 year plan with vision, priorities, success measures, owners and a yearly phasing. Keep it usable by governors, not a brochure.

    Fill in first
  • Governance

    Academy conversion briefing

    Set out arguments for and against conversion or joining a trust for THIS school. Separate facts, values and risks. Do not recommend a vote.

    Fill in first
  • Systems and compliance

    Accessibility plan draft

    Draft an Accessibility Plan covering curriculum, physical environment and information, with timescales and owners. Flag statutory bits the user must check.

    Have ready: DfE Equality Act advice for schools

    Fill in first
  • School improvement

    White paper response note

    Map the school's current work against the latest schools white paper themes the user names. Do not invent policy that was not provided.

    Have ready: The 2026 schools white paper

    Fill in first
  • Systems and complianceRecord

    Admissions appeal statement

    Draft a school statement for an independent appeal panel. Stick to published admission arrangements and facts supplied. No pressure language.

    Have ready: School admission appeals code

    Fill in first
  • Pupil supportRecord

    Allergy healthcare plan

    Draft an individual healthcare plan for a pupil with an allergy, in the format the school uses: allergens, signs of a reaction, emergency steps, who holds and checks the medication, and what happens on trips and at lunch. Medical detail only from the plan and the family. Never invent a dose, device or contact.

    Have ready: DfE allergy safety in schools (2026); DfE supporting pupils with medical conditions; The pupil's plan

    Fill in first
  • Day to day

    Assembly script

    Write an assembly script for the age range given, tied to the school's values if supplied. Keep it short enough to deliver.

    Fill in first
  • Systems and complianceRecord

    Attendance code explainer

    Suggest which attendance code may apply and why, in plain English. Say this is not legal advice and the school must check current DfE attendance guidance.

    Have ready: DfE attendance guidance (July 2026)

    Fill in first
  • School improvement

    Whole-school attendance plan

    Draft a whole-school attendance plan from the data the user pastes. Name barriers, actions, owners and review points. No fake benchmarks.

    Have ready: DfE attendance guidance (July 2026)

    Fill in first
  • Communication

    Attendance message

    Write a parent-facing attendance message in the channel asked for (text, email, letter, call script). Warm and clear. No shame.

    Have ready: DfE attendance guidance (July 2026)

    Fill in first
  • Pupil supportRecord

    Pupil attendance plan

    Draft a plan for one pupil or family from the facts given. Practical, kind, reviewable.

    Have ready: DfE attendance guidance (July 2026)

    Fill in first
  • Day to day

    Meeting notes from a transcript

    The model cannot hear audio. Paste a transcript from Teams, Meet or a speech-to-text tool. Turn it into notes: decisions, actions with owners and dates, and open questions. Do not attribute words to anyone the transcript does not name.

    Fill in first
  • School improvement

    Audit follow-up plan

    Turn a RAG audit or visit note into an action plan. Keep the original findings visible. Do not upgrade a Red to Green.

    Fill in first
  • Staff and personnel

    Behaviour examples bank

    Turn the school's behaviour policy into concrete examples of expected conduct by age, for staff to use consistently.

    Have ready: DfE behaviour in schools; Your school's own policy

    Fill in first
  • Pupil supportRecord

    Behaviour incident note

    Structure an incident record from facts given. Do not invent witnesses, times or sanctions. Use factual language.

    Have ready: DfE behaviour in schools; Your school's own policy

    Fill in first
  • Pupil supportRecord

    Pupil behaviour support plan

    Draft a support plan, not a punishment sheet. Include triggers, adult responses, teaching of the skill, and review.

    Have ready: DfE behaviour in schools; SEND code of practice and your SEND policy

    Fill in first
  • Communication

    Funding bid draft

    Write a bid from the funder's criteria and the school's evidence. Mark every claim that still needs a number.

    Fill in first
  • School improvement

    Book look feedback

    Write developmental feedback from the scrutiny notes provided. Separate what was seen from what is inferred.

    Fill in first
  • Systems and compliance

    School business case

    Draft a business case: problem, options, cost, benefit, risk, recommendation. Do not invent costs.

    Fill in first
  • School improvement

    Impact case study

    Write a case study from the evidence supplied. Before/after only if the user gave numbers.

    Fill in first
  • Staff and personnel

    Change plan

    Build a change plan: why, who is affected, what will be different by when, how staff are involved, how you will know.

    Fill in first

Take the whole library with you, for a local model or the staff shared drive.

What every prompt does

Every prompt carries the same rules. UK English. England unless you say Wales or Northern Ireland. No invented pupils, staff, data, quotes, grades, citations, medical details or costs: the model writes [NEED: ...] or asks instead. If the context is thin, it asks up to five sharp questions before it drafts. It ends by listing its assumptions, what you still need to check, and what should not go into a public model.

50 jobs are marked Record. They can become a pupil, staff or legal record: safeguarding concerns, references, investigations, health plans, exclusion papers. Those prompts open with a stop line, and they belong in a model your school controls, never a public chat.

For a lesson, scheme or exam job, paste the programme of study or the specification. The prompt is told not to invent a topic list or a paper. For anything statutory, paste the guidance named on the job. The prompt will not pretend to know this year’s edition.

These prompts write drafts. They do not hold a duty, sit on a board, or sign a reference.

Where to run them

A model on a machine you control. Ollama or LM Studio on a school laptop keeps everything on the device. It is the right home for the jobs marked Record.

The assistant your school already licenses. Many schools have an assistant inside their Microsoft or Google accounts. Ask your data protection officer what it may be used for before you paste anything about a pupil or a colleague.

A public chat, for public work. Lesson resources, letters with no names, a newsletter, a plan from published data. Never a record, never casework.

The downloads under the library give you every prompt as one text file and the catalogue as a spreadsheet, for a local model, a staff drive or your own tools.

Put it on your school intranet

The whole library also comes as a plain web page your IT team can host: no server code, no sign-in, no calls to anywhere else. They set your school’s details once, choose the AI tool staff should use, hide the shelves you do not need and add your own prompts. Every member of staff then gets prompts that start filled in.

Install on your staff intranet

Worked example

A fictional school, and the drafts it used

Samplefold Community Primary School is not real. Marrowgate is not a place. There is no URN and no inspection grade. The figures were invented so you can see what to paste, and what a draft looks like when the context is filled in.

Maintained community primary, England, ages 3 to 11. 312 on roll, plus 28 in nursery. Head: Priya Sen. Attendance lead: Daniel Okoye. Both invented.

Full year 2025/26, invented register: attendance 93.1%. Persistent absence 18.4%, 57 pupils. Severe absence 1.6%, 5 pupils. Pupil premium persistent absence 27%. Year 5 lowest, at 91.0%. Term-time leave in Year 2 and Year 5. Lates heaviest on Monday.

The job was Whole-school attendance plan. The context block was the school card. The draft names Daniel on the daily late check, Priya on the leave letter, and a bus log for ten days. It does not invent a trust target. It does not name the five pupils in severe absence.

School card, plan, parent email, curriculum note, Monday staff note →

CC BY 4.0. Use them. Change them. Keep the credit. The plain-text jobs are also on GitHub.