A school's guide to 1:1 device rollouts that actually work

A 1:1 device program — one laptop or tablet per student — sounds like a procurement project. In practice, it's a change-management project that happens to involve procurement. Schools that treat it as "buy devices, hand them out" run into trouble by week three. Schools that plan the support model first tend to have a program that's still running smoothly three years later.

Start with management, not hardware

Before choosing a device, decide how you'll manage it at scale. Mobile device management (MDM) software lets your team push updates, enforce content filtering, lock down settings, and remotely wipe a lost or stolen device — all without touching each device by hand. Choosing devices before you've chosen (and tested) your MDM platform is the single most common ordering mistake we see.

A rollout sequence that holds up

1. Pilot with one grade or department — surface configuration issues before they multiply across the whole school.
2. Pre-configure devices before delivery day — enrollment, apps, and restrictions should already be in place, not set up in front of students.
3. Train staff before students — teachers need to know how to manage the devices in their classroom before day one, not learn alongside students.
4. Build a repair and loaner pipeline — devices will break. Decide the turnaround process before the first cracked screen shows up, not after.
5. Set a refresh timeline — plan for the hardware's realistic lifespan (typically 3–5 years) so replacement is budgeted, not a surprise.

Network capacity is usually the hidden bottleneck

A school that could comfortably support a computer lab of 30 machines can struggle when 500 devices try to connect simultaneously at first bell. Wi-Fi capacity planning — access point density, bandwidth, and network segmentation for student devices — needs to happen alongside the device rollout, not after complaints start.

Support after launch is what determines success

The rollout isn't done when devices go home. Ongoing help desk support, a clear process for reporting issues, and a support team that understands the MDM configuration are what keep the program running through year two and year three, after the initial excitement fades.

How we help

We plan and implement 1:1 rollouts end to end: MDM selection and configuration, network capacity planning, staff training, and an ongoing support model sized to your IT team — whether that's one person or none.