IT Asset Management App Starter · Industry version
School Device Management Template
An asset system built for 1:1 programs — student assignments, loaner pools, carts, damage fees — generated into code your district owns.
A district device program is an asset problem with a bell schedule: two thousand laptops assigned to students, a loaner pool for cracked screens, carts that migrate between classrooms, and a three-week window in June to collect it all. This starter models that year and hands your district the code.
- 6 core entities
- Full audit trail
- Code you own
- Vibe + Governed modes
01 · The problem
Why a generic IT Asset Management falls short
Corporate asset tools assign devices to employees; schools assign them to students — which drags in guardians, grade levels, homerooms, and the annual churn of enrollment. When the student isn't a first-class record, the fall rollout becomes a mail-merge project and the June collection becomes a manhunt.
Damage runs on a different economy too. A cracked screen means a same-day swap to a loaner so the student can work, a repair ticket for the broken unit, and often a fee against a family — waived, insured, or on a payment plan per district policy. Generic tools model none of that chain; schools live in it weekly.
And devices in schools travel in herds. Carts of thirty move between classrooms, checked out to teachers rather than students, and a cart missing two units on Friday is a different problem from a missing student device. Cart-level custody with unit-level contents needs to be in the schema, not in a clipboard on the cart.
02 · Data model
The data model, adapted
Everything in the base IT Asset Management starter —
assetslicensesaccessoriescheckoutsauditslocations— plus the entities this industry actually runs on:
| table | what it holds |
|---|---|
students | Enrolled students with grade, homeroom, and guardian contact — the people devices are actually assigned to, refreshed with enrollment each year. |
device_carts | Rolling carts holding a set of units, checked out to teachers and rooms, with per-slot contents so a short count is visible at a glance. |
repair_tickets | Damage and repair records linking the device, the student, the fault, the loaner issued, and any fee assessed under district policy. |
03 · Screens
Modules through the industry lens
Rollout and collection at grade scale
01Checkout becomes batch assignment: a grade level's devices issued against the enrollment list, with agreement forms and condition recorded per unit. Collection runs the same list in reverse, and the exceptions report — not returned, returned damaged — is the summer worklist.
Loaner pool with swap flow
02A damaged device swaps for a loaner in one action: the loaner checks out to the student, the broken unit opens a repair ticket, and both show in the student's record. Nobody loses a school day to paperwork, and nobody loses the loaner either.
Damage fees under district policy
03Repair tickets carry assessed fees with your policy encoded — first incident waived, insurance applied, hardship exceptions — and a balance view per family. Because the rules are code your district owns, a school-board policy change is an edit, not a feature request.
04 · In practice
Workflows it models
Fall 1:1 rollout
01Import the enrollment list, batch-assign devices by homeroom, and capture the signed agreement per student. By Friday of week one, the dashboard shows exactly who has what and which students still need a unit.
Cracked screen on a Tuesday
02The student brings the device to the media center; the tech swaps in a loaner, opens the repair ticket, and the fee posts per policy. The student walks out equipped, and the broken unit is in a tracked queue.
June collection and audit
03Collection runs against the assignment list by homeroom, condition checked per unit. The final exceptions report drives holds and follow-ups, and the summer audit confirms carts and storage rooms match the records.
School Device Management template — frequently asked questions
Does it work for Chromebook 1:1 programs?
Yes — 1:1 device programs are the core case: batch assignment against enrollment, per-student custody with guardian contacts, loaner swaps, and end-of-year collection. It's device-agnostic, so mixed fleets of laptops and tablets track the same way.
Can it manage damage fees and device insurance?
Repair tickets carry assessed fees, and your district's policy — waivers, optional insurance, payment plans — lives as rules in code you own. Family balance views make the follow-up letters a report, not a research project.
How does it handle carts and shared classroom sets?
Carts are first-class: a cart checks out to a teacher and room while its units remain individually tracked inside it. Short counts surface at cart level immediately, without losing per-device history.
Can it import our student roster?
Students load from a roster export, and because you own the schema, mapping your SIS fields — grade, homeroom, guardian email — is a straightforward import you can rerun each fall as enrollment settles.
Related
Dual7 App Starters
Build your School Device Management on your terms
An asset system built for 1:1 programs — student assignments, loaner pools, carts, damage fees — generated into code your district owns. Describe your version to start — the output is a project you own.