Combine several sources
Compare invoices, existing administration records and information from teams. No single source necessarily shows everything. An application might be billed annually or through another organization. Mark unclear entries rather than guessing their state.
Record the product, contract or account reference, owner, billing rhythm and next known renewal date. Credentials do not belong in this list. A reference to the responsible administrator is enough.
Add purpose and dependencies
Explain the tool’s purpose in one sentence. Marketing is often too broad; “monthly delivery of the client newsletter” identifies an actual process. Note important connections to other services where a change could interrupt them.
Distinguish the person responsible for licensing from the person using the tool every day. They may differ. Usage questions need the operational perspective, while contract changes need the intended administrative route.
Resolve uncertainties systematically
Choose several entries without an owner or clear purpose and ask targeted questions. Give unanswered questions a review date. Unknown is a working state and should not remain for months without a next step.
When similar applications appear, compare their actual tasks first. Sharing a product category does not automatically make their functions interchangeable. Consolidation needs its own examination of data, roles and workflows.
Update the inventory when software is purchased, responsibility changes or a subscription ends. A one-time inventory quickly becomes outdated. Its value comes from connecting the next renewal or inquiry with a reachable person and an understandable purpose.
Track trial accounts separately from paid subscriptions without making them invisible. A free account can still contain working data or connect to another service, so its organisational owner should also be identifiable.
