checklist
What Should an Asset Audit Cover Before Your Busy Season?
A useful audit answers four things per site: what equipment exists and who it serves, whether each device is reachable and monitored, whether documentation matches reality, and which changes since the last audit were never recorded. Walk the list site by site and fix the map before the ticket volume arrives. SignalNook keeps the asset map, health signals, and change log on one desk for small ISP and managed-WiFi operators. You can open these pages and sign in to the workspace today. That does not mean SignalNook is connected to your routers or monitoring systems, and it does not mean the product has formally launched.
What an audit is actually for
Audits fail when they degrade into a spreadsheet of model numbers nobody consults again. The question each item serves is narrower: if this site went down at nine on a holiday evening, would the record tell whoever is on call what is there, who is affected, and what changed last? If not, that gap is the finding.
Read-only monitoring cannot diagnose assets that are unreachable or undocumented, so the audit's main output is shrinking the undocumented set. Network, billing, and DNS mutations require operator authorization: the audit lists needed changes, it does not perform them.
What to line up first
Your current asset list per site, a way to check reachability during the walk, the change log since the last audit, and the mapping of each asset to the customer or service it supports. Where that last mapping is missing, budget extra time; it is usually where audits find their worst gaps.
Step 1: Reconcile the map against the field
Walk or remotely verify each site and mark every difference between the documented inventory and what physically exists: extra devices, missing ones, hardware swapped without a note. Reconciliation is dull and it is the whole foundation; every later step assumes the map matches the world.
Step 2: Check reachability and health signals per device
For each mapped device, confirm it responds and its health signals are actually being collected rather than merely configured. Devices that fail here go on the unreachable list with a date, because an unreachable device is invisible to every future incident review until someone notices.
Step 3: Tie every asset to a customer or service
Each asset names what breaks for whom if it dies. This mapping is what turns an incident record from 'device X is down' into 'the Hendersons and the office behind them are dark', which is the difference between triage and archaeology at night.
Step 4: Review the unrecorded changes
Go through the period since the last audit and hunt for work that left no trace: firmware pushed by hand, cables moved, a replacement unit installed by a contractor. Every unrecorded change is a false lead waiting in the next outage investigation.
Step 5: Publish the undocumented and unreachable set
End the audit with two named lists and dates: assets with no documentation, and assets that would not answer. These lists are the audit's real deliverable. Everything else confirms what worked; these two pages are what prevents the next bad night.
Step 6: Schedule the deferred fixes
Not every gap gets closed this week. Give each deferred item an owner and a date, and put the next audit on the calendar now, roughly six months out plus after any big change or new site. An audit without scheduled follow-ups is a wish.
Verification
Every site on the map carries a reachable-or-flagged status with a date, every asset names the customer or service it supports, and the deferred-fix list has owners and dates attached. The standing test: a brand-new operator could take the night shift from this map alone and know whom each problem affects.
Limits of the audit
Read-only monitoring cannot diagnose assets that are unreachable or undocumented. Network, billing, and DNS mutations require operator authorization. Remediation stays with your team throughout.
An audit drawn from the desk is only as current as the most recent health signal. Where documentation is stale beyond checking, say so on the record instead of letting the map imply certainty it does not have.
How SignalNook carries the audit
SignalNook holds the asset map, collects read-only health signals, and keeps the change log beside the map so an audit becomes a review instead of a rebuild. Ask it for the unreachable and undocumented lists directly; they are kept as living records, not audit-day artifacts.
You decide which gaps get fixed first, and your team makes every change.
FAQ
Questions this guide is for
How often should a small operator audit assets?
About twice a year, plus after any large change or new site. The goal is keeping the undocumented set small, not performing ceremony.
Will the audit fix the devices it finds offline?
No. Network, billing, and DNS mutations require operator authorization. The audit produces the list; your team acts on it.
Which output matters most?
The unreachable-and-undocumented list. Those are precisely the assets that cost you an untraceable hour on the worst possible evening.
Start in the workspace
Shrink your undocumented set
Sign in or create an account. You return to the SignalNook conversation. Pull up the asset map, walk the checklist site by site, and leave with named lists instead of a vague unease about the map.