Most schools manage their student, staff and parent data in a management information system — SIMS, Arbor, Bromcom or ScholarPack. The MIS is the single source of truth for who is in the school, which classes they belong to, which year group they are in, and who their parents or guardians are. When a school introduces an AI chatbot for parent communication, the question of how users get into that system — and how they are removed when they leave — becomes a practical concern with real safeguarding implications.

Ask.School is an AI-powered parent communication platform for UK schools that integrates directly with the school MIS through Wonde, the data integration platform used by 98% of UK schools. This integration means schools do not need to create user accounts manually, assign groups by hand, or remember to deactivate accounts when students, staff or parents leave. The MIS remains the source of truth, and Ask.School stays in sync automatically.

This guide covers how the integration works, what data is synced, how it handles leavers and guardians, and what schools need to set it up. For schools that are still evaluating whether an AI chatbot is the right step, the procurement checklist for evaluating AI tools provides a structured framework for comparing options.

Why does manual user management create problems?

When a school sets up an AI chatbot without MIS integration, every user account must be created manually. Students need accounts. Staff need accounts. Parents and guardians need accounts. Each account needs to be placed in the correct groups — year groups, classes, form groups — so that the chatbot can tailor its responses and control who sees what.

For a primary school with 200 students, this might mean creating 200 student accounts, 30 staff accounts, and 300-400 parent accounts. Each one needs a name, an email address, and the correct group assignments. For a secondary school with 1,200 students, the numbers multiply accordingly.

The initial setup is time-consuming but manageable. The ongoing maintenance is where the problems compound.

New starters and leavers

Students join the school throughout the year, not just in September. Each new starter needs an account, the correct group assignments, and — if the school uses the chatbot for parent communication — their parents need accounts too. Students who leave need their accounts deactivated. So do their parents, unless they have other children still at the school.

Staff turnover follows a similar pattern. New teachers and support staff need accounts. Those who leave need deactivating. Supply teachers and temporary staff complicate things further.

Without MIS integration, someone in the school office must track every arrival and departure and make the corresponding changes in the chatbot system. In practice, this is the kind of task that gets missed. A student leaves at half term, but their account remains active. A parent’s child moves to a different school, but the parent still has access. A supply teacher who covered for one week still has a staff account months later.

Group changes

Students change classes. Year groups roll over every September. Form group allocations shift. Staff take on new teaching assignments. Each of these changes should be reflected in the chatbot system so that users see relevant information and access controls remain accurate.

Manually tracking group changes across hundreds or thousands of users is not practical. Schools that attempt it inevitably fall behind, and the chatbot’s user data drifts further from reality with each passing week.

The safeguarding dimension

The problems above are administrative inconveniences. The safeguarding dimension is what makes them serious.

When a student leaves a school, they should lose access to that school’s systems. This is a basic principle of access management and a practical safeguarding requirement. A former student who retains access to a school chatbot can still interact with it, potentially accessing information that should only be available to current students. More significantly, the school may still have obligations around monitoring and logging that become complicated when former users retain active accounts.

The same applies to parents and staff. A parent whose child has left the school should not retain access to parent-facing features. A member of staff who has left — particularly if they left under safeguarding-related circumstances — should have their access removed promptly and completely.

For a detailed look at how safeguarding monitoring works alongside AI tools, see the guide on how AI safeguarding monitoring works in schools.

What is Wonde and why do schools already use it?

Wonde is a data integration platform that connects school software to the school’s MIS. Rather than each software provider building its own direct integration with SIMS, Arbor, Bromcom and ScholarPack — each of which has its own data format and API — Wonde provides a single, standardised connection layer.

Schools approve which data each connected application can access, and Wonde handles the secure transfer. The connection is read-only: Wonde reads data from the MIS but never writes back to it. The school’s MIS data is never modified by any connected application.

Wonde is already used by the vast majority of UK schools for connecting various software tools — attendance systems, homework platforms, assessment tools, parent communication apps. For most schools, Wonde is already set up and approved by the school’s IT team or data protection officer. This means connecting Ask.School through Wonde does not require a new vendor relationship or a new data sharing agreement in most cases.

Which MIS systems does Wonde support?

Wonde supports all major UK school MIS systems:

MIS Market Position Wonde Support
SIMS (ESS) The most widely used MIS in UK schools Full support
Arbor Growing rapidly, particularly popular with academies and MATs Full support
Bromcom Strong presence in secondary schools and MATs Full support
ScholarPack Popular with primary schools Full support

If a school switches MIS — for example, migrating from SIMS to Arbor — the Wonde integration continues to work. Ask.School does not need to be reconfigured because Wonde abstracts the MIS-specific details. The school updates its Wonde connection, and Ask.School continues to receive data in the same format.

How does the Wonde integration work with Ask.School?

The integration follows a straightforward model: the school connects Ask.School to Wonde, selects which data to sync, and the platform keeps user accounts, group memberships and relationships in sync with the MIS automatically.

What data is synced?

The following data flows from the MIS through Wonde into Ask.School:

Data Type What Is Synced How It Is Used
Students Name, email address, year group, class, form group, UPN Creates student accounts, assigns to correct groups
Staff Name, email address, teaching assignments Creates staff accounts, assigns to relevant groups
Parents/Guardians Name, email address, linked students, relationship type Creates parent accounts, links to correct children
Classes Class name, assigned students and teachers Creates class groups in Ask.School
Year groups Year group name, assigned students Creates year groups in Ask.School
Form groups Form group name, assigned students Creates form groups in Ask.School

This covers the complete organisational structure of the school. Once the sync is running, Ask.School mirrors the MIS: every student is in the right year group, every teacher is linked to their classes, and every parent is connected to their children.

Schools can choose which data types to sync. A school that only wants to sync students and staff can disable parent/guardian sync. A school that does not use form groups can exclude them. The Wonde integration documentation covers all the configuration options.

How often does data sync?

Ask.School uses three synchronisation methods to keep data current:

Sync Type Frequency What It Does
Full sync Weekly Compares the entire MIS dataset with Ask.School and reconciles any differences. Catches anything that incremental syncs may have missed.
Incremental sync Multiple times daily Checks for changes since the last sync — new students, leavers, group changes, updated details — and applies them.
Webhook Real-time Wonde sends instant notifications when specific changes occur, such as a student being marked as a leaver. Ask.School processes these immediately.

The combination of these three methods means that Ask.School’s user data is never more than a few hours behind the MIS for routine changes, and critical changes like leaver status are processed in real time.

What happens during the first sync?

When a school first connects Ask.School to Wonde, a full sync runs immediately. This creates user accounts for all students, staff and parents/guardians in the MIS, assigns them to the correct groups, and establishes parent-student links.

For a primary school with 200 students, this typically completes within a few minutes. For a large secondary school or a MAT with multiple schools, it may take longer, but the process is fully automated — the school does not need to do anything beyond initiating the connection.

After the first sync, the school’s Ask.School instance is fully populated with users and groups that match the MIS exactly. No spreadsheets, no CSV imports, no manual account creation.

How does the integration handle leavers?

This is the most important aspect of MIS integration from a safeguarding perspective. When a student, staff member or parent leaves the school, their account should be deactivated promptly and completely. Manual processes for handling leavers are unreliable — they depend on someone remembering to update the chatbot system, which may not happen for days, weeks or at all.

Auto-deactivate leavers

Ask.School includes an auto-deactivate leavers feature that works directly with MIS data. When the MIS records a student as having left the school — which happens as part of the school’s normal administrative process — the change flows through Wonde to Ask.School, and the following actions happen automatically:

  1. The student’s account is deactivated. They can no longer log in or access the chatbot.
  2. Group memberships are removed. The student is removed from their year group, class and form group.
  3. Parent-student links are updated. If the leaving student was the only child a parent had at the school, the parent’s account is also deactivated. If the parent has other children still at the school, the link to the leaving student is removed but the parent’s account remains active.

This happens without any manual intervention. The school office does not need to remember to update Ask.School when processing a leaver — the MIS update triggers everything automatically.

Why does this matter for safeguarding?

Schools are required under Keeping Children Safe in Education (KCSIE) to maintain appropriate access controls for their digital systems. When a student or member of staff leaves, continued access to school systems represents a safeguarding gap.

The risk is most acute with staff leavers. A member of staff who has been dismissed or who has left under safeguarding-related circumstances must have all access revoked immediately. If the school’s chatbot system relies on manual account management, the deactivation depends on whoever manages the system being informed promptly and acting on that information. MIS integration removes this dependency — the MIS update is sufficient.

For students, the concern is slightly different but still relevant. A former student who retains access to the school chatbot may be able to access information intended only for current families. In a secondary school context, where the chatbot might provide information about school events, after-school activities or staff contact details, this access should be time-limited to the student’s period of attendance.

For a broader discussion of safeguarding requirements and AI tools, see the guide on how schools can meet KCSIE requirements when using AI tools.

What about mid-year leavers?

Students who leave mid-year — due to family relocation, managed moves, exclusions or other reasons — are handled in exactly the same way as end-of-year leavers. The moment the school updates the student’s record in the MIS to reflect their departure, the change propagates through Wonde to Ask.School.

This is particularly important for managed moves and exclusions, where the student’s departure may be sensitive and where continued access to school systems would be inappropriate. The automatic nature of the deactivation means there is no gap between the MIS update and the access removal.

How does guardian sync work?

Parent and guardian management is one of the most complex aspects of school user systems. A student may have two parents, a step-parent, a grandparent with parental responsibility, and a foster carer — each with different levels of involvement and different contact details. Maintaining this information manually is error-prone and time-consuming.

Relationship data from the MIS

The school’s MIS stores detailed relationship data for each student: who their parents and guardians are, what the relationship type is (mother, father, step-parent, grandparent, foster carer, guardian, other), and their contact details. This data is entered by the school as part of its standard admissions and data collection processes.

When Ask.School syncs through Wonde, it imports this relationship data in full. Each parent or guardian account is:

  • Created automatically with the correct name and email address
  • Linked to the correct student or students
  • Tagged with the relationship type from the MIS
  • Placed in the correct parent groups based on their children’s year groups and classes

Why relationship types matter

Relationship types enable the school to scope chatbot access correctly from the first day. A school might want to:

  • Send communications to all parents and guardians
  • Restrict certain information to parents with parental responsibility
  • Group parents by their children’s year group for targeted messaging
  • Ensure that both parents of a student receive the same information, even if they live at different addresses

Without MIS integration, building these relationships manually for every student in the school is a significant undertaking. With MIS integration, the relationships are established automatically based on data the school has already entered.

Multi-child families

Many parents have more than one child at the same school. The MIS stores these relationships, and Ask.School reflects them accurately. A parent with children in Year 3 and Year 6 will automatically be a member of both year group parent groups. They will see information relevant to both children without needing separate accounts.

When one child leaves the school (for example, the Year 6 child moving to secondary school), the parent’s link to that child is removed but their account remains active because they still have a child at the school. Only when their last child leaves is the parent’s account deactivated.

Parents with children at multiple schools in a MAT

For multi-academy trusts, the guardian sync handles the additional complexity of parents with children at different schools in the trust. Each school’s sync operates independently, so a parent with one child at the trust’s primary school and another at the trust’s secondary school will have appropriate access at both schools. For more on trust-wide deployment, see the guide on how to manage parent communications across a multi-academy trust.

What does year-end rollover look like with MIS integration?

September is the busiest time of year for school user management. Year groups roll over, new students join in Reception or Year 7, Year 6 and Year 11 students leave, class allocations change, and new staff arrive. Without MIS integration, a school would need to manually update hundreds or thousands of accounts to reflect the new academic year.

With MIS integration, the year-end rollover happens automatically. When the school updates its MIS for the new academic year — moving students into their new year groups, creating new class lists, adding new starters, marking leavers — those changes flow through Wonde into Ask.School within hours.

The school’s administrators do not need to do anything in Ask.School. The new Reception or Year 7 students appear as new accounts. Leavers are deactivated. Students are moved into their new year groups and classes. New parents are created and linked to their children. The entire process is handled by the same sync mechanisms that run throughout the year.

For large schools and MATs, this represents a significant time saving. What would otherwise be a major administrative exercise — potentially taking days of staff time across multiple systems — is reduced to the single task of updating the MIS, which the school has to do regardless.

How does MIS integration compare with CSV import?

Schools that do not want to use Wonde integration can still import users into Ask.School via CSV files. The importing users guide explains this process. However, there are significant differences between the two approaches:

Aspect MIS Integration (Wonde) CSV Import
Initial setup Connect once, sync runs automatically Prepare and upload a spreadsheet
Ongoing maintenance Automatic — changes in MIS flow through Manual — re-upload updated spreadsheet when data changes
Leaver handling Automatic deactivation when MIS is updated Manual — school must remember to update the CSV or deactivate accounts
Guardian relationships Imported automatically from MIS with relationship types Must be specified manually in the CSV
Group assignments Synced from MIS class, year and form group data Must be specified in CSV columns
Year-end rollover Automatic when MIS is updated for the new year New CSV required for the new academic year
Error risk Low — data comes directly from the authoritative source Higher — manual data entry introduces errors
Time investment Minutes to set up, no ongoing time required Hours for initial setup, ongoing time for updates

CSV import is a reasonable option for schools that have a specific reason not to use Wonde — for example, schools using a niche MIS that Wonde does not support, or schools that want to import a specific subset of users that does not match their MIS structure. For most schools, MIS integration through Wonde is the more efficient and more reliable option.

What about data protection?

MIS integration involves transferring personal data — names, email addresses, year group assignments, parent-child relationships — from the MIS through Wonde to Ask.School. Schools rightly want to understand the data protection implications.

Read-only access

The most important point is that the integration is read-only. Ask.School reads data from the MIS through Wonde. It never writes data back. The school’s MIS data cannot be modified, deleted or corrupted by the integration. Wonde enforces this at a technical level — the API connections do not include write permissions.

Data stays in the UK

All data processed through the Wonde integration is stored in the UK. Ask.School hosts all data on UK-based, ISO 27001-certified infrastructure. No personal data is transferred outside the UK at any point in the sync process.

Schools process student and parent data under their existing lawful basis — typically legitimate interests or public task for maintained schools, and legitimate interests or contractual necessity for academies and independent schools. The Wonde integration does not change the lawful basis; it simply provides a more efficient mechanism for transferring data that the school already holds and is already entitled to process.

Schools should ensure their privacy notice covers the use of third-party platforms for communication purposes. Most school privacy notices already include this, but it is worth checking.

DPIA considerations

Schools that are completing a Data Protection Impact Assessment for their use of Ask.School should include the Wonde integration in the scope of the assessment. The key considerations are:

  • What data is transferred (names, emails, group memberships, relationships)
  • Who has access to the data in Ask.School (school administrators, and users to the extent they see their own information)
  • How long data is retained (aligned with the school’s data retention policy)
  • How data is secured (encryption in transit and at rest, UK hosting, ISO 27001)
  • How leavers’ data is handled (automatic deactivation, with data deletion following the school’s retention schedule)

For a step-by-step guide to completing a DPIA for AI tools in schools, see the practical DPIA guide. For a broader discussion of data protection and AI, see the guide on data protection and AI in schools.

How do schools set up the Wonde integration?

The setup process requires two pieces of information and takes approximately five minutes. Schools that already use Wonde for other software integrations will find the process familiar.

What is needed

Item Where to Find It Purpose
Wonde School ID Wonde dashboard or from the school’s IT team Identifies the school in the Wonde system
Wonde API token Generated in the Wonde dashboard Authenticates the connection between Ask.School and Wonde

Step-by-step setup

  1. Log into the Ask.School dashboard and navigate to the Integrations section.
  2. Enter the Wonde School ID and API token in the provided fields.
  3. Select which data to sync. Toggle on or off: students, staff, parents/guardians, classes, year groups, form groups. Most schools enable all options.
  4. Run the first sync. Click the sync button. Ask.School connects to Wonde, retrieves the school’s data, and creates user accounts, groups and relationships.
  5. Review the results. The dashboard shows a summary of what was created: number of students, staff, parents, and groups. Spot-check a few accounts to confirm the data looks correct.

The first sync runs immediately. After that, incremental syncs run automatically throughout the day, and a full sync runs weekly. No further action is needed unless the school wants to change which data types are synced.

For schools not yet using Wonde

Schools that do not yet have a Wonde account can set one up at wonde.com. The process involves registering the school, connecting Wonde to the school’s MIS (which typically requires the MIS administrator to approve the connection), and then granting access to Ask.School. Wonde provides setup guides for each MIS.

For schools that prefer not to use Wonde at all, Ask.School supports CSV user import and manual user management as alternatives.

What should schools consider before connecting?

Data accuracy in the MIS

The integration is only as good as the data in the MIS. If the school’s MIS has outdated email addresses, incorrect year group assignments, or missing parent relationships, those inaccuracies will be reflected in Ask.School.

Before connecting, schools should review the quality of their MIS data, particularly:

  • Parent email addresses: Are they current? Many schools find that a percentage of parent email addresses in the MIS are outdated.
  • Leaver status: Are students who have left correctly marked as leavers? Any students incorrectly still on roll will be synced as active users.
  • Relationship records: Are parent-student relationships complete? A parent who is not linked to their child in the MIS will not be linked in Ask.School either.

This is a useful exercise regardless of the chatbot integration — accurate MIS data benefits every system the school uses.

Staff communication

Let relevant staff know that the integration is being connected and what it means. Office staff should understand that user accounts are now managed through the MIS, not manually in Ask.School. Safeguarding leads should understand that the auto-deactivate leavers feature will handle account removal for leavers automatically.

Choosing what to sync

Not every school needs to sync every data type. Schools should consider which user groups will actually use the chatbot:

  • Students and parents only: If the chatbot is primarily for parent communication, syncing students and parents may be sufficient.
  • Staff, students and parents: If staff also use the chatbot for internal purposes, include staff in the sync.
  • Groups: Syncing classes, year groups and form groups is recommended if the school wants to send targeted communications or restrict certain chatbot features to specific groups.

The configuration can be changed at any time, so schools can start with a subset and expand later.

How does MIS integration support the overall setup process?

For schools setting up Ask.School for the first time, MIS integration fits into the broader onboarding process as the user management step. The setup guide covers the full process — account creation, document uploading, calendar connection, branding, safeguarding preferences and website embedding. MIS integration adds the user management step, which slots in after account creation and before or alongside document uploading.

With MIS integration handling user management, the setup timeline changes:

Step Without MIS Integration With MIS Integration
Create user accounts Hours (manual entry for all users) 5 minutes (connect Wonde, run sync)
Assign groups Hours (manual group assignment) Automatic (synced from MIS)
Handle first leaver Manual (remember to deactivate) Automatic (MIS triggers deactivation)
Year-end rollover Hours (update all accounts manually) Automatic (MIS updates flow through)
Ongoing maintenance Continuous (track every change manually) None (sync runs automatically)

The time saving is most significant for larger schools and MATs, but even a small primary school benefits from eliminating the ongoing maintenance burden.

Summary

Connecting the school MIS to Ask.School through Wonde replaces manual user management with an automated, reliable process that stays in sync with the school’s authoritative data source. Students, staff and parents are created, updated and deactivated based on MIS data, eliminating the administrative overhead and safeguarding risk of manual account management.

The integration is read-only, UK-hosted, and built on a platform that 98% of UK schools already use. Setup takes five minutes. Ongoing maintenance takes zero minutes. And when a student, staff member or parent leaves the school, their access is revoked automatically — no forgotten accounts, no manual intervention, no safeguarding gaps.

Connect your MIS in minutes. Start your free trial at ask.school/register.