How Education Works | School Technology Fleet & Device Lifecycle Management

HEW-NODE-0103 · How Education Works · school device fleets, endpoint lifecycle, inventory, configuration, mobile-device management, repair, spares, charging, support, replacement, accessibility, sustainability and responsible retirement

A school can successfully buy a thousand devices and still fail to create a thousand usable learning tools.

The purchase order closes. The boxes arrive. Photographs are taken. The programme is announced.

Then the quiet work begins: devices must be recorded, configured, assigned, charged, updated, secured, connected, supported, repaired, cleaned, recovered, replaced and eventually retired. Passwords are forgotten. Chargers disappear. Batteries weaken. Screens crack. Operating systems reach end of support. A learning application stops running on older hardware. A student changes school. A teacher needs a replacement before tomorrow’s lesson. A device returns with no obvious owner. A family has broadband but no suitable keyboard. A wheelchair user needs a different input arrangement. A school has enough devices on paper and too few functioning devices at 8:00 Monday morning.

School technology fleet management works when the education system treats every device as a continuing service obligation—from specification and enrolment through daily support, repair, security, accessibility, replacement and responsible disposal—rather than as a one-time purchase.

This article sits beside the How Education Works hub, Education Procurement, School Connectivity, Education Cybersecurity & Digital Service Continuity, Education Data Privacy & Student Records Governance, School Electrification & Energy Reliability, Open Educational Resources & Open Licensing and School Estate Asset Registers & Lifecycle Planning.

Those pages keep their jobs. Procurement owns the purchasing process. Connectivity owns the network path that lets devices reach digital services. Cybersecurity owns wider security, resilience and continuity. Data Privacy owns governance of learner and staff information. Electrification owns usable power. Open Educational Resources owns reusable learning content. School Estate Asset Registers owns the broader physical-asset picture.

This node owns the adjacent endpoint layer: how a school or education system turns purchased laptops, tablets and related learning devices into a dependable fleet by controlling identity, configuration, assignment, support, repair, spares, warranties, batteries, accessories, accessibility, replacement timing, data erasure and end-of-life handling.

The 50-Second Read

Buying devices is the start of a service, not the end of a project.
Count functioning, assigned and supportable devices—not only devices purchased.
Every device needs an identity in the inventory before it disappears into classrooms and homes.
Standardisation reduces support cost, but excessive uniformity can create accessibility or subject-fit problems.
Configuration should be automated wherever scale makes manual setup unreliable.
Mobile-device or endpoint management can enforce updates, settings, applications and security policy remotely.
Device ownership, user identity and data ownership are different questions and should not be confused.
Charging is infrastructure. A device with no reliable charging route is not reliably available.
Repair turnaround determines instructional availability more directly than the headline number of devices purchased.
Keep spares. Waiting weeks for repair while every student technically “has a device” is a paper success.
Warranty terms matter only if schools know how to claim them and have a replacement path while the claim is processed.
Batteries are consumables with a different life curve from many other components.
Accessories—chargers, cases, styluses, keyboards, headphones and adapters—need their own stock and replacement rules.
Accessibility should be specified before procurement and checked again after configuration.
Software compatibility and operating-system support dates influence hardware replacement.
Help desks need triage, service-level targets and escalation routes rather than a shared inbox nobody owns.
Lost or stolen devices require identity, remote action and clear reporting.
Bring-your-own-device policies do not remove fleet management; they move part of it into compatibility, security and equity governance.
Responsible retirement requires secure data erasure, reuse where sensible, and lawful e-waste handling.
Total cost of ownership includes support, licences, repairs, accessories, connectivity, power, staff time and replacement—not only purchase price.

One-Sentence Definition

School technology fleet and device lifecycle management is the operating system that keeps digital learning endpoints identifiable, configured, secure, accessible, charged, supported, repairable, replaceable and responsibly retired throughout their useful life.

A Device Is a Learning Service Endpoint

A laptop is not educational simply because it sits in a school.

It becomes part of an education service only when it can run the required tools, reach the network, authenticate the user, preserve appropriate security, survive the school day, accept accessible input, receive updates and obtain support quickly enough that teachers can plan around it.

The unit of success is therefore not possession. It is dependable usability.

The Inventory Must Exist Before Distribution

Large rollouts can lose control within days if devices are distributed before asset identity is established.

Each device should have a unique inventory record tied to serial number, model, purchase batch, warranty, configuration state and current custodian or location as appropriate. The record should survive changes in user and repair status.

A sticker alone is not an asset system. The label and the digital record must agree.

Know the Difference Between an Asset Register and an Endpoint Console

An asset register answers: what do we own, where is it, what did it cost, what is its lifecycle state?

An endpoint-management system answers: is the device online, configured, encrypted, updated, compliant and running the required applications?

The two systems may integrate, but they serve different operating questions.

Standardisation Is a Support Strategy

A fleet containing twenty laptop models, four charging standards, five operating-system versions and several incompatible accessory ecosystems creates hidden support cost.

Standardising a small number of approved configurations simplifies imaging, spares, repair, training and troubleshooting.

But standardisation should not become rigidity. Different age groups, subjects, accessibility needs or vocational programmes may require different device profiles.

Choose a Device Profile for the Work

The right endpoint depends on the educational job.

Reading and lightweight classroom tasks may favour portability and battery life.
Programming, design, simulation or media work may require more processing power and storage.
Young learners may need durability, simplified login and touch interaction.
Examination use may require locked-down environments and specific compatibility.
Assistive access may require ports, screen size, external switches, alternative keyboards or specialised software.

Procurement should therefore begin with the learning workload and the support model rather than the most visible specification.

Configuration at Scale Should Be Automated

Manually configuring every device may work for twenty laptops. It becomes fragile at twenty thousand.

Modern fleet management can enrol devices automatically, apply security settings, deploy applications, configure Wi-Fi and update policy remotely. Automation reduces variation and makes replacement faster because a new device can inherit the standard configuration without days of technician work.

Identity Is the Control Plane

A device often needs to know who is using it before the correct applications, permissions and data become available.

Account provisioning, authentication and role assignment should therefore be designed with device rollout. A tablet that works only when one administrator knows a shared password is not scalable infrastructure.

Identity governance should also anticipate arrivals, departures, transfers and role changes.

Device Ownership Is Not Data Ownership

A school may own the laptop while a learner owns rights in personal data stored or accessed through it. A family may own a BYOD device while the school legitimately controls access to its network and applications.

Policies should separate property rules, account rules, monitoring rules and data rules instead of assuming one answers the others.

Charging Is Part of the Architecture

One-to-one programmes often assume the battery will arrive full.

Reality is less cooperative. Students forget chargers. Homes have uneven power access. Shared devices return to carts half charged. Old batteries no longer last a full day. Classrooms may not have enough safe outlets.

Charging plans can include home charging, secure classroom charging, central carts, spare chargers, power banks where appropriate and battery-health monitoring. The correct design depends on how devices move through the day.

Battery Health Is an Availability Metric

A device can pass every software check and still be operationally useless because the battery lasts forty minutes.

Battery capacity degrades differently from many other components. Lifecycle budgets should include battery replacement where technically and economically sensible rather than treating battery failure as an unexpected event.

Accessories Are Part of the Fleet

Chargers, keyboards, styluses, cases, headphones, adapters and accessibility peripherals are often procured as afterthoughts and managed even more weakly.

Yet a missing $20 charger can remove a $600 device from service. Accessory stock, compatibility and replacement should be planned as operational inventory.

Cases and Durability Are Economic Decisions

A cheaper device with frequent breakage can be more expensive than a more robust device with a higher initial price.

Protective cases, reinforced hinges, spill resistance, repairable keyboards and replaceable parts may reduce total cost where devices move daily through backpacks, buses and crowded classrooms.

The Help Desk Is Part of Instructional Time

If a teacher spends fifteen minutes of a forty-minute lesson troubleshooting logins, the technology programme has consumed learning time.

Support design should therefore be judged partly by how quickly ordinary problems are removed from classrooms.

Define Support Tiers

Tier 0: self-service guidance for common issues.
Tier 1: front-line school support for password resets, basic configuration and common device faults.
Tier 2: specialist technical support for deeper operating-system, management or network issues.
Tier 3: vendor, warranty or advanced engineering escalation.

Not every system needs those exact labels. It does need an agreed route so users know where a fault goes next.

Service-Level Targets Turn Support Into a Measurable Service

“We will fix devices as soon as possible” is not operationally useful.

Define target response and resolution times by severity. A teacher device needed for tomorrow’s national assessment may require a different priority from a cosmetic crack on a spare tablet.

Keep Spares Close Enough to Matter

A repair process can be excellent and still take several days.

Spare pools maintain continuity. The school can swap the failed device, preserve instructional access and repair in the background.

The correct spare ratio depends on failure rates, repair time, geography and the criticality of devices. The principle is universal: availability requires redundancy.

Repair Turnaround Is a Better Metric Than Repair Count

A support centre can close many tickets and still leave students without devices for too long.

Track time out of service, repeat repairs, first-time-fix rate and percentage of users receiving a loan device where policy requires one.

Repairability Belongs in Procurement Specifications

Lifecycle management begins before purchase.

Systems should consider availability of parts, service manuals, authorised repair options, warranty turnaround, modularity, battery replacement, keyboard replacement and vendor support period. A device that cannot be repaired economically may have a much shorter real life than the brochure suggests.

Warranty Is a Workflow, Not a Clause

A warranty has little value if staff do not know which faults qualify, how to file claims, where devices are sent, who pays shipping and what happens to the learner while the device is away.

Warranty administration should be integrated with ticketing and asset records so recurring defects can also be identified at fleet level.

Track Failure Patterns by Model and Batch

If one model develops hinge failures after eighteen months, the information should influence future procurement and warranty claims.

Fleet data becomes a learning system when repair history changes the next buying decision.

Updates Need Governance

Operating-system and application updates improve security and functionality but can also break compatibility or disrupt examinations if applied at the wrong moment.

Use staged deployment where scale justifies it: test on a small group, monitor, then expand. Critical security updates may require accelerated action, but even urgency benefits from controlled rollout where possible.

Unsupported Operating Systems Are a Lifecycle Event

A laptop does not stop turning on when its operating system reaches end of support.

But the security and application ecosystem begins to narrow. Replacement plans should therefore consider vendor support timelines and application requirements, not merely physical failure.

Application Portfolios Need Lifecycle Control Too

Schools accumulate software easily. A trial becomes a subscription. A teacher leaves but the licence remains. Two departments buy tools that solve the same problem. An old application requires a legacy browser.

Device management should connect with application governance: approved tools, licence counts, pedagogical owner, privacy review, support responsibility and retirement decision.

Security Baselines Should Be Boring and Automatic

Encryption, screen-lock policy, update compliance, endpoint protection, restricted administrative rights and device-management enrolment should not depend on every user remembering to configure them correctly.

The wider threat, incident and continuity architecture belongs to Education Cybersecurity & Digital Service Continuity. This page owns the fleet-level implementation of those controls on devices.

Lost and Stolen Devices Need a Defined Response

Users should know how quickly to report loss, which team records the incident, whether remote lock or wipe is available, when police or insurance notification is required and how the learner continues schoolwork meanwhile.

A missing device is simultaneously an asset event, a security event and potentially a data event.

Do Not Turn Monitoring Into Invisible Surveillance

Management tools can provide powerful visibility into school-owned devices. Capability does not automatically create justification.

Schools should define what monitoring is necessary, lawful and proportionate, inform users appropriately and separate security telemetry from intrusive observation of student behaviour. Data governance belongs with Education Data Privacy & Student Records Governance.

Accessibility Must Survive Configuration

A device may be technically capable of screen reading, captions, magnification, alternative input or speech recognition while school restrictions accidentally block the feature.

Accessibility settings and compatible peripherals should be tested in the managed environment actually used by students, not only on an unrestricted demonstration unit.

Assistive Devices Need Higher Continuity

For some learners a standard laptop is helpful. For others a configured device is the primary communication, reading or writing route.

Failure therefore has unequal consequences. Critical assistive endpoints may require faster repair, dedicated spares or backup communication methods. The learner-specific planning sits with Inclusive Education Needs Identification & Individual Support Planning.

BYOD Changes the Boundary, Not the Need for Governance

Bring-your-own-device programmes reduce some public hardware cost but create variation in operating system, screen size, battery health, security capability and family purchasing power.

A BYOD policy needs minimum technical standards, supported platforms, network controls, equity provision for students without suitable devices, examination rules and a clear line between school and family support responsibilities.

Shared Devices Have a Different Operating Model

Shared carts can be efficient when devices are needed for selected lessons rather than continuously.

They create scheduling, charging, cleaning, authentication and storage challenges. A cart with thirty devices is useless to the fourth class if the first three leave them uncharged or logged into previous accounts.

One-to-One Programmes Shift Responsibility Toward the User

When a device travels between school and home, policies need to address care, acceptable use, family support, damage, loss, insurance or liability arrangements, home connectivity and return when enrolment ends.

The programme should distinguish reasonable care expectations from punitive policies that push families away from using the device.

Home Connectivity Can Nullify Device Equity

Equal devices do not create equal digital access when home bandwidth, data cost, quiet study space and shared household use differ.

Offline capability, downloadable resources, local caching, loan hotspots where appropriate and flexible submission arrangements may be necessary. The network infrastructure itself belongs to School Connectivity.

Teacher Devices Are Operationally Critical

A classroom may have student devices but still depend on one teacher laptop for presentation, attendance, assessment, communication and access to planning resources.

Teacher-device failure can therefore affect many students at once. Priority and spare strategies should reflect the blast radius of failure.

Computer Laboratories Remain a Fleet Model

Not every education system is moving to one-to-one devices. Fixed laboratories can still provide concentrated access, especially for specialised software or contexts where device security and maintenance favour centralisation.

The lifecycle principles remain: identity, configuration, updates, spares, support, replacement and power.

Total Cost of Ownership Changes the Procurement Conversation

Purchase price is visible because it arrives on one invoice.

Lifecycle cost is scattered across years and budgets: licences, management tools, help desk, technicians, batteries, screens, chargers, cases, network upgrades, teacher training, insurance, storage, electricity, replacement and disposal.

A cheaper device can be expensive to own. A more expensive device can also be poor value if its educational use is weak. Cost must stay connected to learning purpose.

Replacement Should Be Condition-Based Where Possible

Replacing every device on the same birthday is simple but can retire usable equipment prematurely or keep heavily used equipment too long.

Systems can use a combination of age, security support, battery health, failure history, performance requirements and repair economics to decide replacement. Fleet standardisation may still justify cohort replacement where operational simplicity has value.

Plan the Replacement Wave Before It Arrives

Large one-time rollouts create large future replacement liabilities.

If 100,000 devices are bought in one year, the system should already be modelling what happens when a large share reaches end of useful life within a narrow window. Sustainable programmes convert capital excitement into recurring budget discipline.

Reuse Can Extend Value

A device no longer suitable for demanding classroom workloads may still serve a lighter administrative, library or training function.

Internal redeployment can extend useful life if security support and performance remain adequate. Reuse should be deliberate, not a way of moving obsolete risk to less powerful users.

Secure Data Erasure Comes Before Disposal

Devices may contain cached credentials, local files, browser data or configuration secrets.

Retirement procedures should remove the device from management systems, revoke relevant access, erase data using an appropriate method and record the asset disposition before sale, donation, recycling or destruction.

E-Waste Is an Education-System Responsibility

Technology programmes can create large streams of batteries, screens, cables and electronics.

Responsible lifecycle management should follow applicable environmental rules, favour certified reuse or recycling channels where available and avoid simply transferring unusable equipment to communities that lack safe disposal routes.

Measure Educational Availability, Not Just Technical Uptime

A device can be powered on yet educationally unavailable because the required app will not run, the account cannot authenticate, the charger is missing or the battery dies before the lesson.

Useful fleet metrics should therefore include end-user availability and time lost to faults, not only server-style uptime.

Technology Must Still Earn Its Place in Learning

Excellent fleet operations can keep devices available. They cannot prove the devices improve learning.

Teachers and system leaders still need to ask whether a digital tool improves access, feedback, practice, creation, simulation, communication or some other legitimate educational outcome. A perfectly managed distraction remains a distraction.

Case Study: The Thousand Laptops With 730 Chargers

Invented example: a district buys one thousand laptops for secondary students. After eighteen months, inventory shows 963 laptops physically present but only 811 regularly usable. The largest single cause is not motherboard failure. It is missing or damaged chargers and batteries that no longer last through the day.

The district creates an accessory stock, standardises replacement chargers, records battery health and adds charging stations in high-use areas. Usable-device availability rises without buying a new laptop cohort.

The lesson: small lifecycle components can control the availability of expensive assets.

Case Study: The Warranty That Took Three Weeks

Invented example: devices carry a three-year warranty, but every repair requires shipping to a central depot. Students receive no loan device. The programme reports a low device-failure rate while affected students lose weeks of access.

The next contract includes on-site diagnosis, defined turnaround targets and a vendor-supported spare pool. Fleet metrics begin reporting user-days unavailable rather than warranty claims alone.

The lesson: a warranty protects value only when the service path protects learning continuity.

Case Study: The Update That Broke Monday

Invented example: a new operating-system release is pushed automatically to the entire fleet over the weekend. On Monday, an examination application fails on the new version.

The system introduces deployment rings: technical test devices, pilot schools, then general release. Examination periods receive controlled change windows unless urgent security needs override them.

The lesson: updates are necessary, but uncontrolled change is an availability risk.

Case Study: The Accessible Feature That Policy Disabled

Invented example: a student relies on speech recognition. A new security baseline disables microphone access for a broad application category. The device remains compliant but the learner cannot complete written work independently.

The technology and inclusion teams create an approved exception profile tied to the learner’s managed account, test it before rollout and add accessibility regression checks to future configuration changes.

The lesson: security, accessibility and learning have to be engineered together.

Failure Mode 1: Count Devices Purchased

The programme reports inventory volume rather than usable learning capacity.

Repair: measure functioning, assigned, compliant and available devices.

Failure Mode 2: Distribute Before Enrolment

Asset identity and control are lost immediately.

Repair: register, configure and verify devices before handover.

Failure Mode 3: Buy the Cheapest Hardware

Repair, battery and support costs overwhelm the initial saving.

Repair: compare total cost of ownership and the educational workload.

Failure Mode 4: No Spare Pool

Every hardware fault becomes lost learning time.

Repair: size spares according to failure rate and repair time.

Failure Mode 5: Warranty Without Workflow

Staff do not know how to claim support or users wait too long.

Repair: integrate claims, logistics, replacement and asset records.

Failure Mode 6: Ignore Accessories

Cheap missing components disable expensive devices.

Repair: manage chargers, cases, keyboards and accessibility peripherals as fleet inventory.

Failure Mode 7: Apply Every Update Everywhere

A configuration change creates system-wide disruption.

Repair: use staged rollout, test groups and change windows.

Failure Mode 8: Treat BYOD as Free Infrastructure

Family purchasing power becomes device quality and support inequality.

Repair: define standards, equity provision and supported boundaries.

Failure Mode 9: Replace Only When Devices Die

Unsupported operating systems and declining batteries create hidden risk before physical failure.

Repair: plan replacement using support status, condition, performance and repair economics.

Failure Mode 10: Throw Away the End of the Programme

Data, environmental responsibility and asset accountability disappear at retirement.

Repair: erase, record, reuse where appropriate and recycle through responsible channels.

The Device Lifecycle Chain

Define the educational workload. Know what the device must actually do.
Specify lifecycle requirements. Include support period, repairability, accessibility and management capability before purchase.
Procure using total cost thinking.
Register every asset. Create durable identity before distribution.
Enrol into management. Apply standard configuration and security.
Assign to user or location. Record custody appropriately.
Provide accessories and charging. Make daily use physically possible.
Train users. Cover care, login, basic troubleshooting and reporting.
Operate tiered support. Make the fault path clear.
Maintain spares. Protect continuity while repairs happen.
Track repair and warranty performance.
Monitor battery and component health.
Stage updates and configuration changes.
Audit security and accessibility compliance.
Forecast replacement. Use support dates, condition and educational requirements.
Redeploy where appropriate. Extend useful life without exporting risk.
Erase data and de-register endpoints.
Retire responsibly. Sell, donate, recycle or dispose under controlled rules.
Feed lifecycle data back into the next procurement.

A School Device Fleet Dashboard

devices purchased;
devices received and asset-tagged;
devices enrolled in management;
devices currently assigned;
functioning-device rate;
device-to-learner ratio by actual availability;
average battery health;
devices reaching operating-system end of support;
devices below minimum application requirements;
open repair tickets;
mean time to repair;
median user-days unavailable;
first-time-fix rate;
repeat-failure rate;
spare-pool utilisation;
warranty claim turnaround;
repair cost by model and batch;
lost or stolen devices;
remote lock or wipe success where used;
missing accessory rate;
charger stock;
help-desk response time;
ticket volume per 100 devices;
software-compliance rate;
security-patch compliance;
accessibility exceptions requiring support;
BYOD users requiring equity provision;
replacement forecast by year;
retired devices securely erased;
devices reused or redeployed;
e-waste processed through approved channels;
estimated total cost per usable device-year.

A Practical Fleet Management Protocol

Define supported device families and the learning workloads they serve.
Require asset identity, endpoint enrolment and security configuration before handover.
Maintain one source of truth for custody and lifecycle state.
Automate standard configuration where scale justifies it.
Use named ownership for application, device and support policies.
Publish simple user guidance for common faults.
Maintain a school-level or regional spare strategy.
Track chargers and critical accessories.
Measure battery health rather than waiting for complaints.
Integrate warranty claims with ticket and asset records.
Review model-specific repair patterns before the next procurement.
Stage operating-system and configuration changes.
Protect examination periods with controlled change where appropriate.
Test accessibility features under the managed configuration.
Define BYOD minimum standards and equity arrangements.
Separate asset monitoring from unnecessary user surveillance.
Forecast operating-system end-of-support dates.
Forecast replacement budget several years ahead.
Use condition and support status, not age alone, where practical.
Securely erase and de-register every retired device.
Use responsible reuse and e-waste channels.
Report usable-device availability to education leaders, not only purchase totals.

Current Authoritative Guidance

UNESCO’s 2023 Global Education Monitoring Report on technology in education remains a crucial reference because it asks education systems to judge technology on educational need, equity, evidence and sustainability rather than novelty. The report notes substantial inequalities in electricity, connectivity and device access, while also warning that technology products turn over quickly and that infrastructure, teacher capability and governance determine whether access becomes useful learning.

UNESCO’s related guidance on questions to ask before choosing technology in education explicitly raises environmental sustainability, e-waste, privacy, safety and the rapid turnover of education technology. Those are lifecycle issues: a system has to know not only why it is buying technology, but how long it can support it and what happens when the product leaves service.

The World Bank’s Education and Technology Readiness Index separates the education technology ecosystem into pillars including devices, connectivity, school management, teachers, students and digital education resources. That structure supports an important operating distinction for this node: device availability is one subsystem inside a larger digital education service, and weaknesses in any adjoining subsystem can erase the value of the hardware.

UNESCO’s January 2025 update on smartphone regulation also reinforces the core principle that devices belong in education when they clearly support learning. Lifecycle excellence is therefore necessary but not sufficient. The endpoint must be dependable, equitable and secure—and the educational use still has to justify the technology.

The transferable operating principle is: buy fewer surprises by designing support, repair, security, accessibility and replacement before the first device is handed to a learner.

Canonical Owner Boundaries

Education Procurement owns competitive purchasing, specifications, supplier selection, contracting and general procurement control.
School Connectivity owns broadband, local networks, Wi-Fi and the route between devices and digital services.
Education Cybersecurity & Digital Service Continuity owns threat management, incident response, resilience and wider security operations.
Education Data Privacy & Student Records Governance owns lawful, proportionate and accountable handling of learner information.
School Electrification & Energy Reliability owns the power service that makes digital infrastructure usable.
Open Educational Resources & Open Licensing owns reusable and adaptable learning content rather than endpoint operations.
School Estate Asset Registers & Lifecycle Planning owns the broader estate-wide asset view across land, buildings and equipment.

This node owns endpoint operations after acquisition: device identity, configuration, custody, charging, accessories, help desk, repair, spares, warranty, update control, accessibility, replacement, secure erasure and responsible retirement.

The Return Path

Return to the thousand devices that arrived in boxes.

Before distribution, each receives an identity. Standard configuration installs automatically. Users receive accounts, chargers and clear support instructions. Spares sit where repair delay would otherwise stop learning. The help desk knows what it owns and when to escalate. Battery data reveals decline before whole cohorts fail. Warranty claims feed back into vendor performance. Updates move through test rings. Accessibility settings are checked under real policy. End-of-support dates enter the replacement forecast years before they become emergencies. When devices leave service, accounts are removed, data is erased and equipment is reused or recycled through a controlled route.

The technology programme becomes less exciting.

That is a compliment. Infrastructure is most useful when teachers and students can rely on it without having to think about the machinery keeping it alive.

Digital learning becomes dependable when the system stops treating devices as purchases and starts treating them as a fleet that has to survive real school life.

Return to the How Education Works hub.

How Education Works | School Technology Fleet & Device Lifecycle Management — How Devices Stay Secure, Repairable, Supported and Useful After Procurement