For technology directors

1:1 Device Rollout Checklist for K-12 Schools (2026 Edition)

The deployment day playbook used by KBS districts running 1:1 Chromebook, iPad, and Windows programs. From board approval through first 30 days, nothing skipped.

The full rollout checklist

Four phases. Run them in order, every time.

T-90 to T-45 days

Plan the program

  • Confirm device model and quantity (with 8% loaner buffer baked in)
  • Lock funding model: parent pay, district pay, or hybrid
  • Draft AUP, damage fee schedule, and equity waiver language
  • Select coverage partner and finalize per device pricing
  • Board approval on AUP and fee schedule
  • Build the family communication calendar (email, SMS, paper, translation)

T-45 to T-15 days

Prep the building

  • Image devices, label asset tags, sync to Google Admin or Jamf
  • Train deployment team (6 to 8 staff per 500 devices per day)
  • Set up parent enrollment portal with coverage and AUP bundled
  • Send communication wave 1: program overview and dates
  • Send communication wave 2: enrollment link and how to pay
  • Pre-load loaner pool, accessories, charger inventory

Deployment day

Run the line

  • Station 1: ID check and family roster confirmation
  • Station 2: AUP signed and coverage enrollment confirmed
  • Station 3: device hand off with serial scan tied to student
  • Station 4: charger and accessories distributed
  • Station 5: photo or 60 second walkthrough
  • Station 6: help desk for translations, questions, holds

First 30 days after rollout

Lock in adoption

  • Send wave 3: how to file a claim, who to contact, what coverage covers
  • Run a claim drill so the help desk can resolve a real claim in under 5 minutes
  • Daily inventory reconcile for the first week, weekly for the rest of the month
  • Late enroller push at day 14 and day 28 to hit 90% participation
  • Capture first 30 day claim data, set the variance benchmark for the year

Hands-off rollout

Want KBS to run parent enrollment and coverage for you?

Our white glove team runs enrollment, AUP collection, claim intake, and reporting so your IT team can focus on imaging and deployment.

Deployment day staffing math

Devices to deployStationsStaffDays
Under 250451
250 – 600681 to 2
600 – 1,5006 to 810 to 122 to 3
1,500 – 5,000Multiple sites15+ rotating5 to 10
5,000+Per building rolloutBuilding IT + district team2 to 4 weeks staggered

The five things rollouts fail on

  1. 1

    Communication starts too late.

    Send the first family email 6 weeks out. Coverage enrollment dies when parents are surprised on deployment day.

  2. 2

    No equity waiver process.

    Without a clear hardship waiver, low income families opt out and the program eats those repairs.

  3. 3

    Inventory scan is skipped or batch-entered later.

    Every untracked device becomes a disputed damage claim by November.

  4. 4

    Loaner pool is too small.

    Budget 8 percent loaners minimum. Otherwise the help desk turns into a triage room.

  5. 5

    No claim drill before day one.

    Run a fake claim through the workflow. If it takes 20 minutes, fix that before 4,000 real ones hit.

Frequently asked questions

How long does a K-12 1:1 device rollout take?+

Plan 90 days for the first rollout in a district. Smaller follow up rollouts (new grade, replacement cycle) compress to 30 to 45 days once the playbook is in place.

When should we open parent coverage enrollment?+

Two weeks before deployment day. That gives parents time to read the plan, ask questions, and pay before the device leaves the building. Districts that wait until deployment day lose 20 to 30 points of participation.

Do we need an AUP for every student?+

Yes. Every student carrying a school device should sign a grade appropriate acceptable use policy and the parent should counter sign. Bundle the AUP with coverage enrollment to cut the form count in half.

What is the ideal deployment day setup?+

Stations not lines. Six tables: ID check, AUP and coverage check, device hand off, accessories, photo and inventory scan, and a help desk. A trained team of six can deploy 400 to 600 devices a day.

Should we deploy at school or send devices home in a box?+

Deploy at school for the first rollout. The 60 seconds of face time per family resolves most of the support calls you would have spent the next two weeks answering.

What is the most common rollout mistake?+

Skipping the inventory scan at hand off. Without it, you cannot prove which device went to which student, which torpedoes every damage claim and lost device case for the rest of the year.

Roll out the right way

KBS plugs into your Google Admin or Jamf fleet, runs parent enrollment, and lets your IT team focus on the work only they can do.

Used by district CTOs from 300 to 30,000 devices.