Why consolidate, and when not to
Schools accumulate software the way they accumulate furniture: each purchase made sense at the time. Years later there are several gradebooks, three ways to message families, duplicate calendars and a spreadsheet holding the truth. Consolidation is worth doing when staff time is going into moving information between systems, and when nobody can say with confidence which record is right.
It is not worth doing for its own sake. If the tools are few, well liked and connected, the disruption of replacing them can cost more than it saves. Start by finding out whether you have the problem.
Start with an inventory
List every system used by teachers, students, families, coordinators, finance, HR and leadership, including the ones nobody bought, such as free tools and personal spreadsheets. Record enough about each to compare them.
| Field | What to record |
|---|---|
| Purpose | What job the system does, in one sentence |
| Users | Who uses it, roughly how many, and how often |
| Data | What it holds, including student data and where it came from |
| Integrations | What it connects to, and whether by real connection or manual export |
| Owner | The person responsible for it, and who fixes it when it breaks |
| Contract | Renewal date, notice period and price per user |
| Satisfaction | What staff say, in their words |
Find the duplicate workflows
The inventory tells you what you have. The duplicates tell you where the cost is. Look for these:
- The same student data entered into more than one system
- Separate gradebooks or markbooks for the same classes
- Several tools for communicating with families
- Duplicate calendars that disagree
- Manual exports and imports between systems, done every term
- Reports assembled by hand from three places
Decide what to consolidate and what to keep
Not everything should move. Consolidate where the seams cost the most and where the data is shared by many people: the student record, assessment, reporting and family communication. Keep a specialist tool where it is clearly better at a job that little else depends on, or where replacing it would be a large project for a small gain.
A useful test for each system is what would break, and for whom, if it disappeared tomorrow. The answer tells you how central it is and how carefully to plan.
Where skodle fits
This section names our own product, so read it as that. The strategy above works whichever platform you end up choosing.
skodle can take over a school's core teaching workflows behind one login: curriculum planning, assessment and gradebook, portfolios, reports, daily attendance, timetable, behaviour, family messaging and staff professional development, with role-based portals for staff, students and families. For the first phase of a roadmap, the highest-friction candidates are usually the gradebook and report cycle and the family-communication tools. See the product overview and assessments and gradebook.
The limits, which shape the roadmap. Integrations with other systems are not working connectors, so any tool you keep runs beside skodle with manual exports and imports. The Migration Centre imports students and staff from a spreadsheet, up to 5,000 rows at a time, so historical grades, attendance history and portfolio media do not move and must be archived from the old tool first. There is no self-serve export of a whole school's data: an administrator can export one student's record as a data file, and reports, transcripts and some registers come out as documents, so ask about leaving before you arrive. There is no library, transport, canteen or inventory module and no native mobile app.
Pricing is per user, per month: $2 per user for up to 150 users, $3 from 151 to 500 users and a custom plan above 500, with parents at half the rate and every feature in every plan. Every new school starts with a free 30-day trial, so the fair test is your own data. See pricing.
Build a phased roadmap
Do not change everything at once. A workable sequence is to prioritise the highest-friction workflow, pilot it with one year group or department, migrate data carefully, then extend. Time each phase around the school calendar, away from report writing, assessment windows and, for IB schools, Diploma deadlines.
- Phase 1: inventory, decisions and a named owner for the project
- Phase 2: pilot the highest-friction workflow with one group
- Phase 3: migrate data for that workflow and retire the old tool
- Phase 4: extend to the next workflow, using what the pilot taught
- Phase 5: review after a full year and decide what remains
Handle data and contracts together
Two things trip up consolidation projects. The first is data: decide what must move, what can be archived and what can be dropped, and check what each old system can export before you commit to a date. The second is contracts: the renewal and notice dates of the old systems set the earliest sensible date to switch them off, and missing a notice period can mean paying for a year of a tool nobody uses.
Measure the outcome
Decide in advance what improvement you expect and how you will know. Sensible measures are the staff hours spent on repeated entry, the time to produce a report cycle, the number of systems staff log into, the number of data-quality errors found, and the effort of preparing evidence for a review. Measure before you change and again after a full year, and say plainly if the gain is smaller than promised.
The wider question of what an all-in-one platform should include is covered in all-in-one school management systems for international schools.
