Skip to content
Request an assessment

Industries · Education

Eight weeks to retire four years of devices

Education disposition is not hard because the devices are complicated. It is hard because everything ends simultaneously, half of it is unaccounted for, and the window closes when school starts.

The real problem

A one-to-one program is a disposition program with a four-year delay

When a district issues devices to every student, it also commits to collecting, sanitizing, accounting for and disposing of every one of them at the end of the cycle. That second half is rarely budgeted, rarely staffed, and almost never planned until the year it arrives.

By then the register is out of date, the summer is short, and the technology department is also deploying the replacement fleet.

The districts that handle this well do one thing differently: they treat collection and reconciliation as a scheduled project with named sites and dates, months before the last day of school — and they scope recovery value early enough for it to influence the purchase.

Failure modes

Four ways education refresh programs come apart

The whole fleet ends at once

District device programs are bought in cohorts and they die in cohorts. Thousands of units reach end of support in the same year, and the window to collect, sanitize, reconcile and redeploy them is the eight weeks when buildings are empty. A provider whose capacity is fine in November is not necessarily fine in July.

Nobody is sure what is still out there

Devices go home with students and staff and do not all come back. By year four the asset register and physical reality have diverged, and the gap is discovered at disposition — which is the worst possible time, because a device you cannot account for is a device you cannot certify was wiped.

FERPA-covered data on machines nobody classified as sensitive

Cached gradebook sessions, locally saved IEP documents, SIS credentials, staff email, photographs. A student device is not a clean slate because it was managed, and "the MDM wiped it" is a claim about a management console, not evidence about the storage medium.

Value is treated as an afterthought

Retired education fleets are frequently given away or scrapped on the assumption that a four-year-old Chromebook is worth nothing. Some are worth little. Many are not, and functional units placed properly can fund a meaningful share of the next purchase. Districts routinely leave that money on the table because nobody scoped it.

How a district program runs

Planned in spring, executed in summer, settled before the first bell

Reconciliation happens per building, because a district-level total conceals exactly the discrepancies you need to see.

  1. 01

    Pre-summer planning

    Cohort identified, collection sites and dates agreed, packaging staged, asset register exported as the baseline for reconciliation.

    Produces
    Collection plan and baseline register
  2. 02

    Collection

    Site-by-site pickup on the agreed calendar, counted and signed at each building rather than aggregated into one district total.

    Produces
    Per-site chain-of-custody receipt
  3. 03

    Intake and reconciliation

    Physical count reconciled against your register per site. Variances are reported by building, not absorbed.

    Produces
    Variance report by location
  4. 04

    Sanitization

    Sanitization to NIST 800-88, with a certificate issued per device carrying serial, method, operator, timestamp and validation hash.

    Produces
    Per-device erasure certificate
  5. 05

    Disposition and settlement

    Functional units tested, graded and remarketed; unusable material recycled downstream under manifest. Recovery reported back against the register.

    Produces
    Settlement and recycling report

Higher education

Universities have the opposite problem

Where K-12 estates are uniform cohorts that end together, higher education estates are the reverse: heterogeneous, departmentally owned, procured on different cycles, and frequently invisible to central IT until something is decommissioned.

Research computing makes it sharper. Lab workstations, storage arrays and GPU nodes hold data whose sensitivity ranges from published to grant-restricted to human-subject, and the disposition record has to be defensible to a research compliance office, not just to procurement.

The practical approach is the same as for a district — reconcile at the level where accountability actually sits — but the unit is the department or lab rather than the building, and the value profile is very different. A retiring research server can be worth considerably more than an entire cart of student laptops.

FAQ

What technology directors ask

Does using your service make our district FERPA compliant?
No. FERPA obligations belong to the educational agency and cannot be transferred to a vendor — treat any provider selling "FERPA-compliant disposition" with suspicion. What we provide is the sanitization records and reconciled asset accounting your technology director and records officer use to demonstrate that student data was properly disposed of under your own policy.
Can you handle the whole fleet inside the summer window?
That is the planning conversation, and it should happen in spring rather than June. Our facility runs surge staffing that supplements the core team within 24 to 48 hours under the same background screening, and modular workstations let a dedicated zone be stood up inside a day. What makes a summer program work is a collection calendar agreed in advance, not raw capacity.
What about devices that were never returned?
They appear as variances on the per-site reconciliation, which is the point of reconciling by building rather than by district. You cannot certify a device you never received, and a report that quietly nets missing units against found ones is not evidence — it is arithmetic that hides the problem.
Do you wipe Chromebooks differently from Windows laptops?
The sanitization profile follows the media, not the badge on the lid. Managed Chromebooks, Windows laptops with SSDs, older machines with spinning disks and iPads all have different appropriate methods, and the certificate records which method was used on which serial. Deprovisioning a device in an admin console is a management action, not a sanitization record.
What is a four-year-old student device actually worth?
It depends entirely on the model, condition and how many of them there are. Some cohorts recover meaningfully; some are worth handling costs and no more. We will tell you which before you commit, based on the actual model mix, rather than promising a percentage that sounds good in a proposal.
Can recovered value be applied to new equipment?
Yes, and that is usually the sensible structure. Because we also handle procurement and deployment, recovery from a retiring cohort can be applied against the incoming one, and a buyback position can be agreed at purchase rather than negotiated at end of life from a weaker footing.
Do you handle deployment as well as disposition?
Yes — asset tagging, imaging, MDM enrolment and kitting, delivered so that devices arrive ready to hand to a student. Districts running both directions through one provider get a single asset record across the whole cycle instead of two systems that disagree by year three.

Plan the summer in the spring.

Send us the cohort, the sites and the dates. We will come back with a collection plan and a realistic view of recovery.

Request an assessment (469) 718-0004