It's worth being honest about why these gaps stay hidden for so long: sales demos are built to show a product at its best, on a script the vendor controls. The twelve points below are deliberately the kind of question a demo doesn't answer unless you ask it directly, because they're the details that separate a smooth first term from a frustrating one.
Content & levelling
CEFR (or equivalent) alignment across the full range you teach, a large enough story library to avoid repetition, and a clear path for adding your own content alongside the vendor's.
On content and levelling specifically, ask to see the actual level-assignment logic, not just a marketing claim of "CEFR-aligned." Some platforms level content once at launch and rarely revisit it; others continuously refine levelling based on how students actually perform against each story, which matters more than it sounds once a library grows past a few hundred titles.
Delivery & engagement
Live-session support if you teach synchronously, built-in vocabulary practice (not bolted-on flashcards), and a motivation layer — challenges, streaks, or competition — that survives past the novelty phase.
On delivery and engagement, the detail that trips schools up most is what happens when a live session's usual teacher is absent. A platform with only single-teacher session ownership can leave a class without access on a sick day; better systems let any authorized staff member step into a scheduled session without losing continuity.
Reporting & operations
Dashboards a teacher can read in one glance, a parent-facing view that needs no explanation, and admin tools for scheduling and rostering that don't require a technical staff member.
On reporting and operations, the make-or-break detail is usually export flexibility. A dashboard that looks clean on-screen but can't produce a simple CSV or PDF for a parent evening or a board meeting creates exactly the kind of manual follow-up work the platform was meant to eliminate.
A simple way to run the checklist live
Rather than emailing this list to a vendor and reading their written response, work through it on a call and ask them to demonstrate each point on screen in real time. Written answers can describe an aspiration; a live demo either shows the feature working or it doesn't, and that distinction becomes obvious within minutes.
What a strong answer sounds like
On the workload question specifically, a strong vendor answer names a concrete number — for instance, minutes to launch a first session, or the number of clicks from login to a student reading — rather than a general reassurance. Vague confidence is the most common tell that a feature exists in theory but hasn't been tested against a real school's constraints.
Where this checklist tends to save the most time
Schools that run this checklist before, not after, a demo report shorter evaluation cycles overall, because it front-loads the questions that would otherwise surface piecemeal across several follow-up calls. A single structured session covering all twelve points typically replaces what would otherwise be three or four shorter conversations.
Turning the checklist into shortlist decisions
Score each of the twelve points on a simple scale during the live demo — clearly present, partially present, or missing — rather than trying to weigh them all equally afterward from memory. In practice, a handful of these points end up mattering far more to a given school than the rest, and scoring in the moment makes it obvious which gaps are dealbreakers versus which are minor and workable. Comparing two vendors' score sheets side by side afterward is a far faster decision process than re-reading notes from separate calls days apart.
A note on trial periods
Even a strong live demo only shows a platform working under ideal conditions with a vendor driving. The real test is a short trial where your own staff log in, schedule a session, and try to produce a parent-ready report themselves, without a salesperson guiding each click. Discrepancies between a polished demo and a hands-on trial are common and worth surfacing before a full commitment, since the person actually using the tool day to day is a teacher, not a vendor's sales engineer.
Ask for a live walkthrough: Any vendor can describe these 12 points. Ask them to demonstrate each one on screen — that's where real gaps surface. A vendor's live response to these twelve points during a single call tells you more than a week of reading marketing pages will.
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
A checklist only earns its keep if it's used during the sales process, not after signing — every point above is designed to be asked out loud, on a call, with a request to see it demonstrated rather than described.
Frequently asked questions
What's the single most-skipped item on this list?
Parent-facing reporting. Many platforms report to teachers only, leaving schools to build their own parent updates by hand.
Should pricing be part of the checklist?
Yes, but as the last filter — first confirm a platform can do what your school needs, then compare cost among the finalists.
How many vendors should realistically go through this full checklist?
Two or three finalists is usually enough. Running the full checklist against every platform in an initial long list wastes time better spent narrowing down to serious contenders first through a lighter first pass.