A practical school website content audit
A content audit finds information that is wrong, duplicated, difficult to use or missing an owner. The most useful output is a prioritised correction list.
Explore the complete school technology reference library. Filter by topic or find guidance for your role.
Looking for materials, equipment or classroom activities? Explore the school resource library.
A content audit finds information that is wrong, duplicated, difficult to use or missing an owner. The most useful output is a prioritised correction list.
Start with the task a pupil wants to do more independently, then match technology, teaching and support to that specific barrier.
An IT strategy should explain the problems the school needs to solve, the order of work and how it will fund and sustain the result. Start with evidence about the current service.
A good technology purchase solves a defined problem and leaves the school with a service it can operate. The specification, evaluation and handover deserve as much attention as the price.
A cashless dinner system connects families, the school office and the catering team. Its design should make the lunchtime routine clearer while protecting pupils whose circumstances require extra support.
A parent app should simplify the jobs families and staff already do. Evaluate it through complete tasks, from receiving an invitation to changing a contact detail, instead of counting features in a brochure.
The most useful display is the one pupils can see and teachers can operate confidently with the resources they already use.
Connect purchasing decisions with real lessons, the space available and the people who will maintain and share the equipment.
Choose resources that help pupils learn and teachers teach, with a clear progression from one activity to the next.
Trip administration works best when booking, consent, medical updates and payment are separate records with clear relationships. A payment alone should never be used as the sole evidence that every other step is complete.
Use technology only where it contributes to a clear purpose, with responsive adult interaction and the wider early years routine kept central.
A school website succeeds when families can complete everyday tasks and staff can keep essential information accurate. Begin with those needs before choosing a design.
A new system changes people's work as well as the technology. Plan the transition around real tasks, protect essential services and decide how you will handle exceptions before launch.
Accessibility is part of every page and task. Begin with essential family journeys, test beyond automated tools and make corrections part of normal publishing.
A successful migration preserves useful information and working journeys. Inventory existing addresses, test replacements and keep website changes separate from unrelated services.
Strong authentication should protect important accounts without leaving staff dependent on improvised workarounds when a phone or token is unavailable.
ParentPay is a school payment service. The options a family sees depend on the school and its setup. This guide explains the main account concepts and how to resolve common questions without sharing private account information.
Trust-wide IT needs a common direction and a clear understanding of each school's circumstances. Standardise where it improves the service, and manage exceptions deliberately.
Choose a limited, useful task, keep a responsible human in charge and evaluate the whole workflow before expanding AI use.
The purchase price is only one part of an IT budget. Compare the full period of use, show when cash is needed and keep the assumptions visible.
Prepare the decisions and contact routes before an incident makes the normal systems and working relationships harder to use.
A useful wireless network must work with a full classroom, across the actual school site and under the same safeguards as wired access.
Attendance software should support accurate registration and timely human follow-up. Its value comes from reliable records and clear responsibilities, not simply from producing a percentage on a dashboard.
A backup is useful when the school can recover the right information and return an important service to safe operation.
Choose connectivity around the school day, the systems you depend on and what will happen when the main connection fails.
A booking system needs to keep places, attendance, payments and collection information aligned. Design those relationships first, especially where a club is busy, families book recurring sessions or providers share responsibility.
Focus on the controls that keep school services usable and sensitive information protected, with clear evidence and ownership.
A school data migration is complete when staff can use accurate records in the new system and explain what happened to the old ones. Copying files or matching a headline record count is only part of that work.
A retention schedule should tell staff what to keep, why, for how long and what to do when that period ends. It needs to cover the places records actually exist, including exports and copies held by suppliers.
Replace equipment for a clear reason, spread future costs and make sure school information does not leave with retired hardware.
Device management connects what the school buys with how that equipment is configured, supported, protected and eventually retired.
Digital governance makes sure technology decisions have an owner, risks receive attention and the school can sustain what it buys. It connects technical work to leadership responsibility.
Choose the display format around what people need to notice, learn or do, then make updates and review part of the routine.
A useful inventory tells the school what it owns or controls, where it is, what it supports and what action is needed next.
Filtering and monitoring work only when the school understands their coverage, their limitations and who acts on the information they produce.
A school management information system holds core records and supports daily administration. Evaluate it through the work it must make reliable: admissions, contacts, attendance, reporting and controlled connections to other services.
Good school communication depends on clear ownership and reliable contact details as much as the application sending the message. Give each type of communication a purpose, a channel and a response route.
A payment platform succeeds when families can pay confidently and the office can explain every balance. Start with those two outcomes, then test how the proposed system handles the difficult cases.
Reduce avoidable printing while keeping the paper resources that teaching, accessibility and family communication genuinely need.
A reliable joining and leaving process connects HR decisions, line managers, IT support and system owners. It gives staff the access they need and removes or changes that access at the right time.
An integration is an agreement about how records move and which system is trusted. Define that agreement in plain language before connecting the school MIS, parent app, payment service or learning platform.
Good navigation reflects the questions visitors bring to the website. Build a simple structure, offer more than one useful route and test it with realistic tasks.
Use the correct guidance for your school type, then give every applicable publication item an owner, a location and a review trigger. A generic checklist cannot certify compliance.
Website security includes the domain, administrator accounts, public content and recovery process. A secure hosting package cannot substitute for school-side ownership.
Digital exclusion is not a fixed label attached to a household. A family may lose connectivity, share a phone, need another format or struggle with one particular task. Design support around the barrier and the job to be done.
Start with the visitor's question, answer it early and make the next step explicit. Good school website writing reduces uncertainty for families and repeated work for staff.