AI in Schools
NAPLAN platform gets $18.2m after March crashes
The Tuesday read is one budget line that quietly buys NAPLAN a runway, one Catholic-system rollout that puts generative AI in front of secondary students, and one US committee deadline that puts a number on Instructure's accountability work. The Sydney AI in Education conference is on at Swissôtel today, and the operational questions in the room are the same three.
Treasury puts $18.2 million on NAPLAN's tired online platform
The 2026-27 Budget, handed down a week ago Tuesday, includes $18.2 million over four years from 2026-27 (with $5.0 million per year ongoing) to support the Online National Assessment Platform operated by Education Services Australia. The 50 per cent Commonwealth contribution to hosting and maintenance is framed in the Budget papers as ensuring "essential NAPLAN data can be collected, and students and schools are not disrupted by failing technology". The line lands in the same Budget cycle that already suspended NAPLAN testing for around a million Australian students in March 2026 after a widespread platform outage.
Why this matters: This is the federal government quietly paying the bill for an assessment platform the system depends on but had stopped properly funding. For state systems and the independent and Catholic sectors that have built their assessment calendars around NAPLAN online, the practical question is whether ESA's quoted run-cost is enough to actually retire the architectural debt that produced the March crashes, or whether $4.55 million a year keeps the platform alive at the same fragility. For procurement teams running PAT, ACER and Edrolo equivalents against NAPLAN as the national benchmark, the funding signal is that the Commonwealth will not be moving to a different national platform any time soon, which means a 2027 or 2028 procurement decision against the existing rails is now the safer bet. The Nightly on the $18.2 million NAPLAN allocation, and the ACS Information Age write-up of the March platform crash that triggered the line.
Brisbane Catholic Education opens Microsoft Copilot to secondary students
Brisbane Catholic Education announced on 13 May that Microsoft Copilot is now available to secondary students aged 13 and over across its 146 schools on an opt-in basis, free to schools that complete BCE's mandatory readiness activities. The pitch is real-time learning support, personalised feedback, and built-in safety protections, and the published evidence base is the 2025 trial at Trinity College Beenleigh that the University of Melbourne's New Metrics for Success project measured as a 275 per cent lift in learner agency for at-risk cohorts. BCE's framing is "guide students rather than limit them," with the rollout aligned to the Australian Framework for Generative AI in Schools and the Rome Call for AI Ethics.
Why this matters: The diocesan-system staff Copilot rollout (12,500 educators, 80,000 students addressable through staff use) was the network reference Microsoft already had in market. Opening the tool directly to students changes the procurement comparison again, because the question for every other Australian diocese, AISNSW member, and state system is now whether their internal Framework readiness pack can pass BCE's bar, and what their answer is if a parent asks why the school next door has Copilot in student hands and they do not. The 275 per cent figure is interesting and will not survive contact with the wider cohort intact, but the direction of travel is the read: implementation case studies are now student-facing, not staff-facing, and the comparable in the next twelve months will be NSW EduChat or a Google Gemini for Education pilot, not whether to deploy at all. Brisbane Catholic Education's announcement of the student Copilot rollout.
US Congress gives Instructure until 21 May to brief on the Canvas intrusions
House Homeland Security Committee chair Andrew Garbarino wrote to Instructure CEO Steve Daly on 11 May requesting a briefing no later than this Thursday 21 May on both Canvas intrusions, the data accessed, containment, notification, and Instructure's coordination with CISA and federal law enforcement. The letter follows Instructure's 12 May confirmation that it had reached an agreement with ShinyHunters and that the group had returned and destroyed the 3.65 terabyte dataset, with the company's caveat that "there is never complete certainty when dealing with cyber criminals". Garbarino's framing is that "the gap between Instructure's public characterization of this event and the scale suggested by the attacker's own claims warrants a full and transparent accounting".
Why this matters: This is the part of the Canvas story where the regulator-and-legislator track starts moving faster than the institutional response. For Australian vice-chancellors and chief operating officers, the relevant read is the precedent the US briefing will set on what a major ed-tech vendor has to disclose, because that disclosure standard will land in Australian council risk papers and OAIC complaint files within the year. For school IT leaders, the procurement implication is narrower: the question to put into every renewal conversation this fortnight is whether the vendor has been the subject of legislative inquiry in any jurisdiction in the last six months, because by mid-June Instructure will not be the only one. The Record on the Garbarino briefing request and Instructure's ransom statement, and the House Homeland Security Committee's announcement of the briefing request.
From Digital Attitudes: twelve questions to find where the operational load is actually building up
The week's three stories have one common shape. A national platform under-funded for years (NAPLAN), a diocese rolling out an AI product into student hands (BCE), and a vendor under legislative scrutiny (Instructure) all land on the same operational team inside a school: business managers, IT leads, and the deputy who quietly keeps the systems running. The essay published earlier this month sets out twelve diagnostic questions to find where that operational load is actually building up across an Australian school, before the next vendor incident, framework update, or platform crash adds another item to the list. It is built for the operations meeting, not the strategy retreat, and pairs well with the procurement conversations the day's stories will trigger. Twelve questions to find where your school's operational load is actually building up.
If you are at Swissôtel today, the floor conversation worth having is which of these three stories the school sector should be asking the NSW Department of Education and ACARA about by Friday: the platform funding, the diocese-led student rollout, or the vendor-disclosure standard that is about to harden. More on the operational thread at digitalattitudes.com.au.