How to choose school software without making a mistake: checklist for directors

How to choose school software without making a mistake: checklist for directors

Choosing the management software for your center is one of the most expensive decisions to make: not in license price, but in time, data and disruption when the system doesn't fit and you have to start over. In 2026, the Spanish market has solid options, but also solutions that sell modules that no one is going to use, promise integrations that do not exist and hide the migration cost until the signature. The antidote is an honest evaluation process, with your own criteria (not those of the seller), a demo with your real data, and a three-year total cost calculation before committing. This checklist for directors gives you the framework for that process.

Before searching: define your real problem

Most schools start looking for "the best school software" without having defined what their main problem is. The result is a catalog evaluation where the seller most skilled in presentation wins, not the most suitable. Start by listing the five most frequent frictions your management team faces: non-payments and manual reconciliation? Peak enrollment in September with paper management? WhatsApp communication without registration? Files lost or distributed in three tools? That inventory is your purchasing criteria. If the software you are evaluating does not solve at least three of those five frictions directly, with modules available today, it is not the right one for your center.

Module checklist: essentials vs. what you can add later

Essentials in any center:

• Unified digital file with student data, tutors, history and groups.
• Recurring billing with receipts, direct debit, collection history and non-payment management.
• Portal or app for families with basic self-management (access to file, payments, basic communication).
• Onboarding and documented support: you cannot depend on a single technician to use your own tool.

Assess according to the center:

• CRM with pipeline of requests, forms and statuses, if you have a waiting list or active recruitment campaign.
• Pro communication with push and read confirmation, if the volume and criticality of messages justify it.
• Cloud documentation module, if the document volume is high or your regulation requires an audit.
• Extracurricular activities and stores, if you manage activities with your own places and charges.
• Automation of tasks and notifications, if you want to reduce manual work in repetitive processes.

Questions for the demo: what the provider does not always show on its own initiative

• Can I see the complete flow from a place request to the first payment with my data, not with demo data?
• How is a non-payment managed: how many clicks, what automatic actions and how is it recorded?
• How is my data exported if I decide to change providers in two years?
• What happens if there is an error on a receipt that has already been sent: how can it be rectified without breaking the numbering?
• Where is the detailed migration plan by phases: master data, history, documents?
• How many simultaneous users does support have today? Is the answer 24/7 or during office hours?
• Which modules are included in the base price and which have an additional cost?

How to calculate three-year TCO

The monthly license price per student is just the first layer. Add:

• Migration cost: external or internal technician hours, data validation, systems coexistence.
• Training: not only the initial onboarding, but the cost of training each new addition to the team.
• Integrations: if you need to connect with payroll, external accounting or third-party applications.
• Modules not included in the base price that you will need in year two.
• Re-migration risk: if the system does not scale or the provider changes its business model.

In most cases, a seemingly cheaper system that requires two external integrations ends up being more expensive than an integrated one with modular pricing. Ask the provider for a three-year projection with all these components, not just the monthly rate.

Alarm signs at a supplier

• You cannot demonstrate the functionality with your data in the first session.
• The migration plan is "we solve it in the implementation" without a document.
• The exit contract does not specify how you recover your data in open format.
• Support is only during office hours for a service that is used 24/7
• The "all-inclusive" price hides modules that "are not active in your base plan."
• They cannot show you verifiable references of centers with profiles similar to yours.

The recommended decision process

Week 1: friction inventory and own criteria. Week 2: shortlist of three suppliers, first demo with catalog. Week 3: in-depth demo with own data on the two finalists. Week 4: TCO calculation, contract review (data portability, exit clauses, support) and decision. Pilot: starts with the highest friction process, measures for ninety days and then expands. Do not buy seven modules if you can only activate two well in the first three months: empty software is not an investment, it is a cost.

Numbered checklist for purchasing committee

1. Define three measured pains: Inventory processes in hours or euros (collections, registration, communication). Without a starting metric there is no criterion for the pilot's success.
2. List essentials: Collections, file, family portal and user roles. The rest is desirable, not blocking the first phase.
3. Request a demo with real data: Five fictitious but plausible families and a complete cycle of receipts, not just a catalog of screens.
4. Calculate 36-month TCO per student: License, migration, training, integrations and internal coordination hours.
5. Pilot 8-12 weeks with written cut-off criteria: What KPI must be met to continue (delinquency, admin hours, conversion).
6. Validate data and support commissioning contract in September: Confirm DPA, SLA and response at enrollment peak.
7. Agree on a migration plan and internal manager: A person with a management mandate, not just external IT.

Demo scorecard (0-5 per criteria)

• Billing and delinquency (0-5): Do you issue recurring receipts, reconcile payments and show debt age without Excel? Does it allow staggered reminders and credit traceability?
• Family Portal (0-5): Does the family check status, authorize departures and pay without calling the secretary? Is there a read receipt on critical notices?
• CRM and admission (0-5): Pipeline with stages, lead origin and follow-up in 48 hours? Do you connect reservation with first payment?
• File (0-5): Student data, tutors, NEAE and centralized documents with permissions by role?
• Automation (0-5): Rules for reminders, onboarding and repetitive tasks without multiplying route sheets by hand?
• Security and LOPDGDD (0-5): Custom contract, roles, access log and subprocessors documented?
• Support and implementation (0-5): Phased migration plan, training and support during critical hours (September)?
• Cut-off rule: Sum less than 28/35 points: discard or require a second pilot of 8-12 weeks with real data before signing.

Context in Spain: what a school ERP requires in 2026

Beyond grades and attendance, school management software in Spain must cover billing (including Verifactu preparation), family portal or app, file with minor data under GDPR and LOPDGDD, and communications traceability. Buying an isolated SIS when the real pain is in secretarial, collections and families usually ends in duplicating data between three tools.

In nursery schools they weigh places, ratios, menus and allergies; in academies, bonuses, seasons and multiple venues; in private schools, differentiated fees, internal scholarships and commercial recruitment. An ERP that works in language academies may fall short if you manage child, NEAE or dining room ratios with billing per day.

Evaluates three-year TCO: license, migration, training, internal coordination hours and cost of bridge integrations. Request a demo with your real data (five families, one cycle of receipts) before deciding. Software that seems cheaper at the beginning can become more expensive if it forces you to add CRM, billing or communication separately.

Case study (Spain)

An 85-place nursery school in Girona evaluated three providers with the same checklist: enrollment, menus, billing and family app. The 10-week pilot with real data revealed that only one closed the application-enrollment-payment cycle without Excel. The change cost them 40 hours of migration, but they eliminated duplicate data in three tools.

Conclusion

Choosing the software for your center well is not about comparing product sheets: it is about defining your problem, doing the demo with your data, calculating the real cost and reading the contract. Edena is the platform that centralizes file, collection, registration, communication, documents and analytics with modules that can be activated according to the real need of the center, 24/7 support and accompaniment in the change process. Request a demo, bring your five main frictions and in ninety minutes you will know if it fits.