Higher ed

IT asset management best practices for higher education, and where campuses usually break

Generic ITAM advice assumes one company, one budget and one IT department. A university has dozens of each. Here are the practices that hold up on a decentralized campus.

Published · Nov 20, 2026
Inst.Institutional pattern
5 min read
Published
Read
5 min
Topic
Higher ed

Most IT asset management (ITAM) guidance is written for companies: a single IT organization, a single budget, a single directory of employees. A university has a central IT office, college and departmental IT groups, research labs buying on grants, student-facing loaner programs, and a finance office that needs the same assets on the balance sheet. The practices below are the ones that survive that structure.

What is IT asset management in higher education?

IT asset management is the practice of tracking an institution's hardware, software and subscriptions across their lifecycle — request, purchase, receipt, deployment, use, refresh and disposal — in a single system of record. In higher education it also has to satisfy the controller (capital assets and depreciation), sponsored programs (federally funded equipment), information security (where institutional data lives), and procurement (contracts and renewals).

1. Keep one system of record — and decide what "record" means

The most common failure isn't a missing tool. It's four tools that each hold part of the truth: an MDM console, a help-desk CMDB, a finance fixed-asset module, and a departmental spreadsheet. Each is right about something; none is right about everything.

Pick one register as authoritative for the existence and identity of an asset — its tag, serial, model, owner, location and status — and make the others feed it or read from it. Finance can keep the general ledger; MDM can keep the device's configuration. The register is where they agree on which object they're talking about.

2. Track the whole IT asset lifecycle, not just the middle

Most campuses track assets well while they're deployed and poorly at both ends. The IT asset lifecycle has six stages, and the records you need are created at each one:

  1. Plan and request. Standards, approved models, and the budget line it comes from.
  2. Procure. Purchase order, vendor, cost, funding source — including the grant, if any.
  3. Receive and tag. The asset enters the register here, before it reaches a desk.
  4. Deploy and assign. To a person, a lab, a classroom or a loaner pool.
  5. Maintain and move. Repairs, warranty claims, transfers between departments.
  6. Retire and dispose. Sanitization, surplus route, disposal date and proceeds.

If an asset can enter service without passing through receiving, or leave without passing through retirement, the register will drift no matter how good it is in the middle.

3. Let systems update the register, not people

Manual updates don't scale to tens of thousands of devices. Three feeds do most of the work:

  • MDM (Jamf, Intune, Google Admin) knows every managed device's serial number, model, OS and last check-in. Syncing it into the register catches new devices, flags devices that have gone quiet, and keeps hardware details current.
  • HRIS (Workday, Banner, PeopleSoft) knows who joined, moved and left. Joiner, mover and leaver events should become asset events: assign on hire, re-attribute on transfer, recover on exit.
  • Procurement and AP know what was bought. Purchase data is how assets enter the register with their cost and funding source intact.

People still matter — for tagging, physical counts and exceptions — but their time should go to the things systems can't see.

4. Assign every asset to someone accountable

An unassigned asset is an asset nobody will notice is missing. Assign each one to a person, or to a location with a named custodian for shared equipment. When the person leaves, the HRIS event should create a recovery task, not an orphan.

For research equipment, the custodian is usually the principal investigator's lab, but the PI rarely does the paperwork. Name a delegate and give them access.

5. Respect the decentralized org chart

Colleges, departments and research centers buy their own equipment and often run their own IT. Fighting that usually loses. A better model:

  • Central sets the standards and owns the register. Tag formats, required fields, data classes, retirement rules.
  • Units manage their own assets inside it, with permissions scoped to their college or department.
  • Reporting rolls up. The CIO and the controller see campus-wide totals; each unit sees its own.

Chargeback or showback — attributing device and license costs to the departments that use them — makes the register useful to units, which is what keeps them maintaining it.

6. Plan refresh from data, not from purchase dates alone

A refresh cycle (often four or five years for staff laptops) is a budgeting tool, not a law. Combine purchase date with warranty expiry, device age, and actual condition and usage from MDM. You'll find devices due for refresh that are barely used and could be redeployed, and others that need replacing early. Forecasting refresh by department and fiscal year turns an annual budget surprise into a plan.

7. Put software and SaaS in the same ledger as hardware

Licenses are assets with renewal dates. Track subscriptions alongside hardware, with seats assigned to the same people, so a leaver's laptop and their licenses are recovered together, and idle seats are reclaimed before renewal. For public institutions this also feeds GASB 96 reporting; see our GASB 96 guide.

8. Audit continuously instead of annually

A once-a-year inventory finds problems eleven months late. Continuous checks find them in days:

  • Managed devices that haven't checked in for 30, 60 or 90 days.
  • Duplicate serial numbers across sources.
  • Assets assigned to people who have left.
  • Capital or federal equipment with no physical verification in two years.
  • Warranties expiring on devices still in service.

Then the formal physical inventory — required at least every two years for federally funded equipment under 2 CFR 200.313 — becomes a confirmation exercise rather than a discovery one.

9. Make retirement a controlled process

Retirement is where data leaks and books go wrong. Require a sanitization standard that matches the device's data classification, record chain of custody to the vendor, and post the disposal date and proceeds to the asset. Our IT asset disposition playbook covers NIST SP 800-88 in detail.

Where do campuses usually break?

  • Receiving is optional. Departmental card purchases skip tagging, so the register starts incomplete.
  • Leavers keep their devices. The HRIS knows they left; the asset system never hears.
  • Two lists for one fleet. IT's inventory and finance's fixed-asset list disagree, and nobody owns reconciling them.
  • Disposal by weight. Surplus pickups are recorded as pallets, not assets, so retired equipment lingers on the books.

Where Habeo fits

Habeo is built as the single register for a decentralized campus. It pulls devices hourly from Jamf, Intune and Google Admin, turns Workday, Banner and PeopleSoft changes into joiner, mover and leaver workflows, scopes access by college and department, and keeps hardware, software, grants and depreciation on the same records. Small colleges can start a 14-day free trial with real connectors and no card; larger institutions usually start with a demo.

Related reading: asset tagging for colleges and universities, and the glossary entries for ITAM, system of record and hardware refresh cycle.

For asset directors

Could we save your team a week of reconciliation?

We will pull a sample of your inventory live, walk you through the migration plan, and stay through your fiscal close. No statement of work. No agents on endpoints.

No card required · up to 2,000 endpoints · 14 days on your own data. Or see pricing.

“The institutional record, finally in one place. We’re using Habeo every day — and the controller’s office is, too.”

§
From the Journal
Field notes · Vol. II
Liked the read? Try Habeo on your own devices — 14 days free, no card.
Start free trial