A home security system can contain dozens of devices, but most owners cannot quickly answer basic questions about them: Which model is on the back door? Who owns the outdoor cameras? When does the hub warranty end? Which sensor uses a CR123A battery? A home security equipment inventory turns those loose details into a record you can use during support calls, insurance claims, moves, outages, and replacements.
This guide is about the physical and commercial record for each device: model, serial number, location, owner, purchase date, warranty, power source, network role, and replacement status. It complements a broader home security system documentation checklist, which covers accounts, codes, contacts, and service records. Keep serial numbers, account identifiers, and receipts in a private encrypted vault or another access-controlled location. Never publish them in a shared spreadsheet or a public photo.
What the equipment inventory should answer
A useful inventory should let a homeowner, trusted household member, or technician answer five questions without opening every device:
- What is it? Manufacturer, product name, exact model, hardware revision, and serial number.
- Where is it? A plain-language location plus the alarm zone, camera name, or room name used in the app.
- Who owns and supports it? Owner, installer, retailer, monitoring provider, purchase date, and warranty end date.
- What keeps it working? Battery type, wired power, network path, hub dependency, storage location, and subscription dependency.
- What happens next? Last test date, known faults, expected replacement year, and disposal or transfer status.
The inventory is not a password list. Do not place alarm PINs, recovery codes, Wi-Fi passwords, or encryption keys in the same ordinary spreadsheet. Those belong in a password manager, with recovery tested using a separate security account recovery audit.
Use one row per physical device
Create one row for every hub, keypad, siren, sensor, camera, lock, bridge, range extender, recorder, router, backup battery, and dedicated power adapter. Bundles are useful on receipts, but they hide device-level differences. Two door sensors bought together can have different serial numbers, battery ages, locations, and replacement histories.
| Field | Example | Why it matters |
|---|---|---|
| Inventory ID | SEC-023 | Stable reference even when the app name changes |
| Device type | Door/window sensor | Groups maintenance and spare-part needs |
| Brand and model | Exact label text | Prevents ordering the wrong accessory or battery |
| Serial or MAC | Stored privately | Supports warranty, pairing, and theft records |
| Physical location | Garage side door, frame | Lets another person find the device |
| App or zone name | Zone 08 / Garage Side | Connects the physical device to alerts and logs |
| Power | 1 × CR123A | Drives the spare-battery list |
| Purchase and warranty | Receipt link; end date | Speeds support and replacement claims |
| Owner | Homeowner / landlord / provider | Prevents accidental disposal or transfer |
| Last test | 2026-08-14, passed | Shows whether the record matches reality |
Give each device a stable inventory ID. A small removable label inside a battery compartment or on the power lead can connect the physical device to its row. Do not put a full serial number, account number, alarm code, or property address on an exterior label.
Start with the alarm hub and communication path
The hub is the dependency that ties most of the system together. Record its exact model, serial number, hardware revision, installed location, power adapter rating, backup-battery type, cellular module, Ethernet or Wi-Fi connection, and monitoring account reference. Note whether the hub is owned, financed, leased, or supplied by a monitoring company.
Then document the path an alarm uses to leave the property. That can include a router, modem, cellular radio, range extender, bridge, and subscription plan. Record the device, not passwords. If the router or modem is shared with the household network, link to its separate private network record rather than copying credentials into the inventory.
For a new DIY system, confirm what is included before building the list. For example, the Abode Smart Security Kit product page shows the current kit components, while the Abode plans page separates equipment from optional service. Vendor pages can change, so save the invoice or order confirmation as the purchase record.
Map sensors to both a place and a zone
Sensor names in an app are not always enough. “Back Door” could mean the patio slider, basement bulkhead, or garage entry. Record the physical description, the app name, and the alarm zone number where one exists. Include:
- Door and window contacts, including whether each is recessed or surface-mounted.
- Motion sensors, with room, mounting height, and pet-immunity setting.
- Glass-break, vibration, water, temperature, smoke, and carbon-monoxide devices.
- Outdoor contacts and sensors, including weather exposure.
- Keypads, key fobs, panic buttons, and sirens.
For life-safety devices, record the manufacturer’s printed replacement date and the date code on the unit. Do not treat a passed app status as proof that a smoke or carbon-monoxide alarm is within its service life. Follow the device maker’s test and replacement instructions.
Add battery chemistry and quantity rather than writing only “battery.” A sensor that needs two lithium AA cells should not be serviced with alkaline cells merely because they fit. Use the inventory to build a spare-parts list, then verify devices on the schedule in the home security battery maintenance guide.
Document cameras, doorbells, and recording
Camera records need more than model and location. Add lens direction, mounting height, power method, Wi-Fi band or Ethernet connection, storage type, subscription, and the app account that controls sharing. Record whether footage is stored in the cloud, on microSD, in a base station, or on an NVR.
For each camera, include these fields:
- Camera name in the app and its real physical location.
- Model, hardware revision, serial number, and MAC address where available.
- Power source and the location of any transformer, injector, adapter, or breaker.
- Storage method, retention window, subscription renewal date, and recorder channel.
- Privacy zones, audio setting, household consent notes, and shared-user access.
- Last live-view, recording, night-vision, notification, and outage test.
Take one private installation photo showing the mount and cable route, but avoid capturing keypad codes, Wi-Fi labels, recovery codes, or the full street view. If a camera later fails, the inventory can distinguish a device fault from a missing subscription, dead power supply, lost Wi-Fi path, or full local storage.
Record smart locks and physical access hardware
A smart lock row should identify both the electronic product and the door hardware it depends on. Record the lock model, interior and exterior finish, cylinder or keyway, door thickness, handing if relevant, bridge or hub, battery type, and whether a mechanical key exists. Store key codes and access PINs somewhere more restricted than the equipment list.
Ownership matters here. A renter may own the keypad module while the landlord owns the original deadbolt. A professionally installed lock may remain part of the property. Add a “restore at move-out?” field and link it to the lease, installation approval, or handover note.
Also list non-smart dependencies: strike plates, door closers, gate latches, garage-door controllers, intercoms, and key safes. They can determine whether a digital access event actually results in a locked door.
Track power, network, and storage dependencies
Many apparent device failures begin somewhere else. Build parent-child fields so each device points to the hub, bridge, router, switch, recorder, or power supply it needs. A simple dependency entry might read: “Camera SEC-031 → PoE switch SEC-006 → router SEC-004 → UPS SEC-002.”
For dedicated power hardware, record:
- Adapter voltage, current, connector, and manufacturer part number.
- UPS model, battery replacement date, tested runtime, and protected outlets.
- PoE switch model, port number, power budget, and spare capacity.
- NVR or base-station drive size, drive age, and replacement status.
- Solar panel model, cable route, and seasonal charging limits.
Do not assume a UPS is healthy because its indicator is green. Record the last real runtime test and compare it with the method in the home security UPS runtime test.
Separate ownership, lease, finance, and service
“Installed at this address” does not always mean “owned by the homeowner.” Use separate fields for equipment owner, service provider, payer, and monitoring contact. Mark equipment as one of the following:
- Owned outright: bought and retained by the household.
- Financed: ownership or lien conditions may remain until paid.
- Leased: provider return rules may apply.
- Landlord-owned: should normally stay with the property.
- Installer-supplied: verify the contract before replacement or disposal.
- Borrowed or trial: add a return date and original packaging location.
This section prevents expensive mistakes during a move, cancellation, insurance claim, or contractor handoff. Attach the relevant contract or receipt link, but restrict access to documents containing personal or payment data.
Build the warranty and purchase record
For each purchase, save the retailer, order number, purchase date, price, payment method category, receipt file, warranty term, and warranty end date. The payment-method category can be “credit card” without storing the full card number. Record any extended warranty separately.
When equipment is replaced under warranty, do not overwrite the old serial number. Close the old row with its failure and disposition, then create a new row for the replacement. Link the two records with the support case number. This leaves a clean history for repeat faults and future claims.
If a failure has already occurred, the home security warranty claim checklist covers evidence, support contact, shipping, replacement, and retesting. The inventory should make that process faster, not become the claim itself.
Store the record without creating a security leak
An equipment inventory is useful to a thief if it reveals the exact device map, camera blind spots, alarm zones, or serial numbers. Treat it as sensitive household data.
- Use an encrypted password-manager note, encrypted file vault, or access-controlled document system.
- Require multifactor authentication on the account holding the live inventory.
- Limit access to the smallest practical group.
- Keep a redacted emergency copy that omits serials, costs, and network identifiers.
- Do not email the full inventory unless the file is encrypted and the recipient is verified.
- Remove former residents, installers, and caregivers when their access ends.
A trusted household member may need a recovery path if the primary owner is unavailable. Keep that instruction separate from day-to-day credentials and review it with the home security digital estate plan.
Keep a redacted offline copy
Cloud access can fail during an outage, account lockout, or emergency. Keep a redacted offline copy with inventory IDs, device types, locations, battery types, service contacts, and basic shutoff instructions. Omit alarm PINs, Wi-Fi passwords, serial numbers, recovery codes, and payment details.
Date the copy and define where the live encrypted version is stored. A stale printout is worse than no printout when it sends a helper to the wrong device. Replace the offline copy after major installation changes and shred the old version.
Run the 45-minute home-security equipment inventory audit
This audit tests whether the record matches the installed system. It is not a full alarm acceptance test. Notify household members first, use test mode where needed, and avoid opening life-safety devices unless the manufacturer permits it.
Minutes 0–5: define scope and safety
- Choose the property, system, and owner for this inventory.
- Confirm monitoring is in test mode if any sensor will be triggered.
- Open the encrypted inventory and note its last review date.
- Prepare a phone or camera for private label photos.
Minutes 5–15: verify the hub and network chain
- Match the hub, keypad, siren, router, bridges, and recorder to their rows.
- Check model, serial, power adapter, location, and owner.
- Confirm cellular, Ethernet, Wi-Fi, and backup-power dependencies.
- Flag any unidentified adapters, unused bridges, or missing labels.
Minutes 15–25: sample sensors and locks
- Select one perimeter sensor, one interior sensor, and one life-safety device.
- Match each physical location to the app or alarm zone.
- Confirm battery type and printed replacement date where relevant.
- Check one smart lock for model, power, bridge, owner, and mechanical fallback.
Minutes 25–35: sample cameras and storage
- Match one indoor and one outdoor camera to their inventory rows.
- Confirm power, network, storage, subscription, and privacy fields.
- Verify that the named recorder channel or local card exists.
- Note any camera whose physical direction no longer matches the record.
Minutes 35–42: check purchase and ownership records
- Open one receipt and confirm its file link still works.
- Check one warranty end date against the purchase date and stated term.
- Identify any leased, financed, landlord-owned, or installer-supplied equipment.
- Confirm replaced devices have closed records rather than overwritten serials.
Minutes 42–45: close the audit
- Record every mismatch as an owner, action, and due date.
- Update the last-audited date and next review date.
- Export a fresh redacted offline copy if the live record changed.
- Log structural changes in the home security system change log.
Review cadence
Review the inventory quarterly and after any purchase, replacement, move, warranty claim, account transfer, contractor visit, or monitoring change. A quarterly review can sample devices; an annual review should walk every row. The record is complete only when another authorized person can locate the device, identify its owner, find the right spare part, and start a support case without guessing.
Common inventory mistakes
- One row per bundle: hides individual serial numbers, locations, and battery ages.
- App name only: becomes ambiguous when rooms or doors are renamed.
- Overwriting replaced equipment: destroys warranty and failure history.
- Storing secrets in the sheet: turns a maintenance record into a credential leak.
- No ownership field: causes trouble during a move or cancellation.
- No dependency map: makes a router, bridge, power, or storage failure look like a device failure.
- No test date: records what was installed, not what is currently working.
Frequently asked questions
Should I put alarm codes or Wi-Fi passwords in the inventory?
No. Keep credentials and recovery codes in a password manager or another more restricted vault. The inventory can point to that vault without copying secrets into the document.
Do I need serial numbers for every sensor?
Record them when the manufacturer provides them and when they help with pairing, support, warranty, or theft records. If a low-cost sensor has no visible serial number, assign your own inventory ID and record its model, location, zone, and purchase batch.
Can I use photos instead of typing labels?
Use both. A private label photo is useful evidence, but typed fields are searchable and easier to compare. Protect photos because they can expose serial numbers, MAC addresses, QR pairing codes, and installation details.
How often should I update a home security equipment inventory?
Update it immediately after a device change and review it quarterly. Run a full row-by-row audit at least annually and before a move, insurance claim, major service visit, or ownership transfer.
Is this the same as a home contents inventory?
No. A home contents inventory supports insurance documentation for household property. This record focuses on the security system itself: devices, dependencies, ownership, support, warranties, and maintenance.