Why Notion Works for Asset Tracking
Spreadsheets are the default tool for tracking company laptops and licenses, but they fall apart fast: no relational links between "this laptop" and "this employee" and "this warranty," no automatic status rollups, and no easy way to view the same data as a table one day and a kanban board the next. Notion's databases give you a proper relational model without standing up an actual database server, plus the flexibility to reshape views on demand. For a team managing a few dozen to a few hundred assets, it hits a sweet spot between a spreadsheet and a full-blown ITAM platform like Snipe-IT.
Building the Core Asset Database
- Create a new page and add a Table database (type
/tableand select Table - Full page). - Rename it Hardware Assets and set up these properties:
Asset Tag— Title property (your internal ID, e.g.LAP-0142)Type— Select (Laptop, Monitor, Docking Station, Phone)Status— Select (In Use, In Storage, In Repair, Retired)Assigned To— Relation, linked to a separate Employees databasePurchase Date— DateWarranty Expires— DateSerial Number— TextVendor— Relation, linked to a Vendors database
Set up the Employees database the same way, with a name, department, and email property. Once both databases exist, the Assigned To relation automatically creates a back-reference on the Employees side — open any employee's page and you'll see every asset checked out to them, without maintaining that list manually.
Adding a Software Licenses Database
Software licenses need a slightly different shape since you're tracking seat counts, not physical units:
License Name— Title (e.g., "Adobe Creative Cloud")Seats Purchased— NumberSeats Assigned— Rollup, counting relations from anAssigned Usersrelation propertyRenewal Date— DateCost/Seat— Number (formatted as currency)Total Annual Cost— Formula:prop("Seats Purchased") * prop("Cost/Seat")
Creating Useful Views
The same underlying database can be displayed multiple ways without duplicating data. Click + Add a view at the top of the database and create:
- By Status (Board view): Group by the
Statusproperty so assets appear as cards in In Use / In Storage / In Repair / Retired columns — great for a quick visual audit. - Expiring Warranties (Table view, filtered): Filter
Warranty Expiresto "is within next 30 days" and sort ascending, so you always know what's about to fall out of coverage. - By Owner (Table view, grouped): Group by
Assigned Toto quickly see everything checked out to a specific person — useful during offboarding.
Automating Warranty Alerts
Notion databases don't send notifications on their own, but you can combine a filtered view with Notion's native reminder feature: open a record with an upcoming Warranty Expires date, click into the date field, and toggle Remind to get a Notion notification a set number of days beforehand. For team-wide alerting, connect the database to Notion's official Zapier or Make integration and trigger a Slack/email notification whenever a new row enters your "Expiring Warranties" filtered view.
Handling Offboarding Cleanly
Because assets and employees are linked via a Relation property, offboarding becomes a checklist instead of a memory exercise:
- Open the departing employee's page in the Employees database.
- Every asset currently assigned to them appears in the linked "Hardware Assets" rollup — work through that list.
- For each asset, change
Statusto In Storage and clear theAssigned Torelation. - Archive or mark the employee record as inactive once every asset is reconciled.
Wrap-Up
A relational Notion setup — Hardware Assets, Software Licenses, Vendors, and Employees all linked together — replaces a sprawling spreadsheet with something that stays accurate almost automatically. Rollups keep counts current, filtered views surface what needs attention (expiring warranties, unassigned gear), and the underlying data structure scales from a five-person startup to a few hundred employees before you'd need to graduate to a dedicated ITAM tool.
Discussion & Insights