Who is using which computer, phone, server and network device, which licence expires when, which subscription quietly renews itself: we gather all of it into a single record system. Assignment, warranty, the renewal calendar and decommissioning run in the same system; the inventory moves out of personal memory and into the organisation's records.
In most businesses the list of computers, laptops, phones, tablets, printers, servers and network devices sits in an Excel file, and nobody knows when that file was last correct. A new device is bought and given to someone, then that person changes department and the device goes with them. When a member of staff leaves, which devices have to be returned is usually a question answered from memory. When a stocktake is attempted at the end of the year, two lists appear: the finance team's fixed asset list and IT's own list. The two do not match. The gap is usually not lost devices; it is transfers that were never recorded. The problem is less the device itself than the fact that nowhere is it written who was given it, when, and in what condition.
The second and often more expensive layer is licences. Operating systems, office suites, design software, CAD, antivirus, ERP user rights and an ever-growing number of monthly subscriptions. Some of these are paid on an annual invoice, some renew automatically on a manager's card. Because the gap between how many licences were purchased and how many people actually use them is never measured, the loss runs in both directions: money is paid for seats nobody uses, while some programs run on more machines than were bought. The second is not only a cost issue but a serious compliance problem when a vendor audit arrives. Renewal dates are part of the same disorder; a contract is most often noticed on the day it renews.
IT asset management (ITAM) brings these two layers into a single record system. The hardware side, that is HAM (hardware asset management), tracks a device from its purchase date to its assignment, from its warranty to its maintenance history and finally to its decommissioning and secure disposal. The software side, that is SAM (software asset management), makes visible the gap between the rights purchased and what is actually installed; licence types, user numbers, contract terms and renewal dates are tied to a calendar. The aim is not to produce a tidy inventory list; it is to answer from the same place who currently holds each asset, when it expires and with whose approval it was issued.
Setting this up honestly means stating the limits from the start. Automatic discovery, meaning an agent installed on the device or a network scan, collects most of the inventory by itself; but manual records are needed for devices that never connect to the network, for operator panels on the production floor and for equipment used off site. The system cannot produce information nobody enters: if assignment approval is not obtained, software will not make up for it. Nor do we give any legal assurance on licence compliance; what we build is a table comparing the rights purchased with actual usage, and interpreting the contract remains with your legal and procurement people. Against that, in most organisations a correct assignment system and a renewal calendar alone pay for themselves in the first year.
Companies running hundreds of devices and dozens of contracts with a team of one or two people. In this setup the inventory information mostly sits in one person's memory; when that person goes on leave or leaves the company, which device is with whom and when which subscription expires does not stay with the organisation.
Structures where devices circulate between head office, factory, warehouse and branches. When the record of a computer moving from one location to another is not kept, the stocktake is done from scratch every year. Location-based inventory and assignment history are the two records most often asked for in these firms; when and at which location the stocktake was carried out is held in the same record.
Firms using design, project, communication and cloud tools on monthly subscriptions. When subscriptions are paid on the cards of different departments, nobody knows the total software spend; and what is more, the account of a departing member of staff often stays open for months. A subscription list with a defined owner, user count and renewal date delivers its first benefit here.
Businesses that undergo customer audits, run information security work or process personal data. In these organisations the device inventory, the assignment record and the data erasure certificate for a decommissioned device are concrete items asked for in an audit. Answering from memory is not possible; the record has to exist long before the day of the audit.
Every device is gathered into a single record: make, model, serial number, purchase date and value, warranty expiry, technical specification and current location. A barcode or QR label is attached to the device; stocktaking and assignment can be done from a phone using that label. Serial numbers are kept unique, so the same device does not multiply into two separate records.
When a device is assigned to a person or a department, the handover record is produced by the system and closed with a digital approval. The list of equipment to be issued when a member of staff joins, and the devices to be returned when they leave, come out automatically; devices that are not returned stay open and the person responsible is reminded. The assignment history stays in the device's record; who held a device, and in what order, can still be seen years later.
The licence rights purchased are held side by side with the number of copies actually installed or in use. The licence type (device-based, user-based, term subscription), the versions covered, the contract number and the vendor are recorded. Unused seats and excess installations thus become visible as two separate lists; both are money items.
Licence, subscription, maintenance contract and warranty expiry dates are gathered into a single calendar. Notifications go to the person responsible in advance of upcoming renewals; the decision date is planned ahead of the automatic renewal date. That way a contract comes up for discussion while it can still be dropped, not on the day it renews. During annual budget preparation, which item falls due when is read from the same list.
An inventory agent or a network scan can be used for networked devices; the machine name, hardware details and the list of installed software are collected automatically. The information that arrives automatically is compared with the manually kept records and the differences come out as a reconciliation list. Devices that are in the records but not on site, or on site but not visible in the records, surface in this list.
When a device reaches the end of its life, the process is closed with a record: the decommissioning approval, the data erasure or disk destruction record, the scrap or sale details and the notification to finance. Who the disposed device was transferred to, and on what date, stays in the same record. For devices that have held personal data, keeping the erasure record is a document specifically asked for in audits.
Device counts by department and location, annual cost per device, software spend and age distribution are reported. A comparison can be made with the fixed asset list in accounting; the difference between the two lists reveals unrecorded transfers and devices that were never written off. Renewal investment is then based on the age and fault history of the device rather than on a personal complaint.
We decide together which asset types will enter the system: only computers and phones, or servers, network devices, printers and field terminals as well. The Excel lists you hold, purchase records and the finance team's fixed asset list are collected. Starting with a narrow scope is the only thing that gets the first stocktake genuinely finished.
Which fields will be mandatory for each asset type, who can create a record and how an assignment is approved are set down in writing. The steps that run when someone joins or leaves are defined, and the labelling and numbering scheme is agreed. Installing software before these rules are clear goes no further than moving the disorder onto a screen.
We go out on site, the devices are labelled and recorded through a mobile stocktake. A comparison is made with the existing lists; missing, unowned and duplicate records are cleared out. The first stocktake is the most laborious step of the job and usually spreads over several weeks. But the reliability of the system throughout its life comes precisely from here; a first stocktake left incomplete is not easily made good later.
Software contracts, invoice records and card-paid subscriptions are reviewed; each is tied to an owner and a renewal date. Contract documents are attached to the record, so a renewal negotiation is entered without hunting for paperwork. Over-usage and under-usage appear as a table for the first time; in most organisations this table is the first concrete saving.
The assignment flow, renewal notifications and reports go live; usage is handed over to the IT and human resources teams. How the periodic stocktake will be run, and who will update the records and how often, are left in writing. After go-live, monitoring, fault fixing and update support continue.
Both manage assets, but different assets and different questions. EAM (enterprise asset management) tracks the production asset: machine, line, mould, facility, vehicle. Its questions are life, criticality, maintenance and investment decisions. ITAM tracks the information technology asset: computer, phone, server, network device and software licence. Its questions are assignment, licence rights, renewal and secure disposal. Both can be used together in the same factory; they meet on the procurement and accounting side. We clarify in discovery which asset belongs on which side.
We do not give a legal assurance and we cannot. What we build is a record system that compares the rights you have purchased with what you actually use and gathers the contract documents in one place. That makes it markedly easier to be prepared for an audit and to see the open points in advance. But interpreting the licence texts, the negotiation to be conducted with the vendor and the legal responsibility remain with your procurement and legal people. We prefer to state that limit from the outset.
No. The system also works with manual and barcode stocktaking; in many organisations the first stage is set up entirely that way. Automatic discovery is recommended where it is possible, because it makes detecting installed software easier and keeps the inventory up to date by itself. Manual records are needed in any case for operator panels on the production floor, devices on closed networks and equipment used off site. We decide together during discovery which method is used where.
It will not; their purposes are different. The accounting record is for depreciation and the financial statements; the official record stays in your ERP or accounting program and we do not rewrite it. ITAM answers the operational question: who holds the device right now, in what condition, and when does its warranty end. We match the two lists and report the differences. In practice this reconciliation reveals transfers and off-record devices that nobody has noticed for years.
The help desk and the ITSM side run the record of faults and requests; ITAM knows what the device discussed in that record actually is. When the two are connected, opening a fault record brings up the device model, its warranty, the person it is assigned to and its past faults automatically; devices that keep causing trouble also surface this way. We have described the service management side on a separate page; this page deals with the asset itself.
A labelled hardware inventory that has actually been counted; an assignment and return flow that works with handover records; a licence and subscription table comparing the rights purchased with usage; a renewal, warranty and contract calendar with notifications; decommissioning and data erasure records; cost and age reports by department. The source code, the data and the documentation belong to you.
In a 30-minute discovery call we listen to what you need and tell you honestly whether custom development or an off-the-shelf product is the better answer.
We tie risks to their owners and place a control, and the evidence for that control, against each risk. Policies run under version control, audit findings are tracked to a deadline, and a regulatory change lands with the right person. Work on personal data, occupational safety and the environment is read from a single dashboard under the same roof.
Details →We break projects down into a work breakdown structure, make resources and capacity visible, and put budget and actuals side by side. Milestones, risks and decisions sit in the same record; management reads the whole portfolio from a single dashboard and discusses which work comes first by looking at data.
Details →We design and build internal systems and subscription-based SaaS products that run in the browser, sit behind secure sign-in and show content according to role and permission. We shape them around how your business actually works, and we share the source code with you.
Details →We bring your field, sales and customer-facing work into a single app. We design iOS and Android applications around your needs, build them with offline mode and push notification infrastructure, and publish them on the App Store and Google Play.
Details →Desktop applications that keep going even when the internet drops, connect directly to barcodes and local hardware, and run fast on the shop floor and in the office. For Windows and macOS, with the source code yours.
Details →Web applications that are installable, work offline and meet the Core Web Vitals thresholds. Measured speed, a solid technical SEO foundation and an experience developed specifically for your brand.
Details →
