Every school website serves two audiences: Ofsted inspectors and parents. Meeting compliance requirements is essential, but there is an opportunity to make the same website work much harder for families too. Ask.School is an AI-powered parent communication platform for UK schools that answers the questions parents actually ask, 24 hours a day. Understanding what those questions are — and why most school websites fail to answer them quickly — is the starting point for better parent communication.

Ask.School has drawn on data from hundreds of school websites, query logs from AI chatbots deployed across UK schools, and published research from the Department for Education. The sections below map the twenty most common things parents search for, explains why this information can be difficult to surface on traditional school websites, and sets out what schools can do about it.

For a broader look at reducing the volume of routine enquiries reaching the school office, see our guide on how to reduce school office phone calls.

What are the most common things parents search for on school websites?

The answer is remarkably consistent across primary schools, secondary schools, special schools and academies. The same twenty or so queries account for the vast majority of parent searches, regardless of the type of school or its location. These are not complex, unusual or unreasonable requests. They are the basic operational information that every family needs to get through the school week.

Here are the top twenty, ranked by frequency:

Rank Parent query Typical document or source
1 Term dates Term dates page or academic calendar
2 School uniform Uniform policy or parent handbook
3 School times / start and finish times Website or parent handbook
4 Lunch menu / school meals Catering provider or kitchen menu
5 How to report an absence Attendance policy or absence form
6 INSET days / training days Term dates page or newsletter
7 After-school clubs Clubs list or enrichment timetable
8 Parents’ evening dates Calendar or newsletter
9 School contact details / phone number Contact page
10 Admissions / how to apply Admissions policy or local authority page
11 School office opening hours Contact page or parent handbook
12 PE days and kit requirements Year group letter or PE policy
13 SEND provision / SEN support SEND information report or local offer
14 Breakfast club / wraparound care Wraparound care page or booking system
15 Trips and visits Letters home or trip-specific page
16 School policies Policies page
17 Safeguarding / who to contact Safeguarding page or designated safeguarding lead details
18 School map / directions / parking Contact page or location details
19 PTA / Friends of the school PTA page or separate PTA website
20 Homework expectations Homework policy or year group page

Three things stand out from this list. First, the information already exists somewhere in every school. None of these queries require new content to be created. Second, the queries are almost entirely operational rather than strategic. Parents are not searching for the school’s vision statement or its latest Ofsted report. They want to know what time the gate opens and whether it is PE on Thursday. Third, the information changes frequently enough that parents cannot simply memorise it. Lunch menus rotate, clubs change each half-term, trip details are specific to dates, and PE days can vary by year group.

Why do school websites fail to surface this information?

School websites are not badly designed because the people building them are incompetent. They are badly designed because the incentives are misaligned. Schools are required by the Department for Education’s statutory guidance on what maintained schools must publish online to make certain information available on their website. Academies have similar requirements under their funding agreements. These requirements include governance structures, financial information, curriculum details, pupil premium strategy, SEND information reports, and policies.

None of this is what parents search for most frequently. But because it is what schools are inspected on, it gets the prime real estate. The homepage links to the things the school must publish, not the things parents most need to find.

The navigation problem

Most school websites use a navigation structure that mirrors the school’s organisational chart. There is a section for parents, a section for pupils, a section for staff, a section about the school, and a section for policies. Within the parents’ section, there might be subsections for communications, payments, uniform, catering, and transport.

This structure makes sense to the person who built the website. It does not make sense to a parent who needs to know whether Year 4 have PE on Wednesday.

The parent’s mental model is not “I need to navigate to Parents > School Life > PE Kit.” The parent’s mental model is “Does my child need a PE kit tomorrow?” These are fundamentally different ways of looking for information, and most school websites are built for the former, not the latter.

The search functionality problem

Some school websites have a search bar. Most of the time, it does not work well. School website search functions tend to be basic keyword matching tools that search page titles and body text. If a parent searches for “PE days,” the search might return the PE policy (a multi-page document about the school’s approach to physical education) rather than the simple one-line answer the parent needs: “Year 4 has PE on Wednesday and Friday.”

Even when the search returns the right page, parents then need to read through the document to find the specific piece of information they need. For a time-pressed parent checking their phone at 7:30am, this is too much friction. They give up and call the school office instead.

The currency problem

School websites are often out of date. Not because nobody cares, but because keeping a website current is a significant administrative task that sits on top of an already overwhelming workload. The clubs list from last term is still showing. The lunch menu has not been updated since half-term. The calendar has events from the wrong academic year.

Parents learn quickly that they cannot always trust the website, which undermines even the content that is current and accurate. Once a parent discovers that one piece of information on the website is wrong, they default to phoning the office for everything.

The format problem

Much of the information parents need is locked inside PDF documents. The uniform policy is a PDF. The term dates are a PDF. The parent handbook is a PDF. These documents are not easily searchable, are difficult to read on a mobile phone, and are often several pages long when the parent needs a single piece of information from somewhere in the middle.

A parent searching for “can my child wear trainers?” does not want to download a twelve-page uniform policy. They want a direct answer.

How does this affect the school office?

The practical consequence of poor website findability is a high volume of routine phone calls and emails to the school office. As explored in detail in our post on how AI chatbots reduce school office phone calls, the typical primary school office receives thirty or more phone calls per day, and the majority of these are about the same small set of routine queries listed in the table above.

Each call takes, on average, two to four minutes. That includes the time to answer the phone, listen to the question, find the answer, relay it to the parent, and deal with any follow-up. For a school receiving thirty routine calls per day, that is one to two hours of staff time spent answering questions that already have documented answers.

Over the course of a school year, this adds up to hundreds of hours. Hours that front office staff cannot spend on admissions processing, attendance follow-up, safeguarding administration, or any of the other tasks that demand attention.

The problem is worse at certain pinch points in the school year:

  • September: New parents unfamiliar with routines, uniform queries, school times, club sign-ups
  • January: Term dates, INSET days, new term clubs and activities
  • Parents’ evening weeks: Booking queries, timing, childcare, location
  • End of summer term: Reports, transition information, September start dates, new uniform for the next year
  • Any time the school sends a letter: Calls from parents who lost the letter, did not receive it, or need clarification

At these pinch points, call volume can double or triple, placing significant strain on office staff who are already managing a demanding workload.

What does the research say about how parents use school websites?

The Department for Education’s guidance on generative AI in education recognises that AI can be most effective when it reduces administrative burden and frees up staff time for higher-value tasks. While this guidance focuses primarily on teaching and learning, the principle applies equally to school administration.

Research from Ofsted’s inspection framework also indirectly supports the case for better parent communication. Ofsted inspectors routinely survey parents through Parent View, and the questions cover whether parents feel well-informed about their child’s progress, whether the school communicates effectively, and whether parents know how to raise concerns. Schools that communicate well with parents tend to score better on these measures. Schools that rely on parents navigating a complex website to find basic information tend to score less well.

The Parentkind Annual Parent Survey consistently finds that parents’ top priorities are practical information about their child’s school day, not strategic information about the school’s vision or performance data. Parents want to know what is happening this week, not what the school’s five-year plan looks like.

This aligns with what query data from school chatbots confirms: the most-asked questions are operational, immediate, and specific.

What do parents search for at different times of day?

One of the most revealing insights from AI chatbot query data is that parent search behaviour varies significantly throughout the day. Understanding these patterns helps schools think about when and how information needs to be accessible.

Time of day Typical queries Context
6:30am – 8:00am Uniform, PE days, school times, breakfast club availability Parents getting children ready for school
8:00am – 9:00am Absence reporting, late arrival procedures, contact details Parents dealing with illness or unexpected situations
9:00am – 3:00pm Admissions, SEND provision, policies, trip details Parents researching during working hours
3:00pm – 4:30pm After-school clubs, collection arrangements, school times Parents planning pick-up
4:30pm – 7:00pm Homework expectations, parents’ evening details, calendar events Parents helping with homework and planning ahead
7:00pm – 10:00pm Term dates, holiday planning, uniform shopping, admissions Parents with time to plan
Weekends Admissions, school comparison, SEND provision, wraparound care Families actively researching schools

Two things matter here. First, a significant proportion of parent searches happen outside school office hours. A parent checking uniform requirements at 7:00am or researching admissions at 8:00pm cannot phone the school office. They are entirely dependent on the website, and if the website does not give them what they need, they will either call the next morning or, in the case of prospective parents, move on to the next school.

Second, the type of query changes throughout the day. Morning queries are urgent and practical. Daytime queries are more research-oriented. Evening queries are about planning. A school’s information architecture should account for this, but most do not. For more on this pattern and what schools can do about it, see our guide on how to give parents answers outside school hours.

How should schools think about the parent search journey?

It helps to map the parent journey for each of the common queries. Taking “school uniform” as an example:

The current journey (typical school website)

  1. Parent goes to school website
  2. Looks for a “Parents” or “Information” section in the navigation
  3. Finds a “Uniform” link (if it exists) or a “Policies” link
  4. Clicks through to a uniform policy PDF
  5. Downloads the PDF (or tries to read it on a mobile screen)
  6. Searches through the document for the specific item they need
  7. Finds the answer, or gives up and calls the school

This journey has six or seven steps. Each step is a point where the parent might give up.

The ideal journey

  1. Parent goes to school website (or opens a chatbot)
  2. Types or asks: “What colour shoes should my child wear?”
  3. Gets a direct answer: “Black shoes. No trainers or boots. Full details are in the uniform policy.”

This journey has two steps. The parent gets a direct, specific answer without downloading a document or navigating a menu structure.

Mapping the journey for all twenty queries

Parent query Current journey (steps) Ideal journey (steps) Friction reduction
Term dates Homepage → Calendar or Dates page → Read Ask → Answer High
Uniform Parents → Uniform → Download PDF → Search PDF Ask → Answer Very high
School times About → School day → Read page Ask → Answer Medium
Lunch menu Parents → Catering → PDF or external link Ask → Answer High
Report absence Parents → Attendance → Absence procedure → Follow steps Ask → Answer + link to form Very high
INSET days Calendar or Dates page → Scan list Ask → Answer Medium
After-school clubs Parents → Clubs → Find current list Ask → Answer High
Parents’ evening Calendar → Find event → Read details Ask → Answer Medium
Contact details Contact page → Read Ask → Answer Low
Admissions Admissions → Read policy or external link Ask → Answer + link to apply High
Office hours Contact page → Read Ask → Answer Low
PE days Year group page or letter → Find info Ask → Answer Very high
SEND provision SEND → SEND Information Report → Read long document Ask → Answer Very high
Breakfast club Parents → Wraparound → Read details Ask → Answer Medium
Trips and visits Letters or Calendar → Find specific trip Ask → Answer High
Policies Policies page → Find specific policy → Download PDF Ask → Answer High
Safeguarding contact Safeguarding page → Read Ask → Answer Medium
Directions / parking Contact → Location details Ask → Answer Low
PTA Community → PTA page Ask → Answer Low
Homework expectations Curriculum or Year group → Homework → Read Ask → Answer High

The pattern is clear. For almost every common query, the current journey involves multiple navigation steps and often requires the parent to open and search through a document. The ideal journey reduces this to a single question and a direct answer.

What about parents who do not speak English as a first language?

For schools with diverse communities, the findability problem is compounded by language barriers. A parent who speaks limited English faces an even more challenging journey through a school website. Navigation menus, policy documents, and PDF downloads are all in English. Even if the information exists, it is not accessible to all parents.

This is a genuine equity issue. The DfE’s guidance on parental engagement recognises that schools should make reasonable efforts to communicate with all parents, including those who speak other languages.

An AI chatbot that supports multiple languages can make a significant difference here. A parent can ask a question in their own language and receive an answer in that language, drawn from the school’s English-language documents. This does not replace the need for translated materials where required, but it provides an immediate, practical way to help parents access routine information.

How does an AI chatbot trained on school documents help?

An AI chatbot that has been trained on a school’s own documents, policies, calendar, and knowledge base can answer the vast majority of the queries in the table above instantly and accurately. The document management and calendar guides explain how schools set this up. The chatbot does not generate information from general knowledge. It draws exclusively from the school’s approved sources, ensuring that answers are specific to that school and verified by the school.

Here is how this works for each of the top query categories:

Term dates and INSET days

The chatbot reads the school’s published term dates (whether as a webpage, a PDF, or a calendar feed) and can answer questions like:

  • “When does the summer term start?”
  • “What are the INSET days this year?”
  • “When is half-term in February?”
  • “What date does school break up for Christmas?”

These are among the most-asked questions on any school website, and they are among the simplest for an AI chatbot to answer accurately.

Uniform

Uniform queries are particularly well-suited to a chatbot because parents usually have a specific question rather than wanting to read the entire policy:

  • “Can my child wear trainers?”
  • “Does the school have a summer uniform?”
  • “Where can I buy the school jumper?”
  • “Are earrings allowed?”

The chatbot draws from the uniform policy and provides a direct answer to the specific question, with a link to the full policy for parents who want more detail.

Absence reporting

This is a common source of confusion for parents, especially at the start of the school year or when a child is ill for the first time. Parents need to know:

  • How to report an absence (phone, app, email, form)
  • What time to report by
  • Whether a reason is needed
  • What happens with extended absences

A chatbot can provide this procedural information instantly, including links to the relevant online form or phone number. This is especially valuable early in the morning when the school office may not yet be staffed but parents need to report an absence before the school day begins.

Lunch menus and dietary requirements

Lunch menu queries are frequent and time-sensitive. Parents want to know what is on the menu today or this week, and whether the school caters for specific dietary requirements. If the school’s menu is available as a document or webpage, the chatbot can answer:

  • “What is for lunch on Thursday?”
  • “Is there a vegetarian option?”
  • “Does the school cater for allergies?”
  • “How much does a school dinner cost?”

After-school clubs and wraparound care

Clubs change every half-term in many schools, and parents often struggle to keep track of what is available, when, and how to sign up. A chatbot can answer:

  • “What clubs are available for Year 3?”
  • “When does football club run?”
  • “How do I sign up for breakfast club?”
  • “What time does after-school club finish?”

SEND provision

SEND queries are particularly important and particularly underserved by most school websites. The SEND Information Report, which all schools must publish, is often a lengthy document that parents find difficult to navigate. Parents of children with additional needs often have specific questions:

  • “Does the school have a SENCO?”
  • “What support is available for children with dyslexia?”
  • “How does the school support children with autism?”
  • “What is the school’s approach to EHCPs?”

A chatbot can draw from the SEND Information Report and the school’s SEND policy to provide direct, specific answers. This is valuable not only for current parents but also for prospective parents who are researching schools for a child with additional needs.

Admissions

For prospective parents, the admissions process is often confusing. Different schools have different timescales, different criteria, and different application routes. A chatbot can answer:

  • “How do I apply for a place in Reception?”
  • “What are the admissions criteria?”
  • “When is the deadline for applications?”
  • “Does the school have a waiting list?”
  • “Can I arrange a visit?”

This is valuable because prospective parents often research schools in the evening or at weekends, when the school office is closed. A chatbot that can answer admissions queries at 9pm on a Saturday evening could make the difference between a parent adding the school to their application and moving on to the next option.

Safeguarding

Parents searching for safeguarding information are often in a situation where they need guidance quickly. They want to know who the designated safeguarding lead is, how to raise a concern, and what the school’s policy is. A chatbot can provide this information clearly and immediately, while also directing the parent to appropriate external resources such as the NSPCC helpline if the concern is about a child outside the school context.

Schools looking for an AI chatbot that handles parent queries with built-in safeguarding guardrails can see how Ask.School approaches this at ask.school/safeguarding. The chat interface guide shows how parents interact with the chatbot, and the useful links feature allows schools to surface key resources alongside chatbot answers.

What about information that changes frequently?

One legitimate concern is how a chatbot handles information that changes regularly. Lunch menus change weekly. Clubs change each half-term. Calendar events change throughout the year. Trip details are specific to individual year groups and dates.

The answer depends on how the chatbot is set up. A well-configured chatbot should be connected to live data sources where possible (such as a calendar feed) and should have its document library updated whenever significant information changes. This is not fundamentally different from keeping a website up to date, but it is simpler because the chatbot does not require page layouts, navigation structures, or formatting. Uploading an updated clubs list is faster than redesigning a webpage.

Schools should establish a simple process for keeping the chatbot’s knowledge base current:

  1. Calendar feed: Connect the school’s calendar so that dates, events, and INSET days are always current
  2. Termly review: At the start of each term, upload updated clubs lists, menus, and timetables
  3. Ad hoc updates: When something changes (a trip date moves, a policy is updated), upload the new document
  4. Annual review: At the start of each academic year, review and refresh all documents

This is less work than maintaining a comprehensive, navigable website, because the chatbot does not require the information to be structured in any particular way. A simple document or even a brief note is enough for the chatbot to answer questions from.

How does this compare to improving the school website?

Some schools respond to the findability problem by redesigning their website. This can help, but it has limitations.

A website redesign typically costs between two thousand and ten thousand pounds and takes several months. The result is a website that looks better and may have improved navigation, but it still relies on parents knowing where to look and being willing to click through multiple pages to find what they need.

More fundamentally, a website redesign does not solve the format problem. Information is still presented as pages, documents, and PDFs. Parents still need to find the right page and read through the content to extract the specific piece of information they need.

A well-designed website and an AI chatbot are not mutually exclusive. The best approach is both: a clear, well-organised website for parents who prefer to browse, and a chatbot for parents who prefer to ask. But if a school has to choose where to invest its limited time and budget, the chatbot typically delivers faster results because it works with existing content rather than requiring a complete restructuring.

Approach Cost Time to implement Handles all 20 queries Works outside office hours Multilingual
Website redesign High (£2,000–£10,000+) Months Partially (improves navigation but parents still search) Yes (but no interactivity) Requires separate translation
Improved search function Low to medium Weeks Partially (better keyword matching) Yes (but limited accuracy) No
FAQ page Low Days Partially (only covers anticipated questions) Yes (but static) Requires separate translation
AI chatbot trained on school documents Low to medium Days Yes (answers from the full document library) Yes (interactive, 24/7) Yes (supports multiple languages)

What should schools do next?

For schools that recognise the findability challenge described above, here is a practical approach to improving how parents access information.

Step 1: Audit the current state

Before making changes, schools should understand their starting position:

  • Review website analytics: Which pages do parents visit most? Which search terms are they using? Where do they drop off? Most website providers offer basic analytics that reveal these patterns.
  • Log phone queries: Ask office staff to note the nature of every phone call for one week. Categorise them as routine (information that exists on the website), procedural (how to do something), or complex (requires a conversation). Most schools find that 60 to 80 per cent of calls are routine.
  • Test the parent journey: Try to answer each of the twenty queries in the table above using only the school website. Time how long each one takes. Ask a parent governor to do the same and compare notes.

Step 2: Fix the quick wins

Some improvements can be made immediately without any new tools or investment:

  • Add term dates to the homepage: Not as a link to a PDF, but as plain text on the homepage itself
  • Create a “Quick Answers” section: A prominent section on the homepage with direct answers to the ten most common queries
  • Replace PDFs with web pages: Convert the most-searched documents (uniform, term dates, school meals) from PDFs into web pages that are mobile-friendly and searchable
  • Improve the contact page: Make sure the absence reporting procedure, office hours, and key contact numbers are immediately visible without scrolling

Step 3: Consider an AI chatbot

For schools that want to go further, an AI chatbot provides the most comprehensive solution to the findability problem. As discussed in our guide on what a school website chatbot should actually do, not all chatbots are the same. Schools should look for:

  • Training on school-specific documents: The chatbot should answer from the school’s own policies, handbooks, and calendar, not from generic information — the creating chatbots guide walks through how this is set up
  • Safeguarding guardrails: The chatbot should detect safeguarding concerns and respond appropriately, meeting the requirements of KCSIE and the Generative AI Product Safety Standards
  • Data protection compliance: The chatbot should comply with UK GDPR and the Data Protection Act 2018, with data hosted in the UK and never used for model training
  • Ease of setup: Schools should not need technical expertise or weeks of implementation time
  • Multilingual support: For schools with diverse communities, the chatbot should support queries in multiple languages

Step 4: Measure the impact

After implementing changes, schools should track progress:

  • Phone call volume: Are routine calls decreasing? Most schools see a reduction within the first few weeks.
  • Chatbot usage: How many queries is the chatbot handling per day? What are the most common questions? Are there queries the chatbot cannot answer that indicate gaps in the document library?
  • Parent satisfaction: Ask parents (through Parent View, surveys, or informal feedback) whether they find it easier to get the information they need.
  • Staff time: Are office staff reporting that they have more time for other tasks?

Step 5: Iterate and improve

The query data from a chatbot is itself a valuable resource. It tells the school exactly what parents want to know, which means the school can:

  • Fill gaps: If parents are frequently asking a question the chatbot cannot answer, the school knows it needs to create or upload that content
  • Identify confusion: If parents are asking the same question in many different ways, it may indicate that the school’s communication on that topic is unclear
  • Spot seasonal patterns: Query data reveals when certain topics peak, allowing the school to proactively communicate before the rush

What about Multi-Academy Trusts?

For Multi-Academy Trusts, the findability problem is multiplied across every school in the trust. Each school has its own website, its own documents, its own term dates, and its own uniform policy. Parents with children at different schools within the same trust may need to navigate entirely different website structures to find equivalent information.

A trust-wide approach to parent communication can help. This might include:

  • Standardised website templates: Ensuring all schools in the trust have a consistent navigation structure and information architecture
  • Shared AI chatbot platform: Deploying chatbots across all schools from a single platform, with each chatbot trained on the individual school’s documents but managed centrally
  • Centralised document management: Making it easier for trust-level administrators to ensure all school websites and chatbot knowledge bases are up to date

For more on managing parent communications at trust level, see our post on managing parent communications across a Multi-Academy Trust.

What does this mean for prospective parents?

The findability problem has a direct impact on admissions. Prospective parents researching schools typically do so in the evening and at weekends, when the school office is closed. They visit the school website, and their experience of that website shapes their perception of the school.

A website where term dates are easy to find, the admissions process is clearly explained, SEND provision is well-documented, and questions can be answered by a chatbot creates a positive impression. A website where basic information is buried in menus and locked in PDF documents creates a negative one.

For schools in competitive admissions environments, this matters. A parent choosing between two schools may well choose the one where they could find the information they needed without making a phone call. As we explore in our guide on how to give parents answers outside school hours, the ability to answer parent queries at 9pm on a Sunday evening is not a luxury. For many families, it is when they do their research.

What about data protection?

Any tool that handles parent queries must comply with UK GDPR and the Data Protection Act 2018. Schools should ensure that:

  • The chatbot does not collect or store personal data beyond what is necessary for the conversation
  • Parent conversations are not used to train AI models
  • Data is hosted within the UK on appropriately certified infrastructure
  • A Data Protection Impact Assessment (DPIA) has been completed before deployment
  • The school’s privacy notice is updated to reflect the use of an AI chatbot

For a detailed guide on data protection considerations for AI tools in schools, see our post on data protection and AI: what schools need to get right.

What are the key takeaways?

Parents search for the same twenty or so things on every school website: term dates, uniform, school times, lunch menus, absence reporting, clubs, SEND provision, and admissions. Most school websites make this information harder to find than it should be, resulting in high volumes of routine phone calls to the school office.

The solution is not to expect parents to become better at navigating websites. The solution is to present information in a way that matches how parents actually look for it: specific questions with direct answers, available at any time of day, in any language.

An AI chatbot trained on a school’s own documents provides the most efficient way to bridge this gap. It works with existing content, requires minimal setup, and reduces the administrative burden on office staff from the first week of deployment.

The data is clear. Schools know what parents search for. The question is whether schools make that information easy to find.

See how Ask.School answers parent questions 24/7 at ask.school.