☕ Buy a Coffee
Home / Productivity & Coding

Use 'Notion' Templates for IT Asset Tracking

Create relational database views to monitor company laptops, monitor inventory, software licenses, and hardware warranty expirations.

Sachin Siju
Sachin Siju
Lead Systems Engineer & Tech Blogger
Jul 15, 2026 4 min read
Use 'Notion' Templates for IT Asset Tracking

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

  1. Create a new page and add a Table database (type /table and select Table - Full page).
  2. 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 database
  • Purchase Date — Date
  • Warranty Expires — Date
  • Serial Number — Text
  • Vendor — 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 — Number
  • Seats Assigned — Rollup, counting relations from an Assigned Users relation property
  • Renewal Date — Date
  • Cost/Seat — Number (formatted as currency)
  • Total Annual Cost — Formula: prop("Seats Purchased") * prop("Cost/Seat")
Tip: The Rollup property type is what makes Notion feel relational instead of flat. It pulls a value (count, sum, or list) from a linked database through a Relation property, so "seats assigned" always reflects live data instead of a number you have to remember to update.

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 Status property 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 Expires to "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 To to 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:

  1. Open the departing employee's page in the Employees database.
  2. Every asset currently assigned to them appears in the linked "Hardware Assets" rollup — work through that list.
  3. For each asset, change Status to In Storage and clear the Assigned To relation.
  4. Archive or mark the employee record as inactive once every asset is reconciled.
Warning: Notion is not a source of truth for security-sensitive data like MDM enrollment status or disk encryption keys — it's an inventory and workflow layer. Keep credentials and encryption recovery keys in a proper secrets manager or your MDM platform, and only reference (never store) that sensitive data from Notion.

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.

Featured Infrastructure Partner

Deploy on High-Performance Hostinger Cloud

Get up to 75% OFF + free domain & SSL. Powering xube.me's sub-second response times.

Claim Discount ↗

Discussion & Insights

Related Technical Essays