Getting teachers on board with a new ERP

Schools rarely fail to adopt software because the software is bad. They fail because a new system arrives as an extra task, with a one-day training and no clear date on which the old way stops. Teachers, already stretched, quietly go back to what they know.

Change management sounds like corporate jargon, but in a school it is simply this: making the new way easier than the old way, and then making the old way go away.

Resistance is usually rational. Common concerns include:

• "This will add to my workload."
• "I am not confident with technology and do not want to look slow."
• "Last time we tried a system, it was abandoned after three months."
• "Who will help me when it breaks at 8:55 in the morning?"

Naming these concerns in the first meeting, and answering each one, builds more trust than any feature demonstration.

Do not launch every module to every teacher at once. Pick the daily tasks where the benefit is most visible to staff, typically attendance and marks entry, and make those work flawlessly first. Once teachers feel the time savings, the appetite for the next module grows on its own.

A phased rollout might look like this:

1. Weeks 1 to 2: attendance for all classes
2. Weeks 3 to 6: marks entry and internal assessments
3. Following term: communication, homework and other modules

In every department or grade level, identify one or two colleagues who are comfortable with the system and respected by their peers. Give them early access and a little extra training. Teachers ask their neighbours before they ask the helpdesk, and a friendly champion on the same corridor resolves most problems in a minute.

A single long training day is quickly forgotten. Better:

• Short sessions of 30 to 45 minutes, focused on one task
• Separate sessions for class teachers, subject teachers, the front office and the accounts team
• A one-page quick-start guide per role, with screenshots
• Recorded walkthroughs that staff can replay when they need them

Always train on the real school's data, not a demo, so the screens look familiar.

This is the single most important rule. If teachers are asked to fill the register and enter attendance online, the online version will be treated as optional. Announce a firm date after which the paper process stops, and make sure leadership means it. Keep the period of overlap short and clearly bounded.

In the first weeks, assign a named contact for questions and publish when they are available. Fast answers in the early days decide whether a small frustration becomes a lasting opinion of the system. Log the questions asked, because repeated questions point to a training gap or a confusing screen.

When the principal opens the attendance dashboard in the morning meeting, or asks for a report that only exists in the system, staff notice. Leaders who keep asking for information through old channels signal that the new system is optional.

Track a few simple indicators weekly:

• Percentage of classes with attendance marked by a set time
• Percentage of marks entered before the internal deadline
• Number of support requests, and how many were repeats
• Number of teachers who have logged in this week

Share the numbers openly and celebrate progress. When one department lags, treat it as a signal to help, not a reason to blame.

If parents will receive alerts or use an app, tell them what is changing, why, and what they need to do. A short message before launch prevents a flood of calls to the front desk afterwards.

Adoption is not a training event. It is a few months of clear expectations, visible support and small, repeated wins. Schools that plan for the human side of a rollout find that the technology mostly takes care of itself.

See how a simple daily workflow can win teachers over: explore attendance management.