Lifecycle
Create the device, assign it, repair it, and retire it without losing the history.
EDUnifi keeps assignment, repair, warranty, and refresh history for each student and staff device. Help desk tickets and staff training connect to that same record.
The inventory is the system of record. Everything else on the platform hangs off that device.
Create the device, assign it, repair it, and retire it without losing the history.
Search by serial, asset tag, building, user, or device type.
Student and staff assignment, with history by device or by user. Names and emails are for that assignment, not for grades or attendance.
Repairs, warranty expirations, device age, and replacement planning.
Barcode and QR scanning for inventory work, plus notes and attachments on the record.
A spare pool while a device is out for repair, and fee records when your process uses them.
Bring devices in from a spreadsheet or create them as they arrive.
Check a device out to a student or a staff member and keep that history.
Record repairs and watch warranty dates before refresh season.
Close the device when it leaves service, with the record still intact.
Help desk and staff training are part of the platform. They use the device history instead of a second database.
Help desk
Intake, assignment, email, and SLAs, with issue history by user, device, and location.
Staff training
Assign training by team or role, then track completion. This is staff training, not a student course system.
Platform access, onboarding, setup, and staff training are included. Pricing is quoted for the district.
| District work | Separate tools | EDUnifi |
|---|---|---|
| Where the device is | A spreadsheet or a standalone inventory | One asset record |
| What happened to it | Repair notes in email or another system | History on the device |
| A new ticket | The help desk cannot see the device | The ticket opens on that record |
| Getting started | Export, clean up, and hope the columns match | CSV migration, onboarding, and staff training |
Each page explains one job. The work itself happens in the app.
No. EDUnifi is built for K-12 school districts of every size. We accommodate small, mid-sized, and large districts.
Yes. EDUnifi includes onboarding support, migration guidance, and setup assistance to reduce switching friction.
Yes. Role models include Super Admin, Organization Admin, and Standard User access patterns.
K-12 is the primary focus, with flexible workflows that can extend to private schools, colleges, nonprofits, and similar organizations.
Yes. EDUnifi is one platform that connects school technology asset records with district IT ticketing so support staff can see device history alongside tickets when both modules are used.
Yes. Districts can maintain assignment history, repairs, and lifecycle records for student and staff devices, including common 1:1 programs, using EDUnifi asset management.
No. EDUnifi is not a student information system. It uses student names and emails so devices can be assigned and so staff can view assignment, ticket, and repair history by device or by user. It does not manage grades, attendance, or academic records.
We walk through device records, assignment, and how a ticket sits on that history. Then we map onboarding to your district.