OBLYTECH Logo
OBLYTECH Logo
ServiceNow License Optimization: Roles, Responsibilities and RACI
Home / Solutions, Guides and Services / IT Asset Management: Guides and Services / License Optimization: Guides and Services / ServiceNow License Optimization: Roles, Responsibilities and RACI

ServiceNow License Optimization: Roles, Responsibilities and RACI

Understanding Software License Optimization in ServiceNow

Software License Optimization is the process of ensuring you pay for software you use, negotiate favorable terms, and maintain compliance with license agreements. It requires multiple roles: procurement teams who buy software, IT teams who deploy and manage it, finance who tracks spending, legal who reviews contracts, and operations who monitor usage.

A RACI matrix clarifies who is responsible for each activity, preventing gaps and overlaps. When everyone knows who makes decisions and who executes them, license optimization runs smoothly.

RACI for Vendor Contract Negotiation

Negotiating software license terms requires multiple parties. Procurement is Responsible for running the negotiation with the vendor. IT is Consulted (they understand your usage and can inform what terms matter). Finance is Responsible for reviewing pricing and budget impact; they are Accountable for ensuring cost is acceptable. Legal is Consulted (they review contract terms). The CIO is Accountable for approving the final agreement.

This separation helps the vendor face a unified front: IT and finance agree on terms before legal reviews them, and the CIO approves. Without clear roles, the vendor might negotiate separately with different teams, each making different commitments.

RACI for Software Inventory and Audits

Maintaining an accurate software inventory requires ongoing work. IT Operations is Responsible for deploying and managing software on devices; they provide inventory data (which software is installed where). The SAM team is Responsible for consolidating this data into ServiceNow and auditing it. Finance is Consulted (they need to verify spending against the inventory). IT Leadership is Accountable for ensuring inventory accuracy.

When audits reveal discrepancies (unlicensed software, unused licenses), the team whose software it is is Responsible for explaining and remediating. The SAM team is Responsible for tracking remediation.

RACI for Cost Optimisation Initiatives

When you discover an opportunity to reduce software spending (consolidate tools, renegotiate pricing, remove unused software), multiple parties are involved. The SAM team is Responsible for identifying the opportunity and proposing a solution. The affected business unit or team is Consulted (their workflow must be considered). Finance and IT are Responsible for evaluating feasibility and cost impact. The business executive sponsoring the tool is Accountable for approving the change.

This ensures you do not force change on a team without their input, but also ensures you act on cost-saving opportunities.

RACI for License Compliance

Maintaining compliance with license agreements requires enforcement. The SAM team is Responsible for monitoring usage against licensed quantities and for remediating non-compliance. The affected team (IT, development, business) is Responsible for cooperating with remediation (removing unlicensed software or purchasing additional licenses). IT Leadership is Accountable for ensuring non-compliance is addressed. Legal is Consulted if a compliance issue is severe and may result in vendor action.

RACI for Renewal and Budget Planning

Software licenses renew on a schedule. The SAM team is Responsible for tracking renewal dates and initiating the renewal process. Finance is Responsible for budget planning and approving renewal costs. Procurement is Responsible for negotiating renewal terms. The business owner of the software is Consulted (does the organisation still need this software). IT Leadership is Accountable for ensuring renewals happen on time and do not interrupt service.

A Sample RACI Table

Activity Procurement IT Operations SAM Team Finance IT Leadership
Vendor contract negotiation R C I R A
Software inventory collection I R R C I
License compliance audit I C R I A
Cost optimisation initiative C C R R A
License renewal planning R I R R A

Effective license optimisation is an ongoing discipline, not a one-time project. As your organisation evolves, software needs change, vendor offerings evolve, and new cost optimisation opportunities emerge. Regular review and adjustment of licensing strategies keeps your organisation aligned with both technical needs and financial objectives.

Continuous Monitoring and Improvement

Software license optimisation is not static. Regular monitoring of software usage, cost trends, and compliance status reveals improvement opportunities. Use Software Spend Detection in the Software Asset Workspace, which needs the Software Asset Management – Spend Detection plugin enabled, to track software spending across your organization and view what each department has bought. Identify trends: are certain teams over-spending, are there redundant tools that could be consolidated, are there unused licenses that could be recovered? Present these findings to stakeholders quarterly and use them to drive optimisation initiatives.

The combination of disciplined governance, clear roles and responsibilities, and continuous monitoring creates an environment where software spending is controlled, compliance is maintained, and the organisation gets value from its software investments.

Where a responsibility matrix fails in practice

A responsibility matrix for license optimization looks settled on paper and then falls apart at the first handoff. The common break is not between two obvious functions such as procurement and IT. It sits at the seam where a reclaimed license has to be removed from one record, released to a different cost center and reflected in the next renewal figure. Each step often has a different owner, and each owner can assume the next one will catch a mistake. This section is for the service owner or program manager who has to make the matrix work across those seams, rather than only draw it.

Handoffs that need their own rows

Many matrices list activities such as negotiation, inventory or compliance. The activities that cause trouble are the handoffs between them. Add a row for each handoff below and assign it separately, because a single “compliance” row hides the moment when a finding becomes a purchase request.

Handoff Who gives it Who must receive it Record that proves it happened What goes wrong when nobody owns it
Reclaimed seat to available pool Business owner of the product Software asset administrator Removal of the assignment and a changed entitlement count The seat stays on the cost center and is counted as used at renewal
Usage finding to renewal input Analyst who reviews usage Procurement lead who runs the renewal A dated note on the renewal record with the usage figure and its source The renewal is priced on the old headcount
Compliance gap to purchase request Compliance reviewer Budget holder for the affected team An approved request linked to the finding The gap is closed by installing a different version rather than buying
Contract amendment to live record Vendor manager Software asset administrator Updated license terms and effective date on the software record Deployment decisions are made against terms that no longer apply
Decommissioned product to retirement Application owner Configuration and asset team Retirement status with the date access was withdrawn The product keeps renewing because its support contract was never cancelled

How to build the matrix from the bottom up

Teams that start with a template often end with a matrix that describes an organization nobody works in. A more reliable route runs from the records outward.

  1. List every record type the program touches, such as installations, entitlements, contracts, renewals and access requests.
  2. For each record type, write down the event that creates it and the event that closes it.
  3. Name the person who performs each event today, not the person who ought to.
  4. Where two people both touch a record, choose one as the accountable owner and make the other responsible only for their part.
  5. Add the handoff rows described earlier and get a receiving owner to agree to each one.
  6. Test the matrix by walking one real product through a full renewal cycle and noting every point where someone asked who was deciding.

The final step is the one most teams skip. A matrix that has not yet been run against a real renewal is still a hypothesis.

Rules that stop accountability from splitting

Two rules prevent much of the damage. First, each row should have exactly one accountable party. When two names share accountability, the team often discovers that neither of them answered the question when it mattered. Second, a responsible party should be someone who can actually change the record. A finance analyst may be accountable for a cost figure but cannot release a seat in the deployment tool. If the person who does the work has no write access, the matrix is describing a permission that does not exist.

Escalation needs the same discipline. Decide in advance which disagreements go to the budget holder and which go to the program sponsor. A disagreement over whether a product is still in use is a technical question for the application owner. A disagreement over whether to renew at a higher price is a budget question. Sending both to the same forum slows down the first and rushes the second.

Signs that roles are not working

Watch for the quiet symptoms. A renewal that arrives with no usage note attached means the analyst’s handoff did not happen. A license reduction approved by finance but never executed points to a missing receiver. Repeated requests to “check with” a named person with no outcome recorded means the accountable owner is absent or unclear. These are better signals than any attendance figure for a governance meeting, and they should be reviewed at each cycle, not left for an annual audit to surface. The governance model guide sets out the forums where those reviews should happen.

When a full matrix is more than the estate needs

A small estate with a few contracts and one administrator does not need the full set of roles and handoff rows. In that case, a single page that names the owner of each renewal and each reduction decision is enough. Build the fuller matrix once the number of products, business units or contracts makes it impossible for one person to hold the whole picture in their head. The point of the matrix is to make responsibility visible, and it should not add meetings for their own sake.

Frequently asked questions about ownership

Who should own the software asset record when a team reorganizes?

The administrator who maintains the record should own it, but the business owner should confirm every change of cost center or user group within a fixed working period. Reorganizations move seats between teams without anyone deciding to, and the handoff row is the place to catch that movement.

Can a vendor manager also be the renewal approver?

It is possible in a small team, but it removes the check that the renewal deserves. Where it happens, the approval should be recorded against the budget holder so that someone other than the negotiator signs the price.

What if an application owner refuses to confirm usage?

Record the refusal as a finding with its date and escalate it to the program sponsor. Treating silence as confirmation is a common route to paying for a product nobody uses.

Should auditors be listed in the matrix?

Auditors are external to the process and should not own rows. They should be able to request the records that each handoff produces, which is the reason to define those records in the first place.

How often should the matrix be revisited?

Revisit it when a major contract changes, when a business unit is added or divided, and at the start of each renewal planning cycle. A matrix that is only reviewed when something breaks has already lost its use.

Next step

Matrices are often tested hardest at the first failed renewal, so it is worth getting the handoffs right before then.

What ServiceNow license optimization means and the order to do it in

ServiceNow license optimization is the routine of comparing what you are entitled to with what is actually installed and used, then acting on the difference before a renewal or audit forces the question. In most implementations it holds up when these things are in place, in order: trustworthy discovery data, entitlements recorded in a usable form, a measure of real use, and a named person who acts on each gap.

  • Know what is installed. Without reliable installation data, later figures are little more than guesses, so check coverage first.
  • Record what you own. Contracts, purchase evidence and the rights each one grants need to be turned into entitlement records. This is usually the slowest step because the source documents sit with procurement and legal.
  • Measure use, not just presence. A product installed on a laptop is not the same as a product someone opened last quarter. Decide what counts as use for each product before reading any report.
  • Reconcile and rank. Compare entitlements against installations and use, then sort the gaps by money and by risk, so the reduction and the shortfall are not treated alike.
  • Act and prove it. Reclaim, reassign, buy, or retire, and keep a dated record of what changed.

A decision rule for each gap

When installed numbers exceed entitlements, treat it as a compliance question first and a purchasing question second. When entitlements exceed use, treat it as a renewal question: the useful lever is the notice period, so the finding must reach the person negotiating before that date. A gap with no owner and no date is a report, not an optimization.

Finding First action Who needs it
Installed more than owned Verify the data, then decide to remove or buy Compliance reviewer and budget holder
Owned more than used Reclaim seats and attach the usage note to the renewal Procurement lead
Installed, not used Confirm with the application owner, then uninstall Software asset administrator
Not discovered Fix coverage before drawing conclusions Discovery owner

The licensing rules differ between vendors and even between products from one vendor, so the counting logic should be confirmed against each contract and on your own instance and release. For the wider overview, see the software license optimization overview and the software asset management guide. For usage data from other tools, the integration patterns page shows how to bring it in.

Frequently asked questions

Who should be the ultimate owner of software license compliance?

IT Leadership should be Accountable: if compliance fails or spending gets out of control, it reflects on IT leadership. But responsibility should be delegated to a SAM team or a dedicated SAM professional who has the expertise and authority to manage vendors, negotiate terms, and enforce policies. This separation allows leadership to provide oversight while a skilled team does the day-to-day work.

What should we do if a business team wants to use unlicensed software?

The team should submit a software request through the SAM process. The SAM team evaluates: is there a licensed alternative, what would it cost to license this software, what is the business value? Then SAM Responsible, Finance approves budget, and the team is Responsible for using only licensed software. This ensures conscious decision-making: if the team really needs unlicensed software, approve it; but do not allow ad-hoc deployment without awareness of cost and compliance implications.

How do we handle situations where a team and Finance disagree on whether a software license is necessary?

Escalate to IT Leadership who is Accountable for the final decision. The team advocates for business value, Finance advocates for cost control. Leadership weighs both and decides. This escalation path exists so conflicts do not stall optimisation efforts. Document the decision and the rationale, so if the situation comes up again, there is a precedent.

Talk to Oblytech

Planning, running or fixing a ServiceNow programme? Tell us where you are and we will suggest a sensible next step.

Contact us