Asset compliance reports

For the helpdesk team

Compliance reports

Compliance reports is a single landing page surfacing the four asset hygiene buckets that the IT lead pulls weekly. The shapes are derived live from the database — there’s no scheduled rebuild, no caching. What you see is current to the page-load.

The four buckets

Older than 5 years — active assets (in service, under maintenance, or received) whose purchase date is more than 5 years ago. The refresh-cycle conversation usually starts here.
Retired / disposed — assets with status Retired or Disposed that are still on the register. Useful for confirming everything in this bucket has been disposed of properly (WEEE, data wipe, asset removal from register). This is a transitional staging list — it’s normal for items to be here briefly during decommissioning.
Not seen in 30 days — hardware assets matched to a discovery agent but whose last check-in is over 30 days ago (or that have never checked in). Either off the network (legitimate — laptop in a drawer) or out of contact (investigate).
Warranty expiring or expired — active assets whose warranty expires within the next 60 days, or has already expired. Both are surfaced together because both require action.

Each bucket shows the count, the threshold used, and a list of rows you can click into.

What the thresholds mean

The thresholds are listed at the top of the page. They’re config defaults — your trust can override them in config/assets.php if the standards differ.

If a row shouldn’t be in a bucket (e.g. a 6-year-old device that’s been refreshed but the row’s procurement date is misleading), fix the row itself rather than tuning the threshold.

When to run this

Weekly — IT lead’s standing review. Five minutes; clears the not seen bucket fastest.
Before a budget cycle — for the aged-devices bucket as the refresh business case.
At ISO audit prep — for the retired/EOL bucket. Confirm every “retired” asset has a disposal note.

Gotchas

Not seen in 30 days counts only assets that have ever reported in. A laptop with no discovery agent installed never lands in the bucket; it lands in “no data” elsewhere.
The aged-devices threshold uses procurement date, not warranty-start. For ex-demo or refurbished kit, those can diverge.
Buckets aren’t mutually exclusive — a 6-year-old retired device shows up in both. Read totals as an upper bound on items needing attention, not as separate populations.