A parent opens a school website with a question. They may be comparing schools, checking whether an application is still possible, looking for next term's dates, or trying to contact the right member of staff.
The website needs to help them move that task forward.
A strong visual identity can communicate a school's character, but its usefulness depends on the information and journeys behind the presentation. Parents need to understand what the school offers, whether it could suit their child, and what to do next.
Designing around those needs means making deliberate choices about content, navigation, forms, accessibility, and the people responsible for keeping the site accurate. This guide explains how to approach those choices, whether you are planning a new website or improving an existing one.
1. Begin with the questions families actually ask
Before deciding what the homepage should look like, investigate the questions your school receives and the tasks people struggle to complete.
Admissions staff can identify recurring enquiries. Reception teams may know which documents are difficult to find. Teachers and parent representatives can contribute useful perspectives, while conversations with families help test the assumptions behind those perspectives.
Review existing website searches, relevant enquiry themes, and available usage information. Ask parents to describe a recent task and show how they approached it, rather than only asking whether they like the current website.
Useful questions might include:
Which information did you need before deciding to contact the school?
What was unclear when you investigated admissions?
Which resources do you return to during the school year?
Have you had to call because the website did not answer your question?
What makes a form or document difficult to use on your usual device?
Treat the answers as evidence to examine. A school's priorities, audience, and operating arrangements should shape its design decisions.
2. Give prospective and current families clear routes
A prospective family needs to evaluate a school and understand the admissions process. A current family may need a calendar, uniform information, an approved notice, or access to an existing school system.
These journeys can share a website without giving every destination equal prominence on every page.
Provide a clear route into admissions and an equally understandable route to resources for current families. Use labels that describe what people will find, such as Admissions, Term Dates, Parent Resources, and Contact.
Consider guardians, carers, and other authorised family members as well as parents. The language and account arrangements should reflect the school's actual community and processes.
Also identify which information belongs on the public website and which belongs in an authenticated service. A public resource page can explain how to access a parent portal without exposing private records.
3. Make the homepage answer the first practical questions
The opening sections should establish the school's identity and the essential context a new visitor needs.
Explain the school's location, the ages or academic phases it serves, and its educational offering in clear language. Make it straightforward to explore the relevant academic information, understand admissions, or find contact details.
A welcoming headline can express character, but practical information should be close enough to help someone assess whether to continue.
For example, an illustrative homepage introduction could identify the school and its location, briefly describe its approach, and provide routes to academic phases and admissions. Current families could have a visible utility link to resources and dates.
Choose the main actions around the school's current situation. If applications are closed, explain the available next step accurately. If visits require an appointment, make the process clear. The website should reflect what the school can actually offer.
4. Organise navigation around recognisable tasks
Navigation works best when a visitor can make a reasonable prediction about where a link will lead.
Begin with a manageable set of clear destinations. A possible structure includes About the School, Academics, Admissions, School Life, Parent Resources, and Contact, with term dates or portal access available through a utility menu.
Adapt that structure to the school. A small primary school and a multi-campus institution may require different navigation and content depth.
Explain academic phase names where your audience may be unfamiliar with them. Include relevant year groups or age ranges approved by the school rather than assuming that every family understands the terminology.
Test the proposed structure with practical tasks: find the application requirements, check the next term's start date, or locate the admissions contact. Observe where people look first and where labels create uncertainty.
Search can help with a larger content collection, but it needs useful page titles, maintained content, and results that distinguish current information from archived material.
5. Help families assess suitability with specific information
Families need enough detail to form meaningful questions about whether a school could suit their child.
Academic pages should explain the relevant curriculum and phases, supported by information about the school day, learning environment, activities, and available support. Describe the provision the school actually offers and how families can discuss individual requirements with the appropriate staff.
Make practical matters discoverable too. Depending on the school, these could include transport, boarding, language of instruction, meals, after-school arrangements, or uniform information.
Where fees apply, publish school-approved information with the relevant year, what is included, and where to ask about additional costs or payment arrangements. Where availability changes, explain how to confirm the current position.
Specific, maintained information helps people evaluate fit. Claims such as exceptional facilities or outstanding support need an explanation of what families can expect, supported by accurate details and appropriate evidence.
6. Explain admissions before asking for an application
An admissions page should help someone prepare, not simply present a large form.
Describe who can apply, which entry points are available, the relevant dates, and what the process involves. Explain required documents and any steps that take place outside the website.
Where different phases have different requirements, separate them clearly. Date-sensitive information should identify the applicable intake or school year.
Set expectations for what happens after submission. Explain whether the school reviews the application, requests further information, arranges a visit, or follows another process. Only publish response expectations the admissions team has approved and can support.
Make the distinction between submitting an application and receiving an offer explicit. A confirmation message should describe the actual status of the request.
Provide an alternative contact route for people who need assistance or whose circumstances do not fit the standard process.
7. Match forms to the task and the information needed
A request for a prospectus, an enquiry about a visit, and a complete admissions application are different tasks. They do not necessarily need the same form or the same amount of information.
For a simple enquiry, ask for the information staff need to respond appropriately. For a longer application, explain what families should prepare before starting, group related questions, and make the next step understandable.
Use descriptive field labels, explain unfamiliar requirements, and identify errors in a way that helps the person correct them. Where a form has multiple steps, show progress and make reviewing earlier answers practical. W3C's forms guidance provides a useful reference for these interface decisions.
Design the failure and recovery experience as carefully as the successful submission. A family needs to know if a file did not upload or a submission did not reach the school.
If save-and-return is part of the scope, explain how it works and consider shared-device use. Do not imply that a draft has been securely stored or an application received unless the implemented service supports that claim.
8. Give current families dependable everyday resources
A parent returning for a specific piece of information should be able to find it without repeating the school's introductory journey.
Create a clear home for frequently used resources. The appropriate collection might include term dates, calendar events, uniform guidance, transport information, approved notices, policy documents, and links to established school systems.
Give downloadable files meaningful names and labels. Include the relevant year or version where it matters, and make it clear whether a document has been superseded.
Keep current announcements distinct from a historical news archive. An old event can remain useful as part of the school's story, but it should not appear to be an upcoming appointment.
Choose a dependable source for each piece of information. If dates appear in several places, assign responsibility for keeping those versions consistent or investigate whether the information can be managed centrally.
9. Make the important journeys work on a phone
Plan for families using the website in varied circumstances, including on smaller screens and connections that differ from the school's own office network.
Review the tasks themselves on a phone: opening the menu, reading requirements, following a calendar link, completing a form, and contacting the school.
Keep essential information available as readable page content where practical. A downloadable prospectus can offer additional detail, while the key admissions requirements and next steps remain available without opening a large document.
Use images at appropriate sizes, and assess the value and loading cost of video or other rich media. Important actions should remain usable while decorative content loads.
Test with realistic content and typical devices. A form that looks comfortable with short example names may behave differently with longer names, different address formats, or an error message that wraps across several lines.
10. Make content understandable and accessible
Parents differ in their access needs, familiarity with school terminology, language preferences, and confidence using online services.
Use descriptive headings and meaningful link text. Explain necessary terminology, keep instructions direct, and present important dates and requirements consistently. W3C's accessible writing tips offer additional guidance on organising and expressing web content.
Include accessibility in the project from the start. Important journeys should be reviewed for keyboard operation, readable contrast, text resizing, understandable focus movement, and compatibility with relevant assistive technology.
Provide text alternatives or captions appropriate to the content, rather than leaving essential information available only in an image or video.
If the school offers translated content, decide who checks it and how updates will be maintained across languages. A translation option is useful when the resulting information remains accurate and understandable.
Keep an accessible way to contact the school for help. Testing and improvements should consider the families who are most likely to encounter barriers.
11. Build trust through accurate, authentic content
Show the school as it is. Current, school-approved photographs, a clear explanation of the learning environment, and relevant information about staff and facilities can help families understand its character.
Use a defined approval process for photographs and personal information, reflecting the school's publication permissions and responsibilities. Avoid publishing details merely because they are available to the website team.
Check statements about results, qualifications, facilities, affiliations, and achievements before publication. Give dated information appropriate context so it is not mistaken for a current guarantee.
Testimonials should be authentic and approved for their intended use. A useful account of an experience can provide context; invented endorsements would undermine the trust the site is meant to support.
Families also need accurate contact details and a clear sense of who handles different enquiries. A carefully maintained contact page is part of the school's presentation, not an administrative afterthought.
12. Plan private admissions services separately from public pages
A public website, an admissions processing system, and a parent portal can be connected, but each has different responsibilities.
An interface demonstration may show application steps without providing a complete operational system. Before accepting real applications or documents, establish how information will be received, stored, accessed, reviewed, and handled by authorised staff.
The school and its implementation team should agree what information is needed, who is responsible for it, and what operational and data-handling requirements apply. Those decisions should guide the technical scope and review process.
If an existing platform already handles applications or parent records, a clearly explained link or suitable integration may be more appropriate than building another system. Verify the complete journey, including handoffs and confirmation messages.
The website should describe the service available today. A button labelled Parent Portal should lead to a functioning, appropriate destination or explain what families need to do to access the existing service.
13. Use visual design to support a calm, clear experience
The site should communicate the school's character while keeping practical information easy to read and use.
Choose typography, spacing, photography, and colour as a consistent system. Let important headings and actions stand out without making every section compete for attention.
Movement can support feedback or help a visitor understand a change, but consider the purpose of each effect. Admissions instructions and parent resources should remain readable and usable when motion is reduced.
Keep time-sensitive notices concise and relevant. Establish when an announcement should appear, who maintains it, and when it should be removed. Repeated interruptions can make routine tasks unnecessarily difficult.
A clear experience can still feel welcoming and distinctive. The design should help families understand the school and find the information they came for.
14. Give content an owner and a review schedule
A school website needs an operating plan after launch.
Identify who maintains admissions information, calendars, academic pages, news, contact details, and downloadable resources. Decide who approves changes and who covers an owner's absence.
Set review points around the school's actual calendar. Admissions dates, fees where applicable, term schedules, and staff information may change at different times.
Make the publishing process manageable for the people doing the work. Content controls, training, and written handover guidance should reflect their responsibilities and technical confidence.
Measure useful tasks and recurring problems. Depending on the website's purpose, you could review enquiries reaching the appropriate team, application completion problems, visits to key resources, or questions that repeatedly require a phone call.
Combine those observations with conversations with families and staff. Use the findings to prioritise specific improvements rather than treating traffic alone as evidence that the site meets parents' needs.
15. Explore the approach through the Westbridge prototype
Our Westbridge Academy case study demonstrates how a school website can connect an introduction to the school with academic information, parent resources, and a guided application interface.
The navigation provides routes for prospective families and existing members of the community. The application screens offer a way to examine the proposed admissions journey before connecting a real school's content and operational services.
Westbridge is a demonstration school identity. Its history, people, statistics, fees, testimonials, and events are illustrative, and the hosted prototype is not an operational admissions or parent-portal service. It provides a concrete starting point for discussing information structure and interface decisions, rather than evidence of admissions outcomes.
A practical checklist for your school website brief
Before commissioning the work, agree the questions that should shape the scope.
Which prospective and current-family tasks matter most?
What have families and staff told you about the current experience?
Which academic phases, locations, and admissions routes need clear explanations?
Who prepares and approves information about dates, fees, support, and school provision?
Which resources should be public, and which belong in an authenticated service?
Are enquiries, applications, visits, and portal access separate journeys?
What happens after each form is submitted, and who handles it?
Which existing school systems need to be linked or integrated?
What mobile, language, and accessibility needs should be considered?
Who approves photographs and other personal information before publication?
Who maintains the content after launch, and how will changes be reviewed?
Which tasks and feedback will help you assess whether the website is working?
Record unresolved questions alongside confirmed requirements. Our website brief guide provides a broader template for organising responsibilities, scope, content, budget, and approvals.
Make the next step clear for every family
A useful school website gives families practical support at the point where they need it. It helps prospective parents investigate suitability, understand admissions, and ask informed questions. It gives current families a dependable route to information and services.
That experience comes from clear content, considered design, functioning journeys, and an agreed process for keeping everything accurate.
Planning a school website? Apporal Digital can help organise the information, design the key journeys, and define what the public website and any connected services need to deliver. Tell us about your school project, including the people it should serve and the tasks it should make easier.
Further reading
The GOV.UK Service Manual offers a useful introduction to learning about users and their needs. Its examples concern government services; the school-specific examples and planning recommendations in this article are Apporal Digital's guidance.
