For K-12 finance and tech

Why Schools Are Moving Away From Self-Insuring Chromebooks

Self-insuring looks cheap in year one. By year three the help desk is buried, the repair line is double what was budgeted, and damage fees are getting written off because nobody has time to chase them. Here is why districts are switching.

Hidden labor cost Climbing parts pricing No risk pool

What self-insuring actually costs

On paper, self-insuring a Chromebook fleet sounds like the cheap option. There is no premium, no third party, and the technology budget already exists. The real cost shows up everywhere else: in tech hours, in loaner inventory, in unpaid damage fees, and in the equity gap between families who pay and families who quietly stop bringing the device to school.

  • Parts pricing on common Chromebook screens climbed double digits the last two years.
  • Loaner inventory ties up 5 to 8 percent of the fleet at any given time.
  • Damage fee collection rates from families typically sit between 40 and 70 percent.
  • Help desk hours spent on claim intake and repair logistics are not on the strategic plan.
  • Self-funded pools have no reinsurance, so a bad year hits the general fund.
  • Year three and four of a deployment is when repair volume spikes hardest.

Self-insured vs pooled coverage

LineSelf-insuredKBS pooled
Funding sourceDistrict repair budgetParent enrollment fee
Risk concentration100% on the districtPooled across districts and families
Loaner programDistrict-owned inventoryIncluded
Damage fee collectionCase by case, inconsistentFlat fee at enrollment
Equity guardrailManual waiversBuilt-in hardship path
Tech staff hours per claim30 to 60 minutesNear zero
ReportingSpreadsheetsQuarterly dashboard

Run the numbers

See what your self-insured fleet really costs

Share fleet size and last year's repair spend. We will model a pooled rollout against your current line and send the side by side same day.

Three signals it is time to switch

The repair line overran two years running

If the technology budget for repairs has been over by 20 percent or more two cycles in a row, the underlying model is broken. Pooling fixes the variance.

Help desk is doing claim ops, not IT

If techs are spending more than a half day a week on intake, loaners, and chasing damage fees, the district is paying salary for a workflow KBS already runs.

Damage fees create equity friction

If some families pay every time and others quietly stop bringing devices to class, the program is not really universal. A pooled fee plus hardship waiver fixes both.

Frequently asked questions

What does self-insuring a Chromebook fleet actually mean?+

The district sets aside a repair budget and absorbs every parts, labor, and loaner cost in-house. There is no third-party coverage, no risk pool, and damage fees are collected case by case from families.

Why are districts moving away from it?+

Three reasons: repair costs are climbing faster than budgets, fee collection from families is inconsistent and inequitable, and IT staff hours spent on claim ops are hours not spent on instruction or strategy.

Is pooled coverage really cheaper?+

For most fleets over 1,000 devices, yes. The per-device flat fee in a parent-pay pool is typically lower than the loaded cost of one in-house claim, and the district line item drops to zero.

What happens to families who cannot afford a fee?+

KBS deployments include a hardship waiver path that mirrors free and reduced lunch eligibility. Coverage stays universal and the district does not have to fund the exception.

How fast can we switch from self-insured to pooled?+

Most districts go live inside a single back-to-school window. Kickoff to first covered claim is typically four to six weeks.

Stop carrying the risk on your own balance sheet

A 10 minute call. We model your current repair spend against a pooled rollout and send the math back the same day. No commitment.