WebelieveOntario'sonlineschoolsdeservebettersoftware
Built by people who understand Growing Success, Form 3003E, and the 110-hour credit requirement. We've seen the spreadsheet chaos first-hand, and we built Edpace to fix it.
The problem we solve
Ontario's 446+ inspected private schools are held to the same standards as any publicly funded school. Growing Success, OSSD requirements, Ministry inspections — every rule applies. But the tools available today weren't built for this reality.
Schools use a patchwork of LMS platforms, student information systems, and spreadsheets — none of which understand KTCA categories, 70/30 weighting, or the Provincial Report Card template. Teachers spend weeks on compliance paperwork instead of teaching. Edpace replaces all of it with one platform built specifically for Ontario.
How we built Edpace
We didn't guess at compliance. We read every document, mapped every requirement, and built to spec.
Studied the regulations
We read every page of Growing Success, OS K–12, the OSR Guideline, the OST Manual, the Private Schools Policy Manual, and 12 PPMs. Then we mapped them into 175 discrete requirements across 17 domains.
Mapped the inspection form
We obtained the full 9-page Form 3003E (2025/06 edition) and mapped every checkbox to a platform feature. Three autoresearch validation runs against the form confirmed 100% coverage.
Built the compliance engine
KTCA evidence tracking, 70/30 weighting with professional judgment, the Learning Skills separate rail, pixel-perfect Provincial Report Cards, OST generation, OUAC/OCAS data export — all built to spec.
Validated with real schools
Partnered with Ontario inspected private schools to test every workflow against real students, real grades, and real inspection scenarios. Refined until every edge case was handled.
What we stand for
Four principles that guide every line of code we write.
Compliance-first
Every feature maps to a specific inspection item on Form 3003E. We don't bolt compliance on as an afterthought — it's the architecture.
175 requirements mapped across 17 compliance domains.
Canadian data residency
All student data is hosted in Canadian data centers (AWS ca-central-1). PII never leaves the country. PIPEDA compliance is non-negotiable.
Full audit trail on every mutation. Consent tracking built in.
AODA accessible
WCAG 2.0 Level AA compliant. Every component tested for keyboard navigation, screen readers, and 4.5:1 minimum color contrast.
Axe-core accessibility audit runs on every deployment.
Built for educators
Designed around teacher workflows, not around technology. Every interaction is informed by real Ontario classroom practice and Growing Success pedagogy.
Evidence-based gradebook, not a spreadsheet. Professional judgment, not averaging.
Ready to see Edpace in action?
Book a 30-minute demo and we'll walk you through the gradebook, report cards, and inspection checklist with your own school's data.