School ERP Implementation Checklist: Before, During and After Setup

Before setup: agree on the goal

Write down the problems the school expects the software to solve. Identify the workflows included in the first phase and the staff responsible for them. Agree on what a successful pilot looks like, such as fewer repeated entries or faster preparation of a particular report.

Prepare the data

• Choose a unique identifier for each student.
• Standardise class, section and subject names.
• Check guardian contacts and required fields.
• Remove duplicate or obsolete entries.
• Keep a secure backup of the original records.
• Decide who can approve changes to important information.

During setup: configure roles and workflows

Create individual accounts rather than shared logins. Give each person only the access needed for their role. Configure the academic year, classes and relevant workflows, then test with sample records. Confirm that staff know how to report an issue and where to get help.

Run a pilot before the full rollout

Select a small group of teachers or one class. Test normal tasks as well as exceptions: a student changes section, a guardian contact is corrected, an attendance entry needs adjustment or a report must be regenerated. Keep the existing process available until the pilot is stable.

After launch: review adoption and quality

Meet staff after the first week and again after the first month. Review incomplete records, support requests and the time required for routine tasks. Update training materials when the same question appears repeatedly. Remove access for accounts that are no longer needed.

Keep ownership clear

The school should know who manages accounts, approves changes, reviews backups and contacts the provider. It should also understand the export process and the terms for renewal or cancellation.

A careful implementation is more valuable than a rushed launch. Use this checklist when comparing providers and planning your school's rollout.