ServiceNow Asset Management Health Check
What an Asset Management Health Check Covers
An Asset Management Health Check is a comprehensive assessment of your IT Asset Management deployment, examining hardware and software asset tracking, license management, financial tracking, and asset lifecycle processes. We evaluate data quality, configuration effectiveness, integration completeness, and whether asset management is delivering value aligned to your investment. The health check identifies gaps, recommends improvements, and validates that you have visibility and control over your IT assets and spending.
Hardware Asset Assessment
We evaluate whether hardware assets are being tracked comprehensively: are computers, servers, printers, and network equipment being discovered and recorded, is data quality good (asset location, owner, status), are asset lifecycle stages (purchase, deploy, retire) being tracked accurately. We assess whether asset data is current—does discovery run regularly to detect changes, do manual processes keep non-discoverable assets up-to-date. We identify what asset types or locations have coverage gaps and recommend improvements.
Software Asset and License Management
We review software asset tracking: are installed applications being inventoried, is data accurate and current. We assess license management: are you tracking software license counts and allocations, can you demonstrate license compliance, do you understand your true license position to negotiate effectively with vendors. We identify over-licensed, under-used, or at-risk licenses costing more than necessary and recommend optimization opportunities.
Financial and Cost Tracking
We evaluate whether asset financial data—acquisition cost, depreciation, maintenance cost—is being tracked accurately and used effectively. We assess whether asset spending is being allocated to business units, cost centers, or projects appropriately. We identify opportunities to reduce asset-related costs through optimization or better contract management.
Recommendations and Roadmap
The health check produces a detailed report with findings organized by priority and effort. Quick wins—improvements requiring minimal effort with high value—are recommended first. Larger data quality initiatives or process redesigns are planned for phases. The report includes effort and value estimates, helping prioritize your asset management improvement roadmap.
Asset Accuracy and Data Quality Assessment
The health check evaluates accuracy of asset records: are asset locations correct, are ownership assignments accurate, are purchase dates and costs recorded correctly, are depreciation calculations valid for financial reporting. Data quality issues can lead to incorrect financial reporting, audit findings, and poor decision-making about asset disposal or replacement. We assess how asset data is maintained—automated discovery, manual entry, imports—and identify quality gaps.
Optimization and Cost Reduction Opportunities
The health check identifies cost reduction opportunities: over-licensed software that can be reallocated or eliminated, redundant hardware that can be retired, maintenance contracts on unused equipment, inefficient procurement processes. For each opportunity, we estimate savings potential and effort to achieve savings. This helps prioritize asset management improvement investments where effort yields highest return.
Financial and Compliance Reporting
The health check validates that asset financial tracking supports accounting and compliance reporting. Assets must be depreciated correctly per accounting standards. Disposal and write-off processes must be documented. Asset registers must reconcile with financial statements. We assess whether your current asset management supports accurate financial reporting and audit compliance.
Vendor Contract and License Optimization
Asset Management data informs vendor contract negotiations and license renewal decisions. If you can see exactly how much software you use and where, you can negotiate volume discounts or alternative licensing models. If you track hardware warranty status, you can optimize when and how hardware is maintained or replaced. Asset Management supports better financial and operational decisions about technology investments and relationships with vendors.
Depreciation and Financial Tracking
Asset Management supports financial accounting through accurate depreciation calculation. Assets must be depreciated according to accounting standards—straight-line, accelerated, or other methods. Depreciation calculations must be accurate for financial statements. Asset Management should be configured to calculate depreciation correctly and reconcile with accounting systems. This accuracy is critical for audits and financial reporting.
Audit Readiness and Compliance
Asset Management helps prepare for internal and external audits. Asset records should reconcile with fixed asset registers. Purchase dates, costs, and depreciation should match accounting records. Disposal records should be documented. Auditors will examine asset records and compare them with physical counts. Asset Management systems that maintain accurate, auditable records make audits smoother and reduce audit findings related to asset accounting.
Lifecycle Tracking and Disposal
Asset lifecycle management tracks assets from purchase through deployment to retirement. Assets should be marked as deployed, in storage, under repair, retired, or disposed. Accurate lifecycle data helps with financial accounting, compliance, and operational decisions. When assets reach end-of-life, proper disposal documentation ensures regulatory compliance. Asset tracking throughout lifecycle supports regulatory audits and environmental compliance for electronics recycling.
Reconciling a sample of records against evidence
This section is for the finance or IT leader who has noticed that the asset register and the fixed asset ledger do not agree, or that a purchase order and a live device cannot be matched. A health check is often requested as a general review, but the most useful piece of it is a reconciliation exercise. The aim is to take a sample of records and test each one against independent evidence, such as a purchase invoice, a device seen on the network or a signed disposal note. Testing the register against itself proves very little.
The sample should be drawn from more than one place. Records that came from discovery will look healthy because they are present on the network, which is exactly why they need to be checked against the purchase side. Records that were entered by hand, and devices held outside the normal estate such as loan equipment or items in storage, are where the gaps tend to sit. A sample taken only from the discovery list will therefore make the register look better than it is.
Evidence tests and what each one shows
| Test | Independent source | What a failure usually means |
|---|---|---|
| Record exists for each purchase in the period | Purchase invoices and goods receipts | Items received but never registered, or registered under a different name |
| Record shows the device in the location recorded | Physical check or a current network scan | Moves not recorded, or a device that was never deployed |
| Owner on the record is the current holder | Joiner, mover and leaver records from HR | Ownership left behind after a departure |
| Cost and purchase date match the invoice | Finance ledger | Estimated values entered instead of actual cost |
| Retired record has a disposal note | Disposal or certificate of destruction | Ghost records still counted in totals |
Each row of the table is a test that can be run by someone who did not configure the register. That independence is what makes the result credible to auditors, and it is also what makes it uncomfortable for the team that maintains the data. The hardware asset management measures give a sensible set of figures to report back once the sample has been tested.
Running the reconciliation in a defensible order
- Agree the population for the sample, including the date range, asset classes in scope and any records excluded for a stated reason.
- Select records at random from each source, not only from the newest or highest value, and keep the selection list so the test can be repeated.
- Pull the independent evidence before opening the register, so the reviewer is not influenced by what the record says.
- Record each test as pass, fail or cannot be verified, and keep the reason for every fail in plain words.
- Group the failures by cause, such as missing purchases, unrecorded moves or stale ownership, because the fixes differ.
- Agree with finance which failures affect reported values and which only affect operations, since the response to each is different.
When a health check should not be used as a cost exercise
The reconciliation exercise is sometimes requested as a way to find savings, by identifying licenses and devices nobody uses. That can work, but only after the register is trusted. Savings identified from a register that is wrong about ownership and location tend to be disputed, and the disputes take longer than the savings are worth. A better sequence is to reconcile first, then look for optimization in the records that passed.
Another failure is treating a failed sample as proof that the whole register is unusable. A failure rate concentrated in one site, one supplier or one period points to a process gap that can be fixed in that area. A failure rate spread evenly across the register points to a design problem, and that calls for a different kind of work. Once the reconciliation has separated those two patterns, the optimization service route is the next step to consider.
Questions finance and IT ask about reconciliation
How large should the sample be?
Large enough that a reviewer can explain why it was chosen, and large enough to show failures in each source. A small sample drawn from one source proves little about the others. The sample size should be agreed with the auditor or finance lead before testing starts.
What if we cannot find the physical device?
Record it as cannot be verified, not as a fail, and check whether the device was disposed of, lost or moved to a location that is not in the scan scope. A missing device is a control finding, and it should be escalated according to the asset policy, not quietly removed from the register.
Who should perform the tests?
Someone who did not enter the records, and ideally someone who sits outside the team that administers the platform. Independence matters more than seniority, and the reviewer should be able to explain each test to a non-technical reader.
Should we correct records during the review?
Not during the testing itself. Corrections change the evidence trail. Record the findings first, then agree and log each correction as a separate change with the reason, so the before and after state can be shown later.
Next step after a reconciliation
The failures from a reconciliation are most useful when they are sorted by cause before anyone proposes a fix.
Frequently asked questions
Why does an asset management health check test records against outside evidence rather than against the register itself?
Checking the register against its own contents proves very little, because a wrong record agrees with itself. The health check takes a sample of asset records and tests each against an independent source: a purchase invoice, a current network scan or a physical check, HR joiner and leaver records, the finance ledger, or a signed disposal note. A record that fails one of these tests points to a specific gap, such as items received but never registered, moves not recorded, or ghost records still counted in totals.
Where should the sample for an asset reconciliation be drawn from?
From more than one source. Records that came from discovery look healthy simply because the device is on the network, so they need checking against the purchase side. Hand-entered records, loan equipment and items in storage are where gaps tend to sit. The sample should be selected at random from each source rather than from the newest or highest-value items, the selection list kept so the test can be repeated, and the population agreed in advance with finance or the auditor.
Can the health check be used straight away to find savings on unused licences and devices?
Only once the register is trusted. Savings identified from records that are wrong about ownership or location tend to be disputed, and the disputes can outlast the value of the saving. The sequence that holds up is to reconcile first, sort the failures by cause, and then look for optimisation among the records that passed. Oblytech can run the reconciliation independently of the team that maintains the data, which is what makes the result credible to auditors.
Related guides
Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.
Contact us