IT Asset Management With AI: Tracking Devices for a 60-Person Company

When the office manager of a 60-person company asked me to help her find the company's laptops, I assumed she meant the procurement records. She meant the actual machines. The register had drifted so far from reality that she didn't know how many devices were unaccounted for, who had them, or whether any were sitting in former employees' kitchen drawers.

Why does IT asset tracking quietly collapse around 50 people?

Because the founder was the registry. Up to 30-40 employees, one person in the company can hold "who has what" in their head. Past that, the head-registry fragments — office manager remembers some, HR remembers some, the engineer who set up the laptop remembers some, and nobody has the full picture. The Plan was "we know where every device is." The Fact is "we know where most of them are." The Gap is invisible until a laptop walks out the door.

Definition: Joiner / Mover / Leaver (JML) — the three lifecycle events that trigger asset transactions: a new hire receiving equipment, an internal role/team change, and a departure requiring return. Every asset transaction maps to one of these three.

The most common symptom: hardware budget that has crept up faster than headcount, with no clear explanation. Usually it's a mix of unreturned devices, lost peripherals, and impulse purchases that didn't go through procurement.

What does the joiner / mover / leaver flow look like?

Three sub-flows. Each has an AI-drafted email and a single update target — the asset register, treated as the source of truth.

Joiner

When HR creates the new-hire record, AI drafts the check-out email: which laptop model and serial, which accessories, which software accounts, where to pick up or where it will ship, what to sign on receipt. Office manager reviews and sends. Asset register updated automatically when the hire signs.

Mover

When someone changes role or team and the equipment changes, AI drafts the transition email: what stays, what comes back, what's new, and the dates. Common case: a designer joining the dev team needs a different machine spec; a remote employee moving to a hybrid role needs office hardware added.

Leaver

When HR creates the departure record, AI drafts the check-in email: which devices to return, return method (courier, in-person, shipping label attached), data-wipe certification, exit-survey link, deadline. Office manager and IT review. Asset register flags "pending return" until devices are physically confirmed.

Definition: Single source of truth — for asset management, the one register that all teams (HR, IT, Finance, Office) read from and write to, with no parallel spreadsheets allowed.

The quarterly audit

Three steps. Roughly 90-120 minutes for a 60-person company.

1. Reconcile register vs reality. AI compares the register against signals from MDM (mobile device management), SSO login data, and any other system that touches devices. Flag any asset where signals disagree.
2. Physical spot-check. Pick a 20% sample. Confirm physical possession (photo + signature, or in-person). Tier the rest by risk.
3. Update + budget. Write off truly lost devices, update the register, and produce the budget impact for the CFO.

The first quarterly audit usually surfaces a meaningful gap — 10-25% of devices in larger spec drift, 1-3 missing entirely. This is normal. Subsequent quarters drop to under 5%.

Copy/paste check-out / check-in template

This goes into the JML flow, one per event. AI drafts, office manager reviews, recipient signs.

Event: [JOINER | MOVER | LEAVER]
Employee: [NAME, ROLE]
Effective date: [DATE]

Devices in scope:
| Device | Serial | Action | Owner before | Owner after | Notes |
|--------|--------|--------|--------------|-------------|-------|
| MacBook Pro 14 | XXX-1234 | issue | inventory | [NAME] | new |
| Monitor 27" | XXX-9876 | return | [NAME] | inventory | data-wipe required |
...

Sign-off:
- [ ] Employee acknowledges receipt/return
- [ ] Office manager confirms physical handover
- [ ] IT confirms enrollment/de-enrollment in MDM
- [ ] Register updated [TIMESTAMP]

For LEAVER only:
- [ ] Data-wipe certificate attached
- [ ] All accounts deprovisioned (SSO, SaaS)
- [ ] Deadline: [DATE]   Escalation: [NAME] after 7 days

The "Register updated [TIMESTAMP]" line is the entire game. Without it, the event closes in the email thread but the register stays stale.

Tool tip (AIAdvisoryBoard.me): IT asset management is one of those quiet workflows that follows the Plan → Fact → Gap pattern perfectly. Plan: every employee has the right equipment for their role, every device has an owner, the register matches reality. Fact: today's MDM signals, SSO logins, and physical confirmations. Gap: devices without recent signals, devices assigned to former employees, register entries with missing data. The 7-day diagnostic at https://aiadvisoryboard.me/?lang=en surfaces this pattern alongside every other operational hygiene cadence in the company.

Good vs bad leaver email

Bad: "Hi [Name], please return your laptop on your last day. Thanks!" (Vague device, no return method, no deadline, no consequence path.)

Good: "Hi [Name], on your last day [DATE]: please return MacBook Pro serial XXX-1234, the 27" monitor serial XXX-9876, and the YubiKey. Office manager will meet you at 15:00 on [DATE] to confirm handover and sign the data-wipe certificate. If devices cannot be returned in person, use the prepaid shipping label attached — devices must arrive within 7 days. After 14 days, devices not returned are charged at [REPLACEMENT COST] per the employment agreement, section X.X."

The good version is direct, specific, and references the policy basis. AI drafts this from the template; the office manager doesn't have to compose it.

Manager scan (2-minute digest example)

• Plan: asset register matches reality within 5% drift; JML events close in 7 days for joiners/movers, 14 days for leavers
• Fact: 62 devices in register, 3 leaver events open (1 within deadline, 2 escalated), 1 joiner event scheduled this week
• Gap: 1 leaver device 22 days unreturned — escalation policy triggered, IT to charge per agreement
• Plan: quarterly audit complete by end of Q
• Fact: Q2 audit complete, drift was 8%
• Gap: 5 devices with MDM signal but no register entry — likely impulse purchases — finance reconciliation needed
• Plan: hardware budget tracked per role
• Fact: budget overspent 14% YTD on peripherals
• Gap: unclear if this is policy drift or genuine new need — COO + IT to clarify

Micro-case (what changes after 7-14 days)

A 65-person SaaS company hadn't run an IT asset audit since hitting 35 employees. The first quarterly audit (AI-assisted on the reconciliation step) surfaced 4 unaccounted-for laptops, 2 of which belonged to former employees who'd left in the past year. Both were recovered within 10 days of an AI-drafted "we noticed our records show this device is still assigned to you" email. The other 2 turned out to be in-office spares that had been re-labeled and lost track of. By the second quarter the JML flow was running and drift dropped from "8%" to under 2%. The CFO noted that hardware budget alignment improved enough to defer a planned procurement cycle by 6 weeks.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30-500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

Tool tip (AIAdvisoryBoard.me): IT asset hygiene is one of those workflows where you don't think you need a system until you suddenly do — and by then the cleanup cost is 10× what it would have been at 35 employees. The 7-day diagnostic at https://aiadvisoryboard.me/?lang=en treats asset management as one of the operational cadences alongside scheduling, expense, and vendor management — same Plan → Fact → Gap shape, same daily/quarterly rhythm. If the asset register is drifting, the same pattern is almost certainly drifting in two or three other ops areas you haven't measured yet.

FAQ

Don't we need a real ITSM tool like ServiceNow for this? At 60-200 employees, almost certainly not. Most ITSM tools are sized for organizations with dedicated IT teams of 5+. For SMBs, a single source of truth (one well-maintained spreadsheet or lightweight asset tool) + the JML flow + quarterly audit covers what matters. Move to a proper ITSM when you have a full-time IT manager who needs ticket workflows.

What about devices that aren't laptops — monitors, peripherals, keys? Track at the same granularity until it becomes the wrong granularity. For most SMBs, monitors and YubiKeys (or other security tokens) are worth tracking; mice, cables, and headphones are not. The break point is usually "if it costs over $100 and could walk out the door, it's tracked."

How does BYOD fit in? The register tracks company-issued devices. For BYOD, the register tracks the access (SSO accounts, MDM enrollment for company data) rather than the device itself. The JML flow still applies — joiner/leaver still need account provisioning/deprovisioning even if no hardware changes hands.

What about the data-wipe certificate? Is that necessary? Yes, especially for leavers. A simple signed statement that the device was wiped (date, method, signature) sits in the register entry. This is your audit trail when an ex-employee later asks "did you actually wipe my personal files?" and when regulators ask about data handling. It takes 2 minutes per event.

Conclusion

IT asset management in SMBs isn't a heavyweight problem until the day it is. The transition from "the founder remembers" to "the register matches reality" usually has to happen between 50 and 80 employees. AI doesn't replace the discipline — it makes the per-event work cheap enough that the discipline actually happens.

Run the first quarterly audit. Wire the JML flow. Pick a single source of truth. Watch the drift drop quarter over quarter.

If you want a system that surfaces the Plan → Fact → Gap automatically across the company — including asset, vendor, and scheduling cadences — see how the 7-day diagnostic works at https://aiadvisoryboard.me/?lang=en.