Vertask gives school and district IT a single record for every laptop, tablet and cart: who has it now, who had it before, what broke, what it cost and when the warranty runs out — alongside a help desk for staff.
Get Started Free See PricingFree forever No credit card Setup in minutes
1:1 programmes fail on record-keeping, not technology. When a device comes back cracked, the questions are always the same — and a spreadsheet cannot answer them.
A device changes hands three times in a year. Without a permanent record of each handover, damage cannot be attributed and nothing can be recovered.
Hundreds of devices come back at once. Which were never signed out? Which never came back at all? The spreadsheet was last accurate in March.
A teacher catches you between lessons. It never becomes a ticket, so it is never prioritised and never counted when you ask for budget.
Assign the device to a student or staff member and to a building. That handover is now on the record.
Every repair ticket attaches to the device itself, so its damage history travels with it, not with a technician’s memory.
It moves to a new student. The previous holder, the date and the reason are written permanently to the ownership history.
Warranty lapse raises a ticket automatically. Age and lifecycle reports turn the fleet into a defensible refresh budget.
Fleet-wide compliance and encryption posture, refresh planning backed by real age data, and reports that survive a board meeting.
Walk up already knowing who has the device, what broke last time and whether it is still under warranty.
A real check-out and check-in trail for devices and equipment — without maintaining another spreadsheet.
No — and we would rather say so up front. Automatic device and user sync works with Microsoft Entra ID and Intune only. Chromebooks, iPads and anything else are still fully supported as tracked assets: import them by CSV or through the REST API, and every other feature — chain of custody, warranty alerts, tickets, reports, per-school groups — works exactly the same regardless of platform.
Yes. Every time a device is reassigned, Vertask writes a permanent record of who held it, when it changed hands and the reason given. That history cannot be quietly overwritten, and it exports as an ownership-change report — which is what you need when damage has to be attributed.
Two lists do most of the work. The lost-and-found view shows every device that was never filed into a group, and the unassigned view shows devices sitting in inventory with no holder. Between them you get a real punch list instead of reconciling a spreadsheet by hand.
No. Anyone who only raises and follows requests — students, teachers, office staff — uses the portal and does not consume a seat. You pay per agent: the technicians and administrators who actually do the work. Small teams can run on the free plan indefinitely.
Yes. Group devices by building, cart or department and grant a campus technician access to just their own group, while district IT keeps the fleet-wide view. If one specific device needs to be shared with one specific team, that can be granted on its own without restructuring anything.
Yes. Import from CSV with a downloadable sample file to match the format, or push records in through the REST API. Existing Microsoft-managed devices can be pulled in automatically instead.