What Do You Actually Own? A Kitchen-Table Inventory for Your Office Tech
Photo: United States Small Business Administration, Public domain, via Wikimedia Commons
Every small office has a drawer. Maybe it is the bottom one in the reception desk, maybe it is a plastic bin in the supply closet with a label someone printed in 2019. Inside: two dead chargers, a router that used to work, a label maker nobody claims, and a laptop with a sticky note on it that says DO NOT USE.
That drawer is not an inventory. It is an archaeology site. And the reason it exists is simple—most teams learn what they own at the exact moment something breaks, which is the worst possible time to go looking.
A tech asset map is the unglamorous fix. Not a database, not a subscription, not a platform with a per-seat price. A spreadsheet with maybe nine columns and a calendar reminder. Twenty minutes to start, ten minutes a quarter to keep alive.
The real cost of not knowing
When a laptop dies on a Tuesday morning, four questions show up at once. Who was using it? Is it still under warranty? What was on it, and is that backed up? And who has the login for the thing it was connected to?
If the answers live in three different heads and one Gmail thread from 2023, you have just converted a hardware problem into an operations problem. Same thing happens with the printer lease that auto-renewed, the domain that lapsed because the renewal notice went to a former employee, and the software seat you are still paying for on behalf of someone who left last spring.
None of those are IT failures. They are records failures. And records are cheap to fix when you are not on fire.
Nine columns, no more
Resist the urge to build something beautiful. Asset-management tools sell dashboards; you need answers. Start with these:
- Asset name — whatever people actually call it. “Front desk PC” beats “WS-0042.”
- Type — laptop, desktop, printer, router, switch, phone, software subscription, domain, cloud service.
- Serial or account number — the thing a warranty claim asks for.
- Assigned to — a person, or “shared” if it lives in the conference room.
- Purchased from / date — where the receipt lives matters more than the exact day.
- Warranty or contract end — the single most valuable cell in the sheet.
- Admin owner — who holds the keys, not who uses it.
- Cost and billing cycle — monthly or annual, and which card it hits.
- Notes — “lease, don’t buy,” “do not factory reset,” “old owner’s email is the recovery address.”
Everything else is optional. Photos of serial-number stickers are a nice touch if your phone makes it a five-second job. Photos of the actual equipment are a nice touch if you enjoy taking photos of equipment.
Twenty minutes, honestly
Set a timer. Walk the office with a laptop and fill in the physical gear first—every screen, every box with a blinking light, every printer, every desk phone. Do not stop to fix anything. If a serial number is hidden behind a monitor arm, write “check later” and move on.
Then open your billing statements. Credit card and bank, last three months, filtered by anything that smells like software. Every recurring charge gets a row. This is where most people find the surprises: the design tool with three seats and one user, the backup service for a server you retired, the phone system add-on nobody turned off.
Then the invisible stuff—the assets with no physical form and no invoice:
- Your domain registrar and the login email on the account
- Your DNS host, if it is separate
- The business Wi-Fi admin panel
- Your email or Google Workspace / Microsoft 365 admin account
- The ISP account, including the circuit ID on the bill
- Any point-of-sale or payment processor portal
- Social accounts and the business listing pages
That is the whole session. One tab, maybe fifty rows for a small shop. It will not be complete, and that is fine—completeness is not the goal.
The top-five exercise
Here is the step that turns a spreadsheet into something useful. Before you close the file, highlight five rows: the assets whose failure would stop money from coming in or work from happening tomorrow.
For a dental office it might be the practice-management server, the scheduling software, the front desk PC, the card terminal, and the router. For a two-person design shop it might be the file storage, the Adobe seats, the domain, the main laptop, and the invoicing tool.
Those five get the extra treatment: a documented recovery step, a backup that has been tested, and a second person who knows how to get in. Everything else on the list can be handled when there is time. The top five get handled before there is a problem.
Write the five on an index card and tape it inside the supply cabinet. Seriously. The list you can find in a panic is worth three lists you cannot.
The quarterly ritual
Put a recurring fifteen-minute block on the calendar—first Monday of January, April, July, October works fine. The agenda never changes:
- Anything new since last time? Add it.
- Anything retired? Mark it, do not delete it—you will want the history when a charge reappears.
- Any warranty or contract expiring in the next ninety days? Flag it.
- Did anyone leave or change roles? Reassign their rows and revoke access.
- Does the top five still make sense?
That is it. No scoring model, no depreciation schedule unless your accountant asks. If you sell the business or apply for a loan, an accurate asset list is a genuine asset—but do not build it for that. Build it so the next broken laptop is a fifteen-minute inconvenience instead of a two-day scramble.
Where to keep it
Store it in whatever your team already opens without thinking—a shared drive, a Google Sheet, a Notion page. What matters is that at least two people can reach it, it is backed up with everything else, and it is not stored only on the laptop it describes.
One caution: a full inventory is a map of your weak points. Do not put admin passwords in the same sheet. Note who holds each credential and where it lives—a password manager, a sealed envelope, whatever your team uses—and leave the secret itself out of the file. If the sheet ever leaks, you want it to be embarrassing, not catastrophic.
The point of all this
You are not building an IT department. You are building a memory. Small teams run on institutional knowledge that lives in one or two heads, and heads are the least reliable storage medium available.
Twenty minutes now, fifteen minutes a quarter, and the drawer in the supply closet stops being a mystery. That is a good trade for any small business—and it costs exactly nothing but attention.