Choosing a school parent app: what to test

Start with the problem the app should solve

Write down the three or four outcomes that matter most. Examples include reducing missed trip responses, replacing duplicate data entry, making school notices easier to find or improving the handling of routine absence reports. Give each outcome a current baseline and an owner. Otherwise a busy launch can look successful without improving the work.

List existing systems that already provide some of the proposed functions. A new app may be useful as a single entry point, but it may also introduce another place for records to disagree. Decide which services will be retained, replaced or connected before considering a long-term contract.

Test complete family journeys

Build fictional household records that reflect the school's circumstances. Include siblings in different year groups, two households, an adult without a smartphone, a carer using a screen reader and a family joining after term begins. Ask prospective providers to demonstrate each journey from invitation through completion.

Task	What a successful test shows
First activation	The intended adult can get access without avoidable office intervention
Add a second child	The account clearly distinguishes each child's tasks
Report an absence	The office receives a usable report without automatically overwriting the register
Change a contact detail	The request reaches the approved verification process
Respond to a trip	The response, pupil and information version remain traceable
Lose a phone	Recovery is practical and old access can be controlled

Ask staff to perform the tasks themselves. Record where the demonstration required hidden configuration, administrator intervention or an additional paid module.

Check permissions before visual polish

Find out how adult-child relationships are created and changed. Can the school apply restrictions without relying on staff to remember them at every send? How does the app handle a change of carer or a request for separate access? A single family label may be too simple for real households.

Review staff roles with the same care. A teacher who posts a class update should not automatically need access to payment information or every pupil's contact record. Demonstrate what each role can see, change, export and delete. Test with a normal user account, not only the administrator account used in sales presentations.

Check accessibility in actual use

Ask for accessibility information, then carry out practical tasks. Can a user navigate with a keyboard, enlarge text without losing buttons and understand an error without relying on colour? Does the app work with relevant assistive technology? Are documents attached by the school readable, or do they undermine otherwise accessible screens?

Compare the app with its browser alternative where one exists. If a household shares a device or cannot install an application, access should not depend on a workaround nobody has tested. Include the office-assisted process in the evaluation and ask families with different access needs to give structured feedback using fictional data.

Understand what integration really includes

A claim that an app integrates with the MIS does not specify which fields move, in which direction or how quickly. Request a field-level description and the rules for conflicts, deleted records, new starters and leavers. Establish whether the connection requires another contract or intermediary charge.

Test a contact correction, a pupil moving class and an adult's access being removed. Ask where failures appear and who investigates them. The office needs a visible exception process; an integration that fails quietly can be worse than a manual process with a reliable check. Read school system integration for a fuller specification.

Compare the operating cost and exit

Include setup, training, messages, modules, support, renewals and export assistance in the comparison. Clarify whether historical messages and responses can be exported in a useful form, with dates, attachments and relationships intact. A downloadable list of names is not a complete archive of school communication.

Review privacy and contractual arrangements with the appropriate leads before sharing live records. Ask what the supplier does with data beyond delivering the school service, how incidents are reported and what happens when the contract ends. Product descriptions alone cannot settle those questions.

Pilot against the original outcomes

Run a bounded pilot with agreed success measures and a way to stop safely. Track completed tasks, support requests, delivery failures and staff administration time. Gather feedback from the office and families, including those who needed assistance.

Use the results to decide whether to launch, adjust the configuration or reconsider the purchase. A successful app leaves fewer fragmented processes behind. It should be possible to explain precisely which old channels and duplicate records will close after the transition.