Your Chromebooks Have an Expiration Date. Plan the Fleet Around It.

01 / THE DATEEvery Chromebook model carries an expiration date

Every Chromebook model has an Auto Update Expiration (AUE) date: the month Google stops shipping ChromeOS updates to it. Since Google’s September 14, 2023 announcement, the window is ten years from the platform’s release date. That is the release date of the hardware platform the model is built on, not the date your district bought it. A model purchased in 2022 on a platform released in 2019 runs on the 2019 clock.

How the ten years arrive depends on the platform’s age:

• Platforms released in 2021 or later receive the full ten years automatically.
• Eligible platforms released before 2021 get their extra years only if an administrator opts in. In the Admin console the setting is under Devices → Chrome → Settings → Device settings → Device update settings → Extended Auto-update. Opting in removes the Google Play Store, erases Android data, and ends Android app support on those devices, and Google notes that some features and services might not be supported. That makes it a curriculum decision as much as an IT one: if a class depends on an Android app, extended updates take it away.

When the date passes, the device still powers on. What changes is the guarantee. Google’s Auto Update policy warns that after the final update, existing and future policies may not work as intended and technical support will not be provided. For a managed school fleet, an unpatched device that management policies may stop controlling is a device that has reached a retirement decision.

02 / FOUR CLOCKSWhy the AUE date is only one of the deadlines

Districts bought Chromebooks in waves, and the pandemic wave was the largest. The U.S. PIRG Education Fund’s 2023 Chromebook Churn report counted more than 31 million Chromebooks sold globally in the first year of the pandemic, and school IT staff it interviewed said the devices typically last about four years. A fleet of that age runs on four clocks at once:

The testing clock is the one that tends to surprise people, because it arrives in spring with no warning in the Admin console. Assessment vendors publish supported ChromeOS versions each year. A DRC device-support notice that Wisconsin’s Department of Public Instruction posted for 2023–24 is a typical example: ChromeOS versions below stable channel 109 would fail DRC’s System Readiness Check and be blocked from running its testing software. A device past its AUE date can no longer climb to newer versions, so sooner or later it lands below the line.

The funding clock matters for devices bought through the FCC’s Emergency Connectivity Fund. Under 47 CFR 54.1713, equipment bought with that support may not be sold or transferred for value until it is at least three years old, at which point the rule treats it as obsolete and allows it to be resold, donated, traded, or disposed of. Under 47 CFR 54.1715, participants must keep program records for at least ten years from the last date of service or equipment delivery, including a serial-level asset inventory of every device: who received it and when it was loaned out and returned, or, for shared devices such as carts, the responsible employee and the dates in service. Devices bought with other federal grants fall under the Uniform Guidance (2 CFR 200) and your state’s rules; a single Chromebook typically falls below the 2 CFR 200.1 equipment threshold (the lesser of your capitalization level or the federal limit), but your board’s surplus-property policy still governs any sale or donation. Check with the business office before the truck is booked.

03 / THE RETIREMENT LISTBuild it from the Admin console, not from memory

The fleet data you need already exists. In the Google Admin console, the Chrome Insights report (Devices → Chrome → Reports → Insights) includes a chart of devices receiving their last automatic update by month. Hover over a month to see the model breakdown, and click it to list the devices reaching their last update that month. Reporting must be turned on, and new data can take up to 24 hours to appear.

Turn that list into retirement waves by adding four columns per serial:

1. AUE date, and for pre-2021 platforms whether you will opt in to extended updates (and lose Android apps) or retire on the original date.
2. Condition and repair history: battery health, open repair tickets, and whether parts for that model are still in your repair pool.
3. Testing fitness: whether the device can run the version your assessment vendor will require next spring.
4. Funding source and age: Emergency Connectivity Fund, other federal grant, or district funds; for ECF devices, the delivery date (which starts the three-year resale clock) and your last ECF service or delivery date (which starts the ten-year records clock).

The natural collection window is the end of the school year, when devices come back in for summer anyway. Plan the replacement purchase and the retirement in the same wave so the old units never sit in a storage closet over the summer. Our Refresh Wave Planner turns a device count and a deadline into a wave schedule you can export to a calendar.

04 / DEPROVISION FIRSTA managed Chromebook still belongs to your domain

A Chromebook enrolled in your Google Admin console stays tied to your organization even after it is factory reset. Google’s guidance for selling managed devices is direct: the only way to completely remove administrative control is to deprovision the device from your account. A device that hasn’t been deprovisioned won’t enroll in another organization (the buyer sees that it is marked for management by a different organization), and Google notes that it can’t be fully tested and repaired. Skip this step and a reusable device becomes a parts unit.

• Pick the right reason. Use Retiring from fleet when you are reselling, donating, or permanently removing devices. Same model replacement is for warranty and RMA swaps. Upgrades bundled with a device can’t be transferred to another device.
• Choose the factory reset. Deprovisioning lets you factory reset at the same time, removing user profiles, device policies, and enrollment data. If you don’t, wipe the device afterward.
• Get the devices online. Deprovisioning only takes effect when the device connects to the internet. Devices sitting dead in a cart will not pick it up, so charge and connect them before the collection date.
• Don’t confuse disable with deprovision. Disabling is for lost or stolen devices; a disabled device stays enrolled in your organization. Retiring devices should be deprovisioned, not disabled.

Management locks are a common reason school devices arrive at a recycler unusable. Our brief on BIOS, MDM, and Activation Locks covers the same problem across Windows, Mac, and mobile fleets.

05 / THE DATAWhat is actually on a student Chromebook

Most student work lives in the cloud, which leads some districts to treat retired Chromebooks as data-free. They aren’t. A shared cart device can hold sign-in profiles for every student who used it, downloaded files, offline documents, cached data, Android app data, and saved Wi-Fi credentials. Google encrypts user data at rest with keys protected by the device’s security chip, and describes Powerwash (the factory reset) as a cryptographic erase that clears those keys. Google also notes that a Powerwash does not necessarily erase every trace of user data: an encrypted remnant, a copy of the operating system, diagnostic data, and the device’s enterprise enrollment can remain, and data stored in the cloud has to be deleted separately.

FERPA itself prescribes no destruction method. The Department of Education’s Privacy Technical Assistance Center recommends NIST SP 800-88 Clear, Purge, or Destroy, signed certification forms, and contracts requiring third parties to destroy student data. For a Chromebook fleet that means:

• Working devices: deprovision with a factory reset, then record the method (cryptographic erase via Powerwash), the date, and the serial in your disposition log.
• Dead devices: a Chromebook that won’t boot can’t run a Powerwash. Many education models store data on flash memory soldered to the motherboard, so there is no drive to pull and wipe separately. Send those units to physical destruction and get a certificate that lists them by serial.
• Student accounts: the cloud side is an account-lifecycle task in Google Workspace for Education, handled under your records retention schedule, not by the device.

The FERPA field guide covers the full disposal framework, and the NIST SP 800-88 Rev. 2 field guide covers how to document a sanitization program.

06 / WHERE THEY GOReuse, harvest, recycle, in that order

A Chromebook past its AUE date still has useful parts, and a Chromebook retired for condition or model consolidation while it is still inside its update window may still have a second life. Sort retired units into three streams:

• Reuse: devices still inside their update window, deprovisioned and in working order, can be remarketed or donated, if your funding terms and board policy allow it. Donating a device past its AUE date hands the recipient an unsupported computer; say so, or don’t donate it.
• Harvest: PIRG found that Chromebook parts are hard to source and often change between models. Retiring units of the same model you still run are the best source of keyboards, screens, and chargers for your repair pool.
• Recycle: everything else goes to a certified recycler. Each unit holds a lithium-ion battery, so carts of retired Chromebooks should be stored and shipped under battery rules. Our battery disposition field guide covers handling and shipping.

Whichever stream a device takes, the record should close the loop: one line per serial showing the deprovision date, the sanitization method or destruction, and the final disposition. For Emergency Connectivity Fund devices, that line is what makes the ten-year asset inventory complete.

07 / THE CHECKLISTBefore the summer collection

1. Pull the Insights report and list every serial reaching its last automatic update in the next 24 months.
2. Decide extended updates for each pre-2021 model, with the curriculum team in the room if Android apps are in use.
3. Check next spring’s assessment requirements against each model.
4. Tag every serial with its funding source and delivery date; confirm sale and donation rules with the business office.
5. Schedule the replacement purchase and the collection in the same wave.
6. Charge, connect, and deprovision with Retiring from fleet and a factory reset.
7. Separate dead units for physical destruction; separate same-model units for parts.
8. Keep a per-serial disposition record and file it with the asset inventory.

08 / FAQChromebook end-of-life FAQ

This brief reflects public sources as of October 15, 2026, including Google’s published ChromeOS Auto Update policy and Admin console help, the U.S. PIRG Education Fund’s 2023 Chromebook Churn report, DRC’s 2023–24 Chrome OS Device Support notice (posted by the Wisconsin Department of Public Instruction), and the FCC’s Emergency Connectivity Fund rules at 47 CFR 54.1713 and 54.1715. Admin console menus and assessment requirements change; check current documentation. It is general information, not legal advice: funding terms, state law, and board policy decide what a district may sell or donate, so confirm them with your business office and counsel. CyberCrunch credential statements reflect certificates held at the time of publication.