Hardware lifecycle management done right

When to refresh, when to reassign, when to retire. A working hardware lifecycle policy rests on three numbers per device — and the difference between knowing them and guessing them is six figures a year.

Most companies replace laptops on rumour. Someone's machine "feels slow." A new hire "needs the newest model." A returning employee "shouldn't have to use the old hardware." The result is a hardware budget that grows faster than headcount and a closet full of devices that nobody quite knows what to do with.

Lifecycle management replaces rumour with three numbers per device. With those, every refresh, reassignment, and retirement happens on a schedule.

The three numbers

1. Assignee. Who has it, today, by name and email — synced from your identity provider.
2. Warranty end. When the manufacturer support ends. After this date, replacement parts get expensive and downtime becomes a real cost.
3. Refresh due date. Set at acquisition based on a depreciation policy. For laptops, typically 36 or 48 months from purchase.

If you have these three numbers for every laptop, monitor, phone, and major peripheral in your fleet, you've solved 80% of hardware lifecycle management. The remaining 20% is enforcement.

Refresh policies that actually save money

The choice between a 36, 48, or 60-month refresh cycle is the single biggest hardware cost lever. The math:

The right answer is usually tiered: 36 months for engineering and design, 48 months for general knowledge workers, 60 months for kiosks and shared workstations. A blanket 36-month policy across the whole company over-spends; a blanket 60-month policy creates productivity drag and warranty gaps.

Reassignment — the under-used lever

When someone leaves, their laptop usually has 12–30 months of useful life left. Reassignment to a new hire defers the next refresh purchase by exactly that much. Most companies miss this for one of three reasons:

1. The laptop never gets returned (the offboarding flow is broken).
2. It does get returned but no one knows what's available when a new hire onboards.
3. The new hire's manager insists on "a fresh laptop" out of reflex.

The fix is workflow, not policy. Offboarding triggers the laptop into a "returned, available" pool with its remaining warranty months visible. Onboarding queries that pool first. The exception (engineer needs latest M-series) gets approved explicitly, not by default.

Retirement and disposal

End-of-life hardware is a security and compliance issue, not just a logistics one. Three things must happen, in order:

1. Data wipe — certified erase, not just a factory reset. Document with a serial-number-stamped certificate.
2. Asset reconciliation — mark the device "retired" in the inventory with disposal date and method.
3. Disposal — manufacturer trade-in, certified e-waste vendor, or controlled donation. Always with a chain-of-custody receipt.

The disposal certificate is what auditors ask for. Without it, a SOC 2 finding is essentially guaranteed. More in the audit checklist.

The "ghost laptop" problem

Ghost laptops are devices assigned to people who no longer work at the company. Every IT manager has met them. They surface during audits, hardware refreshes, or when finance asks why the asset register has 240 laptops for 200 employees.

The solutions, in increasing order of effectiveness:

• Policy: every leaver returns hardware before final paycheck. Effective only when HR enforces it. Often doesn't.
• Process: offboarding ticket includes hardware return as a blocking step, with the asset tags listed automatically. Better.
• System: identity deactivation triggers a hardware return task with a 14-day SLA. After 14 days, it escalates to the leaver's manager. After 30, the device is marked "lost" and reported. Best.

Hardware policy template

The minimum policy your IT lead should have written down — not as a Notion essay, but as enforceable rules:

1. Every device entering the company gets a tag and an inventory record at receipt, before deployment.
2. Refresh cycles: 36 months for engineering/design, 48 months for everyone else, 60 months for shared/kiosk.
3. Reassignment is the default for any device with > 12 months remaining warranty; new purchases require a justification above that threshold.
4. Offboarding triggers a hardware return task with a 14-day SLA.
5. Retirement requires a data-wipe certificate and a disposal receipt; both stored against the asset record.
6. Quarterly reconciliation: physical count vs. register, with variance investigation.

Tooling that supports the policy

InventorIA's hardware module covers the full lifecycle: receipt → assignment → reassignment → retirement, with warranty tracking, depreciation schedules, and the audit log that satisfies SOC 2 / ISO 27001. Identity sync auto-flags ghost laptops the moment a user is deactivated. The result: a register that stays accurate without anyone running a spreadsheet update.