Student Device Fee Policy: A Template K-12 Districts Can Copy

Somewhere in your district there is a document that says what a family owes when a Chromebook comes back broken. It was probably written once, by someone who has since left, and it has been copied forward every August since. Nobody is certain where the numbers came from.

That document does more work than it looks like. It decides how much of your repair budget you recover, how many conversations your front office has in October, and whether a principal can answer a parent without calling you. It also tends to be the thing a board member asks about when device spending comes up.

There is no standard. Districts a county apart charge wildly different amounts for the same cracked screen, and each one arrived at its number independently. So this is the policy broken into the decisions that actually matter, with what districts publish today, and a schedule you can adapt.

What districts actually charge

Five districts publish their fee schedules openly. The spread is not small.

The same repair runs $23 in one district and $175 in another. One charges nothing the first time it happens. None of them are wrong, because they are answering different questions: Henderson County is recovering parts cost, Milford is buying administrative simplicity, Beaverton is trying to change behavior.

We went through the economics behind that spread in what it actually costs to fix a Chromebook screen. This piece is about turning a number into a policy.

The six decisions

Everything else in the document follows from these.

1. Which billing model

Four models are in common use, and the choice is mostly about what you are optimizing for.

Actual parts cost. You charge what the part cost. Defensible in a board meeting and easy to explain to a parent, and it moves with the market, which cuts both ways. Henderson County republishes annually, and you can watch the market move in it: their touch screen charge fell from $115 to $85 between 2025-26 and 2026-27 while the non-touch replacement fee rose from $369 to $411. Parts got cheaper, whole devices got more expensive. Requires you to actually track parts pricing.

Tiered by severity. Damage sorts into three or four buckets, one price each. This is the lightest model to administer, because a tech does not have to itemize a chassis with three things wrong with it. Howard County runs four tiers with a screen at $100.

Single flat rate. One number for any standard repair. Over-charges the cheap repairs and under-charges the expensive ones on purpose. Nobody gets a surprise and no tech ever prices anything.

Escalating by incident. The first one is free or cheap, the second costs more, the third costs more again. The only model that is explicitly about behavior rather than cost recovery, and the only one that requires you to know a student's full history with certainty.

Pick the model before you pick any numbers. Most policies that are hard to administer are hard because they quietly mix two models.

2. What happens the first time

Waiving the first incident is more common than people expect, and the argument for it is not softness. A student who breaks a device and expects a bill has an incentive to not report it, and an unreported broken device is one you discover in June with no history attached to it. Beaverton charges nothing the first time and $50 the second.

The argument against is equally real: a free first incident is a free first incident, and some districts find the second-incident rate climbs.

Whichever way you go, write it down explicitly. The failure mode is a policy that is silent on it and a front office improvising district by district.

3. How families who qualify are handled

This is the decision with the most downstream consequence, and the one most often left to a person rather than a policy.

The common pattern is to bill everyone and then refund or forgive on request. It leaks in both directions: families who qualify but do not ask get charged, and staff spend the fall processing reversals. It also puts a front-office secretary in the position of keeping a mental list of which families to skip.

The alternative is to waive before the charge exists, driven by the economically disadvantaged flag your student information system already carries. Our insurance and coverage module does this with OneRoster metadata mapping: you bind the SIS field to a Manage1to1 field, qualifying students get an explicit waived state instead of a premium, and no invoice is ever generated. Because it refreshes on the nightly roster sync, a family whose status changes mid-year is picked up on the next run rather than at the next complaint.

Either way, your policy needs a sentence that says what happens, not a practice that lives in someone's head.

4. Lost, damaged, and negligent are three different things

Most policies that get argued about collapse these into one number.

A damaged device comes back. A lost device does not, which means you are replacing hardware rather than a part, and the charge is a different order of magnitude. Published replacement charges in the table above run $200 to $454 against screen repairs of $23 to $175.

Negligence is the third category and the one worth defining carefully, because it is where disputes live. A device that falls out of a backpack is different from a device with a pen mark scratched into the display, and a policy that treats them identically will be challenged on the second one. Name the categories, give each a charge, and say who decides which one applies.

5. What happens when nobody pays

An unpaid device fee is not automatically a hold on a transcript, a graduation, or a schedule, and in several states it cannot be. Whatever your district's position is, the policy should state it, because the alternative is that a building secretary invents it in May.

Decide the deadline, decide what happens after it, and decide who can grant an extension.

6. Who can forgive a charge

Someone will need to. A device billed to the wrong family, a repair that came in cheaper than quoted, a principal who decides this one gets forgiven for reasons that do not fit in a policy.

The thing to avoid is forgiveness by deletion. If the way to forgive a charge is to delete the invoice, your collections numbers are fiction and an auditor has nothing to look at. Waiving in our invoicing module is its own permission-gated action: it zeroes the balance, marks the invoice Waived as a state distinct from both paid and cancelled, captures the reason, and can send the family a notice. The original invoice and its line items stay intact, so the charge, the waiver, and the person who approved it are all still there in a year.

A schedule you can adapt

This is a tiered model, which is the one most districts can administer without a parts-pricing process. Numbers are illustrative and sit near the middle of what the five districts above publish. Replace them with your own.

Paired with policy language along these lines:

Devices are issued to students for instructional use and remain district property. Families are responsible for damage beyond normal wear. The first incident in a school year carries no charge. Subsequent incidents are charged per the schedule above.

Students who qualify for free or reduced-price meals are exempt from device damage charges. No application is required; eligibility is determined from district enrollment records.

Charges are issued to the guardian on record and payable through the district payment portal. Unpaid balances do not affect a student's enrollment, schedule, grades, or participation in activities. Building administrators may reduce or waive a charge; waivers are recorded with the reason.

Devices that are not returned at the end of the school year, or on withdrawal, are charged at the replacement rate.

Three things that language is doing deliberately. It states the free and reduced exemption as automatic rather than by application, which is the difference between a policy that works and one that requires a family to ask. It says plainly what an unpaid balance does not affect, which removes the most common escalation. And it puts waiver authority somewhere specific.

What makes it workable

A fee schedule is only as good as your ability to run it in October, and two of the six decisions above quietly require capability rather than policy.

An escalating or first-incident-free model needs history you can defend. To charge nothing the first time and $50 the second, you have to answer "how many times has this happened to this student" with something a parent cannot argue with, going back years and across devices. Incident management keeps that history per device and per user, and repeat-incident thresholds surface a pattern before it becomes an argument.

Any model needs the damage recorded at the moment it arrives. Incident capture in our system is a photo flow rather than a text field: the record carries the image, the date, the device, and the student. When a family disputes a $110 charge four months later, the conversation is about a timestamped photograph rather than whose memory is better.

From there the charge becomes a family invoice from the same record, payable in the parent portal through the platform your district already uses for athletics and lunch money, and the payment posts back against the originating incident. We walk through that whole path in device damage billing.

The mistake worth avoiding

The policies that cause the most work are not the strict ones or the lenient ones. They are the ones that are silent.

Silent on the first incident, so every building handles it differently. Silent on free and reduced, so it depends who is at the desk. Silent on what an unpaid balance does, so a secretary invents a consequence in May that your district cannot actually enforce. Every one of those gaps becomes a phone call, and the phone call escalates to you.

Write the boring sentences. They are the ones that save the fall.

If you want to see the path from a cracked screen to a paid invoice on real data, book a demo and we will walk it end to end: incident capture with photos, the coverage calculation, the family invoice, and the payment posting back. Our whole team is former K-12, so we will also tell you honestly which parts of your current policy the software will not fix.