Use cases · K-12 & tertiary
K-12 & tertiarySchools & universities
Intake week, device fleets, and a timetable that does not pause because a projector failed.
How IT usually works in this setting
Education runs on cycles: enrolment, intake, semester, exam period, holidays. IT support has to scale for two weeks a year and justify its budget for the other fifty.
What it costs you today
- Onboarding hundreds of students lands in one week, and it is done by hand.
- A device fleet ages out without a plan, so failures arrive all at once.
- Teaching staff will not use a portal that is harder than sending an email.
- Nobody can say what the department actually spends per year per device.
What the desk does about it
- Intake as a process — New students and staff arrive in a batch, are placed into the right group, and get their access and their device allocation in one pass.
- A fleet you can plan for — Warranty dates and asset age are visible, so replacement decisions are made from a register rather than from a failure.
- A desk teachers will actually use — Raise it in a few clicks or by replying to an email, with the assistant answering the predictable questions before a technician is involved.
- Numbers for the budget conversation — Requests, assets, licences and time-to-resolve per faculty, exported on demand.
“Devices have a life”
A defensible replacement plan before the next semester.
What we show you, in order
A university department with 40 laptops of mixed age
- Import the fleet with purchase date, warranty and current holder.
- Assign each device to a department and a person, so orphans become visible.
- Run the age and warranty report, and rank what fails next.
- Set up reservations for loan equipment during repairs.
- Give the department head a one-page view of cost and risk.
Why it lands
Replacement stops being an emergency and becomes a line in the budget.
What we can stand behind
- Asset lifecycle from procurement to retirement, including reservations and loans.
- Batch import of users and assets, so intake is not a week of typing.
- A portal and an email address that both feed the same queue.
- Licence tracking, so software renewals are a report rather than a guess.
What we would need from you
- The device register (however messy) and the enrolment list format.
- Your faculty or department structure — it becomes the tenant structure.
- The systems that must be up during exams, in priority order.
- A representative from teaching staff to sanity-check the portal.
What every one of these has in common.
The configuration changes by sector. The platform underneath it does not: one record per request, service levels per team, and tenancy enforced on the server.
One request, everything attached to it
The same data model behind all eight situations — which is why a sector change is a configuration change rather than a new product.