ServiceNow Hardware Asset Management: Roles, Responsibilities and RACI

Procurement and Sourcing Responsibilities

The procurement team initiates the hardware asset lifecycle. They define what equipment to purchase, negotiate vendor contracts, and manage the purchase order process. In an asset management RACI, procurement is responsible (R) for sourcing hardware and accountable (A) for the purchasing decision. They consult with IT operations and end-user departments on specifications, but procurement makes the final purchasing decision. Finance approves the budget before procurement commits to a purchase.

Procurement provides information to Hardware Asset Management: purchase order number, vendor, cost, delivery date, warranty details, and service level agreements. This data becomes the asset record when the equipment arrives. If procurement does not provide accurate initial data, the asset management system starts with incomplete information and remains inaccurate.

Receiving and Initial Asset Registration

When hardware arrives, someone (warehouse staff, IT operations, or the receiving department) counts it, verifies condition, and compares it to the purchase order. This person registers the asset in Hardware Asset Management: they enter or scan the serial number, document the condition, and record the receipt date. In the RACI, receiving is accountable (A) for asset registration. They must not skip registration or defer it; assets that are not registered become invisible to inventory and asset tracking.

The finance team is consulted (C) on receipt because hardware must be capitalized (added to the balance sheet) once it is received and accepted. Accounts payable cannot pay the invoice until receiving confirms the asset arrived and matches the purchase order.

IT Operations and Asset Deployment

IT operations receives hardware from receiving and deploys it to end users. They configure the hardware (install operating system, apply patches, configure network settings), assign an asset tag, and deliver it to the user. IT operations is responsible (R) for asset configuration and deployment. They update Hardware Asset Management with deployment details: who the asset is deployed to, what location, what configuration.

IT operations also maintains hardware throughout its lifecycle. They install patches, replace failed components, and retire equipment at end of life. They are consulted (C) on warranty claims and asset repairs. If an asset fails and must be replaced, IT operations initiates a request in Hardware Asset Management.

Finance and Cost Tracking

Finance owns the asset cost data. They capitalise new hardware purchases, track depreciation, and manage asset disposal (salvage value, write-off). Finance is accountable (A) for asset cost and depreciation accounting. They consult with IT operations on asset retirement dates so they can correct the depreciation schedule. They approve cost-saving decisions (repair vs. replace, lease vs. buy).

Finance reconciles Hardware Asset Management records against the general ledger quarterly or annually. If asset records in Hardware Asset Management do not match finance records, the discrepancy must be investigated. A missing asset in Finance means it was not expensed or depreciated correctly. A missing asset in Hardware Asset Management means it is not tracked and could be lost or stolen.

Platform Owner and Business Unit Management

The platform owner is responsible (R) for the Hardware Asset Management system itself: configuration, reporting, access control, and data governance. They work with IT operations, procurement, and finance to design the asset lifecycle process. They design RACI matrices and approval workflows within Hardware Asset Management.

Individual business units or department managers are informed (I) of asset inventory and are consulted (C) when decisions affect their equipment. A department manager should know what equipment their team has, but the platform owner makes system-wide policy decisions. A department head does not have the authority to retire equipment or repurpose it without approval from IT operations and finance.

Hardware Asset Management RACI Table

A RACI table clarifies who does what for common hardware asset decisions. For “Approve purchase of new equipment,” procurement is responsible and accountable, finance is consulted, and IT operations is consulted. For “Register received asset,” receiving is responsible and accountable, finance is informed. For “Approve asset retirement,” finance is responsible (asset accounting impact), IT operations is accountable (execution), and department head is informed. This table prevents duplication, omission, and confusion about who should act.

Escalation and Decision Authority

Define escalation: if procurement and IT operations disagree about hardware specifications, who decides? If IT operations wants to retire equipment and finance says no (depreciation not complete), who decides? Usually an equipment governance committee (finance, IT, procurement leadership) makes contentious decisions. If there is no escalation path, disagreements paralyse the asset lifecycle.

Map the people to the moments in a device’s life, not to job titles

Hardware responsibilities are easiest to get wrong at the moments when a device changes hands: the day it arrives, the day it moves to a new desk, the day its owner leaves, the day it is sent for repair and does not come back. A role matrix that lists functions by department does not show who acts at those moments. A RACI built around the lifecycle does, which is why the matrix here is built around events rather than teams. Responsible, accountable, consulted and informed are only useful if each event has exactly one accountable party and at least one responsible party who can actually do the work.

Many failed matrices break one of three rules. An event has two accountable parties, so neither answers when it goes wrong. An event has an accountable party who has no access to the record. Or the custodian, who is the person most affected, is only ever informed, so the register never hears from them.

A lifecycle RACI for the events that create most disputes

The matrix below uses one row per event. Each event has a single A. The roles are generic, so map them to your organization’s titles before use. The reading to check is the custodian column: if it is never R or A for anything, the process is making the person holding the device a passive party.

Read the table as a set of questions rather than a finished answer. Each cell should prompt the owner to say what that party actually does, and where it is evidenced.

A walk-through to test the matrix before it is adopted

A matrix looks sound on paper and fails the first time someone is off sick. Test it against real cases before the process goes live, using the steps below.

1. Pick one device from each of three real situations: a recent issue, a recent leaver and a recent repair. Use records that are complete, not the difficult ones.
2. For each event in that device’s history, name the person who actually acted, and check that the matrix gives the same answer.
3. Repeat the exercise with the most awkward case you can recall, such as a device found in a meeting room with no record of who had it.
4. Where the matrix and the practice disagree, decide which one is wrong and change it. Record the change against the event so the reason is kept.
5. Confirm that every A has a deputy with the same authority, so an absence does not leave an event without an accountable party.

Common RACI failures in hardware and how to correct them

The failures below recur because they feel efficient at the design stage. Each has a correction that costs little to set up.

Keeping the matrix current as people change

A RACI often goes stale faster than the process it describes, because the people who hold roles change more often than the design. Attach each role to a group rather than a named individual, so that membership can change without editing the matrix. For keeping those memberships accurate, the assignment groups governance note covers how to keep group ownership clear. Review the matrix whenever a team is restructured, and check it against the leaver and joiner processes, because those are the moments when a role is most likely to be left unfilled.

Can the asset manager also be the receiving desk lead?

In a small estate, yes, but the two roles should be recorded separately so the person who receives a device is not the only person who can accept it as correct. Where they are the same person, add a second check on high-value or data-bearing items.

Should line managers be the custodians of their team’s devices?

Line managers are often the best-placed approvers of an assignment, but they are usually not the holders. Record the holder as the custodian and the line manager as the approver, so that a change of role does not silently transfer equipment.

How does a RACI handle contractors and temporary staff?

The same way, with one addition: the sponsoring manager is the accountable party for return. Contract end dates are a common source of unreturned equipment, so the return event should be tied to the contract record rather than to a person’s employment record.

What is the minimum evidence for an accountable decision?

A record of who made the decision, when, and on what basis, attached to the asset. A decision that exists only in an email thread cannot be traced by a later reviewer, and it is usually the first thing an audit query asks for.