The first day of school is a product of the summer. Every teacher who opens a cart of charged, working Chromebooks in September is benefiting from decisions made months earlier. Every classroom where three devices won’t turn on, two are missing keys, and one screen is cracked is paying for a summer that was treated as downtime instead of preparation time.
For K-12 IT teams, summer is the highest-stakes window of the year, and what happens during it has direct consequences for instructional time, student equity, and teacher morale on day one.
The Scale of the Problem Is Larger Than Most Schools Realize
A year of learning is hard on hardware. Chromebooks and tablets travel between school and home, often without cases, often without care. By June, most device fleets show the evidence: missing keys, cracked screens, batteries that drain in an hour, chargers that have vanished entirely. Classroom hardware faces the same wear: projectors with dying bulbs, interactive displays with calibration issues, charging carts that spark when you plug them in.
None of this is surprising. What is surprising is how many schools approach the June device collection as a checklist rather than a diagnostic moment. Collect. Stack. Store. Redistribute.
Sarah Thomas, instructional technologist and founder of EduMatch, names the shift that matters: “It is easy to treat the summer tech closeout as a checklist, but I would advise closing out the year with the next one in mind. Once you know what your teachers and students will need in the fall, every choice about what to refresh, repurpose or retire is aligned with where you are headed.”
That reframe matters because it changes the question IT teams are answering. The checklist question is: what is broken and how do we fix it? The instructional question is: what does this school need to be able to do in September, and does our device fleet support that?
The Four-Part Framework That Changes the Conversation
A solid summer prep process moves through four distinct phases, and each one has implications that reach beyond the IT department.
The first is a full audit and physical inspection of every device. This means checking not just whether a device powers on, but whether it performs at the level students need. A Chromebook that boots but takes four minutes to load a Google Doc is not a functional learning tool. Battery health, keyboard integrity, screen condition, and charging compatibility all belong in that assessment. So does a comparison of physical inventory against assignment records: who had which device, and what condition did it come back in?
This audit layer is where equity decisions live. If one grade level consistently returns devices with more damage than others, that pattern tells you something. It might be developmental, meaning third graders handle Chromebooks differently than eighth graders. It might be structural, meaning students carrying devices home on buses need sturdier cases. It might be about communication, meaning families needed clearer guidance on device care. Acting on those trends prevents the same problems from compounding next year.
The second phase is categorization: sorting every device into clean and ready, needs repair, ready for redeployment to a different use, or ready for retirement. This is where schools often leave money on the table. Devices that are no longer ideal for daily student use may still be perfectly functional for a charging station, a teacher reference device, or a low-demand task like running a classroom timer or displaying a schedule. As Sandra Paul, former IT director of Township of Union Public Schools, noted when her district scaled from 2,400 to over 7,000 Chromebook devices after the pandemic: some devices sent to manufacturers for warranty repair, those out of warranty were assessed on whether repair or replacement made more financial sense. That case-by-case evaluation, applied at scale, is the difference between a sustainable device lifecycle and a budget spiral.
When IT Decisions Are Also Instructional Decisions
Here is where the conversation needs to move beyond the IT office.
The third and fourth phases of a strong summer plan address software and configuration: ensuring devices are enrolled in the right management systems, that apps and extensions are current, that security policies are applied, and that any new tools the district is rolling out in the fall are already installed and tested before teachers see them.
This is where instructional technology leaders need to be in the room with IT. If a school is launching a new reading platform in September, or piloting an AI writing tool, or shifting to a new LMS, the summer is the only time to configure those tools across the fleet without disrupting instruction. A September rollout of a new platform where devices weren’t pre-configured guarantees a rough first week for teachers who are already managing twenty-five different first days simultaneously.
Matthew Rivers, director of operational technology for Stratford Public Schools, makes the coordination piece explicit: “While summer is often seen as a break, our tech and facilities departments are working at full capacity. Because these two groups operate in the same buildings on very different tasks, coordination is essential.”
That coordination challenge extends to every department that touches the device lifecycle. Teachers need to communicate what broke and why. Curriculum directors need to communicate what tools are coming. Finance needs to know what the replacement budget looks like. And IT needs enough lead time to actually execute. A mid-July conversation about “we’d like to add this tool in September” is a very different situation than a mid-August one.
What Educators and Administrators Can Do Right Now
If you are a teacher, instructional coach, or department head, summer is the right time to do three things.
First, report what broke and what caused it. Not just “the screen cracked” but “six students in this class had cracked screens, and those were all students who carried devices home daily without cases.” That context helps IT and administrators make better decisions about cases, communication to families, and device care instruction.
Second, communicate what you need for fall before August. If you are planning a project that requires all students to have working cameras, say so now. If you are running a podcast unit that needs microphones, surface that. IT cannot configure or procure what they do not know is coming.
Third, if your school has summer professional development on a new tool or platform, ask your tech team whether devices will be ready. “We’ll train in August and configure in September” is a sequence that costs teachers the first two weeks of the school year to technical troubleshooting instead of instruction.
If you are a school leader or administrator, the biggest lever you have is time. IT teams that get the building access, the staffing support, and the clear communication they need in June and July are the ones who deliver a smooth September. Sandra Paul’s district moved away from full collection of all devices to a distributed system using teachers, librarians, and summer student workers to manage the process at scale. That kind of creative staffing solution only happens when leadership treats summer tech prep as a priority, not a background task.
The Quiet Work That Makes Learning Possible
There is no ribbon-cutting for a successful device rollout. When everything works on the first day of school, nobody notices. Students open their Chromebooks, teachers pull up their lesson, and the day begins.
That invisibility is the goal. The IT teams working through July heat to audit, repair, configure, and deploy devices are doing some of the most instructionally consequential work in the district. Administrators who treat that work with the same seriousness they give curriculum planning and staffing will see it in September. Those who treat it as a support function that handles itself will see that too, one broken screen and one lost login at a time.
Start the conversation in June. Ask what your fleet looks like, what is coming in the fall, and what your team needs to make it happen. September is closer than it feels.
EdTech Institute covers technology in education so teachers can focus on what matters: their students.
EdTech Institute also builds free, classroom-ready tools for teachers at RazaEd.
Source: School’s Out: Focus on Device Maintenance and Readiness for Fall (EdTech Magazine K12)