AI staff policy assistant.

Staff ask the office and the principal the same policy questions every term. A well-scoped assistant answers the routine ones from your approved documents, shows its source, and sends everything else to a person.

Workflow5 min readUpdated 19 October 2026

Short answer

An AI staff policy assistant is a private search tool that answers school staff questions from the school’s own policies, procedures and current collective agreements, quoting the clause it relied on. In New Zealand schools it suits routine questions about processes, trips, leave applications and digital use. It should refuse individual employment advice and send grievances and safeguarding concerns straight to the principal.

  • Answers come only from approved school documents, with the policy name, section and review date shown.
  • Teacher terms change: the Primary Teachers’ Collective Agreement 2026–2028 was recently ratified.
  • Grievances, discipline and safeguarding questions go to a person, never to the assistant.
  • ERO found about seven in ten school leaders have no privacy policy for teacher AI use.

What a staff policy assistant does in a school

A staff policy assistant answers questions such as “What is the approval process for an overnight trip?” or “Can I photograph students on my own phone?” by quoting the school’s own documents. It is retrieval over a small, curated library, not a general chatbot, and it always shows the policy name, section and review date so staff can check the source.

Many schools publish policies through SchoolDocs, which says about 2,200 New Zealand schools use it, so the starting text is often already structured. This page is part of our guide to AI for education administration.

The workflow at a glance

Inputs
Approved policies and procedures, the staff handbook, current collective and individual agreements from the Ministry of Education site, a named owner for each document, and staff questions typed into Teams, Google Chat or a web page.
Systems
A document store in Microsoft 365 or Google Workspace, a private retrieval index, a business-tier model that does not train on inputs, school sign-in, and a question log.
Steps
Check the question against a refusal list, retrieve passages from approved documents only, answer in plain language with citations, say plainly when nothing supports an answer and name who to ask, then log the question, sources and feedback.
Human review
The principal or business manager approves the library and refusal list before launch, then samples 20 logged answers a week for the first term and fortnightly after that.
Outputs
Cited answers, referrals to a named person, and a monthly report of unanswered questions and stale documents.
Measures
Correct answers with correct citation in the sample, referral rate, documents past review date, and repeated questions about one policy.
Risks
Superseded agreements, answers that read as personal employment advice, HR material leaking into the index, and staff trusting an answer without opening the source.

Illustrative worked example: a 40-staff primary school

Illustrative example: a primary school with 28 teachers and 12 support staff. Assumptions: the office and principal field 30 policy or procedure questions a week in term time, each takes about 5 minutes once interruptions are counted, and 60% can be answered directly from documents. All figures are synthetic.

Item Assumption Weekly result
Questions answerable from documents 60% of 30 18 questions
Time saved per answered question 4 minutes, after staff check the source 72 minutes
Sample review in term 1 20 answers at 1.5 minutes 30 minutes
Net time returned in term 1 72 minus 30 about 40 minutes
Model usage 12,000 input and 600 output tokens per question 360,000 in, 18,000 out
Model fees Claude Sonnet 5.5 at US$2 and US$10 per million tokens about US$0.90

The model price is Anthropic’s API list price as listed on 19 October 2026. Model fees are negligible and the time returned is modest. The stronger case is consistency: staff stop relying on someone’s memory of a policy that changed last year.

Which NZ documents and rules shape the answers

Agreements change. Teacher pay, leave and allowances sit in collective and individual agreements that the Ministry publishes. Its page on primary teachers’ agreements notes the recently ratified PTCA 2026–2028 and newly promulgated IEAs. An index holding last year’s PDF will answer confidently and wrongly, so index one current version and print its date.

Grievance clocks keep running. The Ministry’s problem resolution page explains that a personal grievance must be raised within 90 days (12 months for sexual harassment). A message that reads like a complaint about treatment must go to the principal the same day, and the assistant must tell the staff member it has not raised anything on their behalf.

Boards have their own advice line. The NZ School Boards Association runs GovHub, which offers free governance and employment advice to state and state-integrated boards. The assistant can point managers there; it should not interpret contested clauses itself.

AI policies are thin. ERO’s 2026 Ready or not report found 45% of primary and 53% of secondary leaders use AI to generate policies, and about seven in ten lack a privacy and security policy for teacher AI use. Index only board-approved policies, never AI drafts. For the AI policy itself, use the Ministry’s generative AI guidance and our AI use policy template.

What stays with the principal and the board

Anything that decides something about a named person stays with a person.

  • Working out any individual’s entitlement, pay or leave balance.
  • Discipline, competency and complaints about colleagues.
  • Anything touching child safety, which goes to the person named in the child protection policy.
  • Interpreting ambiguous clauses, and approving what goes into the library.

Where it goes wrong and how to catch it

Most failures start in the document library, not the model.

Failure What it looks like Control
Stale source Quotes a superseded agreement One version per document, review dates shown, monthly stale report
Over-broad index Repeats a disciplinary letter from a shared drive Curated library only, never whole drives
Answering beyond sources Fills a gap with general or Australian practice Must cite a passage or refer to a named person
Student data typed in A teacher pastes a learner’s details Business tier with no training, a warning when names appear
Weak on te reo and tikanga Mistranslates or flattens kaupapa Māori policy Route those questions to the staff who hold that knowledge

The last row reflects the Ministry’s own warning that AI models are likely to be weak on mātauranga and te reo Māori.

How to start

Begin with a document inventory: every policy, its owner and its review date. Remove duplicates before indexing, write the refusal list, and pilot with five staff for three weeks against the accuracy bar in the FAQs. Our guides to building a searchable knowledge base and private AI search cover the build, and RAG development is the service when you want it built for you. Related workflows: parent enquiry triage and administrative document workflows.

Sources

  1. Generative AI, Ministry of Education, 2026
  2. Ready or not: How are schools responding to Artificial Intelligence? Summary, Education Review Office, 2026
  3. Primary teachers' collective and individual employment agreements, Ministry of Education, 15 July 2026
  4. Employment relationship problem resolution, Ministry of Education, 28 October 2025
  5. Te Whakarōpūtanga Kaitiaki Kura o Aotearoa, NZ School Boards Association, NZ School Boards Association, 2026
  6. SchoolDocs, LIGHTN Limited, 2026
  7. Claude API pricing, Anthropic, accessed 19 October 2026

Written by the Levy Street team in Wellington. Last updated 19 October 2026.

Questions people ask

Can a school just use ChatGPT, Copilot or Gemini as its staff policy assistant?

A small school can, if it uses a business or education tier that does not train on inputs and grounds the tool in a folder of approved documents. The catch is that general assistants fill gaps from general knowledge, which may be Australian or out of date. Test it with 30 real staff questions, including ones your documents do not answer, and check that it says so rather than guessing.

Should the assistant answer questions about pay and leave entitlements?

It can quote the relevant clause of the collective agreement and explain the process for applying, with the agreement’s date shown. It should not work out what a particular person is owed, because that depends on their contract, service history and payroll records. Those questions go to the principal or business manager, who can confirm the answer properly.

How do we keep answers current when a policy is reviewed?

Treat the document library as the product. Re-index whenever a policy is updated, show the review date in every answer, and run a monthly check for documents past their review date or superseded by a new agreement. If your policies are published through a service such as SchoolDocs, export the current versions on a schedule rather than copying them once.

Can we load staff files and HR letters so it can answer more questions?

No. Index a curated library of policies, procedures and agreements, not shared drives. Personnel files hold sensitive information about named staff, and an assistant that can read them can repeat them to the wrong person. Keep HR records in their existing system with their existing access controls, and point the assistant at the process for requesting information instead.

How accurate should it be before all staff can use it?

Set a bar before the pilot starts. A sensible one is 19 of 20 sampled answers correct with the right citation, and no answers on topics that should have been refused, over two consecutive weeks. If it misses that bar, fix the documents or narrow the scope before widening access.

Have something to build?

Tell us about the workflow. We will map where AI can change speed, margin or decision quality, and what it would take to run it in production.