Product guides
How a parent experiences school management, ERP, and SIS
How parents experience school management software through status, fees, attendance, assessment, documents, messages, privacy, and support.
Families experience the workflow
A parent does not experience a database. A parent experiences an application status, a fee, a receipt, an attendance update, a report, a document, or a message. The useful question is whether the information is understandable, current enough for its purpose, and clearly owned by the school.
Map the family journey from the event that starts it to the action or answer the parent needs. Include language, accessibility, relationship, approval, and correction requirements.
Make status and next action clear
Words such as submitted, under review, approved, published, paid, overdue, absent, and archived should have defined meanings. Families should know whether to wait, provide information, make a payment, or contact the school.
- What can this family relationship see?
- Which information is approved for release?
- How is a correction requested?
- Where is help available?
- What happens when an account or relationship changes?
Protect trust
GOV.UK guidance recommends data protection by design, minimum necessary data, access control, security, supplier responsibility, incident notification, and data return or deletion. Test separated guardians, siblings, staff notes, unpublished results, documents, and changed contact details.
Do not promise instant updates, complete visibility, or universal language behavior without testing the actual workflow and content.
Listen after launch
Review support questions, failed actions, family confusion, access exceptions, correction time, and the original outcome at 30, 60, and 90 days. Use the feedback to improve the workflow, message, training, or support route.
Make the next step specific
Use this guidance to improve one bounded part of how a parent experiences school management software. Name the person who owns the decision, the record or workflow affected, the evidence needed, and the date for review. Keep the test small enough for operators to complete and specific enough for a later audit. Record the result, the next action, and the condition that would make the team revisit the decision.
