AI for School Boards in Canada

When school boards call us

• Teachers already use AI tools on their own. Lesson plans, rubrics and parent letters go through personal accounts, and the board has no approved tool or written rule.
• The O. Reg. 52/26 notice is new. The board needs a list of every app that receives student data and a notice for each one, ready early in the school year.
• Trustees want a position on AI. Senior staff need a short written view on benefits, risks and cost before a policy goes to the board.
• Central office inboxes never empty. Transportation, registration, HR and special education administration answer the same questions every week.
• Families write in many languages. Schools need accurate answers to routine questions without a translator on every message.

What we automate for school boards

App register and O. Reg. 52/26 notices. Document processing reads vendor contracts and privacy terms and fills a register: data elements, purpose, vendor name and contact. It then drafts the notice text for each app. The privacy or FOI coordinator checks each entry and approves the notices.

Parent and community inquiry assistant. An FAQ assistant built on board policies, school calendars and transportation rules answers routine questions in several languages and links to the source page. Anything about a specific student goes to school staff.

Central office email triage. Email automation sorts incoming messages by topic and urgency and drafts replies from approved templates. A staff member reviews and sends.

Drafting support for teachers. Lesson plans, rubrics, newsletters and first drafts of routine letters on a board-approved tool. Teachers edit and sign everything that leaves the classroom.

Staff AI use policy and training. A written AI use policy that names the approved tools and the data allowed in each, followed by training by role for principals, teachers and office staff.

Rules that shape AI work in schools

O. Reg. 52/26 (Ontario). From July 1, 2026, a school board must give written notice when personal digital information about a student goes to the owner or operator of a third-party software application. The notice goes to the parent or guardian of a student under 16, or to the student at 16 or 17. It names the data elements, legal authority, purpose, app and vendor, a contact person and the student's rights. Every new AI tool that receives student data adds a line to the register and a notice.

MFIPPA (Ontario). School boards are institutions under MFIPPA. Mandatory privacy impact assessments and breach notification under MFIPPA start January 1, 2027. We draft the PIA for a new AI tool now, so it is ready when the duty applies.

O. Reg. 51/26 (Ontario). From July 1, 2026, school boards run a cyber security program with a senior cyber contact and report critical incidents to the ministry within 72 hours after confirming them. AI tools and integrations join the board's inventory and incident plan.

IPC Ontario on edtech. The Commissioner wrote in November 2025 that school boards "cannot outsource accountability for protecting the personal information entrusted to them." Vendor due diligence therefore stays with the board, and the register keeps the evidence.

Vendor training terms. OpenAI states that data from ChatGPT Edu and ChatGPT for Teachers is not used for training by default. Microsoft states that prompts and responses in Microsoft Copilot (formerly Microsoft 365 Copilot) are not used to train foundation models. Anthropic states the same default for its commercial products. The staff policy names the approved plan, because consumer accounts follow different terms.

Quebec. School service centres are public bodies under the Act respecting access to documents held by public bodies (A-2.1). A new information system needs a privacy impact assessment under section 63.5.

Which package fits

Most boards start with the AI Readiness Review: one week, a score, the gaps to close and 3–5 candidate uses. A board that wants a full map across departments takes the Opportunity Audit.

Full scope of each package is on the pricing page.

How the work runs

The work follows the Remolda Cycle: Audit → Strategy → Implement → Empower → Evolve.

1. Audit. A session with a senior leader, the privacy or FOI coordinator, IT and a principal. We look at current AI use, licensed tools and the list of apps that touch student data. Student records stay out of scope.
2. Strategy. A short list of use cases, the policy points trustees will ask about and the PIA questions for the first tool.
3. Implement. One workflow built on the board's approved tenant, with the privacy coordinator signing off before launch.
4. Empower. The staff AI use policy and training by role.
5. Evolve. A review each term of what staff use, what families ask and which app notices changed.

In our experience the review usually takes one week from the session to the written summary. It depends on the school calendar and how quickly the app list and policies arrive.