Every IT team has started a telecom inventory. Most have abandoned one. The spreadsheet that was going to hold every circuit, phone and contract grows for a few weeks, then an office moves, two people leave, and nobody trusts it anymore.
The inventories that survive are the ones built around the questions people ask. In telecom those questions are consistent: what do we have, where is it, what do we pay for it, and when does it renew. Record what answers those and resist the rest.
Record these for every service
- Provider and the product as the provider names it on the bill.
- Account number and the circuit or service identifier, because support will ask for both.
- The location it serves, as a street address, with an on-site contact.
- Monthly recurring charge and the term, with the contract or order attached.
- The renewal date and the notice deadline, which is usually earlier.
- An owner inside your company who answers questions about it.
- Status: active, being installed, in dispute, or being disconnected.
Group services the way the bill groups them
Two hundred identical phone seats are one record with a quantity of two hundred. Two hundred seats across three license types are three records. Each internet circuit is its own record because the address, the price and the renewal date differ. The rule is to make a separate record when the price, the location, the contract or the identifier differs, and otherwise to use a quantity.
Leave these out
Do not try to track individual handsets, headsets, patch cables or who sits at which desk. Those change weekly, nobody updates them, and the inaccuracy spreads doubt to the records that matter. Keep hardware to what is on a lease or a rental line on a bill. Keep people to the one owner per service.
Keep it accurate by using it
An inventory stays current when it is the place people go to do the work: to open a ticket, to check a bill, to start a renewal. If the inventory is a report that someone updates after the fact, it decays. Tie each bill, ticket and renewal to the service record and the record updates itself as the work happens.
DemarcLabs is built on exactly this structure: contract, billing account, service and quantity, with every bill, ticket, project and renewal attached to the service it concerns.