Proof and references
Evaluate evidence without inflated claims
Use these pages to ask for approved context, workflow scope, implementation detail, measurable outcomes, and honest caveats before relying on a customer story.
Choose a question
Start with the page closest to your decision
Each page includes workflow steps, responsible teams, implementation detail, boundaries, evidence links, and FAQs.
Available now
Customer evidence standards
Understand what makes a school software story useful: named context, workflow scope, timeline, evidence, and an attributed outcome.
Read the pageAvailable now
School software implementation story template
A structured brief for documenting a real school rollout without turning a customer story into unsupported marketing claims.
Read the pageValidate for rollout
Request a relevant school reference
Prepare a focused reference request by curriculum, school type, workflow, module scope, and implementation stage.
Read the page
Rollout walkthroughs
What the first year looks like, by type of school
Four recognisable starting positions, each with the sequence, the reason for that order, what reliably goes wrong, and what a platform does not fix.
A day school moving off spreadsheets
Around 600 students, single campus, one national curriculum, records spread across spreadsheets and a filing cabinet.
An international school running two curricula
Around 1,200 students across two sections, two curricula with different assessment models, tuition billed in a local currency.
A school where fee collection is the presenting problem
Any size, where the immediate pain is collection: cash and cheques, manual receipts, and a debtor position nobody can state confidently.
A school replacing an incumbent platform
Already running a school ERP, moving because of cost, support, or a capability the incumbent will not deliver.
This is a composite, not a customer story. It describes how a rollout typically goes for this kind of school, drawn from implementation experience across several. No school is named, no figures are attributed to a customer, and nothing here is presented as a measured outcome. Named case studies appear on this page only with written consent and stated measurement methods, and none are published yet.
How to use this directory
Guidance before you pick a page
Read this first if you are not sure which page answers your question.
Read case studies for scope, not for numbers
A headline percentage without a baseline, a time window, and a definition is not evidence. The parts of a case study worth reading are the scope of the workflow that changed, the size and type of school, how long the change took, and what did not work.
These pages set out how to extract that structure from a customer story, including which claims to discount entirely.
Ask for a reference that matches your constraints
A reference from a school with different enrolment, curriculum, fee structure, or regulatory context tells you very little about your own rollout. Ask specifically for a school similar in the dimension that worries you most, and accept that a narrow honest match is more useful than an impressive mismatch.
It is also fair to ask what a vendor learned from a rollout that went badly. The answer is informative either way.
We label unverified profiles as unverified
Our public directory includes school profiles compiled from public sources alongside named customers who have given consent. The two are marked differently on purpose, and the compiled profiles are excluded from search indexing because presenting them as endorsements would be dishonest.
When you ask us for references, expect a shorter list of consented, verifiable schools rather than a long list of logos. A logo wall is easy to assemble and tells you nothing about whether any of those schools would take your call.
The same standard applies to our published guides. Where a piece has not been reviewed by a named subject expert it says so and credits the editorial pipeline rather than inventing a byline, because an authority signal that cannot be checked is not an authority signal.
Questions about this directory
How to use these pages during an evaluation, and what they deliberately do not claim.
How should we evaluate a school software case study?+
Check four things: the school is identified or the anonymity is explained, the workflow scope is specific, any metric has a baseline and a time window, and at least one difficulty is described. A case study missing all four is marketing copy and should carry no weight in a decision.
Run a representative class through draft, review, and publish states before relying on the output for a reporting deadline. Check which role owns corrections after the result becomes visible to families.
What should we ask a reference school directly?+
What surprised them during implementation, what they would sequence differently, which staff group took longest to adopt the platform, how support responded to their first serious problem, and what they still work around. These questions produce more signal than asking whether they are satisfied.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Why are some school profiles marked unverified?+
Our directory distinguishes profiles compiled from public information about schools in a market from schools that are Schoolyi customers and have consented to be named. Compiled profiles carry no claim of a customer relationship and are excluded from search indexing.
Run a representative class through draft, review, and publish states before relying on the output for a reporting deadline. Check which role owns corrections after the result becomes visible to families.
Can we speak to a school similar to ours?+
Ask, and specify the dimension that matters: enrolment band, curriculum, country, fee structure, or number of campuses. If we do not have a consented reference that matches, we would rather say so than offer a school whose situation does not inform yours.
Confirm the campus scope and reporting boundary with a representative deployment before treating the capability as group-wide. Record which work remains local when the school group plans its rollout.
Need help choosing the first page?
Bring your school’s workflow, roles, and first-term priorities to a focused walkthrough.
Already using Schoolyi? Sign in