LMS selection for schools almost always goes wrong. Not because the people involved are careless, but because vendors lead the process far too early. A sales rep gets in front of the right person. A demo happens. The product looks impressive. Before long, the school signs a contract without ever defining what it actually needs.

Eighteen months later, nobody uses the system. The IT team is fielding complaints. Leadership can’t work out what went wrong.

Here’s what a better process looks like.

Start with requirements, not products

This seems obvious. It’s surprisingly rare in practice.

Before inviting a single vendor to present, the school needs a clear, documented picture of what the LMS should do. Not a wish list of features, but requirements tied to actual learning and operational outcomes. What does the school need to achieve with this platform that it can’t do now? Where are the workflow gaps? What does success look like in twelve months, in measurable terms?

Requirements also need to come from the right people. Teachers, not just administrators. Heads of department, not just IT leads. Staff who use the system every day have very different needs from those who procure and maintain it. Skipping this step is how schools end up with a platform that satisfies the procurement committee and alienates the classroom.

Build an LMS evaluation matrix before the demos

Once requirements are clear, build a weighted evaluation matrix before talking to any vendor. The weighting reflects what matters most: core functionality, ease of use, integration with existing systems, data compliance, cost of ownership, and vendor support.

With the matrix in place, every vendor demo faces the same criteria from the same people. This does two things. It stops the most confident presenter from winning regardless of product fit. It also creates a documented decision trail the school can defend to a board, a parent body, or an auditor.

Data compliance is not optional

Any LMS a school deploys processes student data. In most jurisdictions, that triggers specific legal obligations around storage, access, and sharing. GDPR in Europe, PDPA equivalents across Southeast Asia, and various national frameworks all set requirements that a vendor’s standard contract may or may not meet.

Resolve this before signing, not after deployment. Ask every vendor: where does student data sit? Who can access it? How does the vendor use it? What are the retention and deletion policies? What happens to data if the school ends the contract?

Most reputable LMS vendors can answer these questions cleanly. Schools just rarely ask them.

The total cost of ownership trap

The licence fee is not the cost of the LMS. Implementation, data migration, system integration, staff training, ongoing support, and internal staff time during transition all belong in the cost model.

Schools consistently underestimate implementation costs by a factor of two or three. Support costs also catch many out, because nobody examined the vendor’s tier-one support model closely during procurement. A realistic total cost of ownership model, built before the final decision, gives a very different picture than a licence fee comparison alone. It also tends to favour vendors with stronger onboarding, which is what actually drives adoption.

Run a pilot before committing to any LMS selection

For any major LMS selection for schools, a structured pilot with one or two departments is worth the extra time. Not a loose arrangement where a few teachers try it out and share informal thoughts. A defined pilot needs a clear protocol, specific usage expectations, and an evaluation framework that produces structured data.

What you learn in a structured pilot, about real usability, gaps between vendor claims and reality, and where staff adoption friction lives, is far more valuable than a demo. It’s also far cheaper than learning those things after signing a full deployment contract.

Polymath Consultancy runs structured LMS selection processes for schools and universities, from requirements gathering and vendor shortlisting to pilot design and adoption planning. If your school is approaching a platform decision, our advisory keeps the process evidence-led rather than vendor-led. Speak with our team at polymathconsultancy.com/contact-us to start with a digital maturity assessment.

Learn more about our Digital Transformation in Education service