Most of that confusion comes from comparing tools that were never built to do the same job. A school searching "reading platform" ends up with search results mixing publisher catalogs, US intervention software, and simple word-count trackers — three different product categories answering three different questions, none of which is quite "how do we run a reading program for EFL learners." Understanding which category a tool belongs to is the fastest way to cut a long shortlist down to a short one.
What the main categories offer
Graded-reader publishers (Oxford, Pearson) supply levelled books but little delivery infrastructure. US ELL platforms (Newsela, Lexia, ReadWorks) are built for native-curriculum intervention, not EFL levelling. Tracking tools (MReader, ER-Central) log word counts but don't teach. Foxton Readers is the closest EFL-specific rival, pairing CEFR readers with a school LMS.
Publisher libraries are usually strong on content quality and weak on everything around it — there's rarely a way to schedule a live session, run a competition, or see a dashboard a non-specialist parent can understand. They're a reasonable foundation if a school already has its own delivery and tracking systems, but a poor fit as a standalone solution.
What an EFL/ESL school actually needs
A program built for English learners needs CEFR alignment from day one, vocabulary instruction (not just exposure), a way to run it live or self-paced, and reporting a non-English-speaking parent can still understand — progress by level, not just pages read.
US ELL platforms carry an assumption that's easy to miss until it causes a problem: they're usually levelled against native-speaker reading benchmarks, not CEFR. A ten-year-old EFL learner and a ten-year-old native-speaker struggling reader are not the same profile, even if a tool's internal level number matches — the vocabulary gap is fundamentally different.
A shortlist approach that works
Shortlist 3–4 platforms, request a real demo with your own class size and schedule, and ask each vendor to show — not describe — how a teacher launches a first session and how a parent sees progress.
Tracking tools solve accountability, not instruction. They're excellent at confirming a student actually read a book, but they assume the content, the vocabulary teaching, and the motivation layer already exist somewhere else. A school adopting one of these tools is really deciding to build (or already have) the other three pieces separately.
How to run a fair comparison
The most reliable way to compare platforms isn't reading feature lists side by side — it's requesting a demo using your school's actual class sizes, level spread, and weekly schedule, then asking each vendor to show, live, how a teacher would launch a first session tomorrow morning. Feature lists tend to look similar; the actual number of clicks between logging in and a student reading a story rarely is.
The question that separates categories fastest
Ask each vendor directly: "if I have zero existing content, how long until my first class is reading?" A publisher library answers in days or weeks (sourcing and organizing). A tracker answers "immediately, but you'll need content from elsewhere." A platform built for EFL delivery from the ground up should be able to answer in hours, because content, levelling, and delivery were designed as one system rather than assembled from parts.
What tends to get overlooked in a shortlist
Parent-facing reporting is the single most commonly missed requirement in early platform comparisons. Schools focus the demo on what a teacher sees, then discover months later that translating platform data into something a parent can understand at conferences requires building a separate report by hand. Asking to see the parent view during the very first demo avoids this gap entirely.
A shortlist template worth copying
A workable shortlist process looks like this: list every platform that survives the category filter above, cut anything that can't answer the "how long until my first class reads" question in under a day, then run the remaining two or three through a live demo using your school's actual numbers. Most schools that follow this order finish their evaluation in two to three weeks rather than the month or more it takes to compare feature lists in the abstract without a structured filter first.
Where iRead fits: iRead combines CEFR-levelled stories, vocabulary games, quizzes, live scheduled sessions and parent-visible dashboards — the categories above, as one program. Ask specifically to see the CEFR-to-quiz mapping and the parent-facing view during any demo — these two things vary the most between vendors and matter the most day to day.
See it in iRead: iRead is a full reading program — CEFR stories, vocabulary games, quizzes and live sessions, ready to launch in a day.
See the iRead programKey takeaway
The fastest way through a crowded platform search isn't more research — it's naming which category you actually need (content, delivery, tracking, or all three combined) before comparing anything, since most of the apparent confusion in this space comes from comparing tools built for entirely different jobs.
Frequently asked questions
Is a graded-reader library enough on its own?
It can work for independent reading, but most schools pair it with something that levels, tracks, and motivates — otherwise usage drops off after the first term.
How long should a platform evaluation take?
Two to four weeks is typical: a demo, a short pilot with one class, then a decision — long enough to see real engagement data, short enough not to lose momentum.
Should a school ever combine tools from more than one category?
Some do during a transition period — pairing a publisher library with a separate tracking tool, for instance — but most schools consolidate onto a single platform within a year once they see how much admin time goes into keeping two systems' reporting in sync.