OBLYTECH Logo
OBLYTECH Logo

ServiceNow Software Reclamation Rules: Thresholds and Exceptions

A ServiceNow software reclamation rule tells your software asset management process which software to flag as unused, and when to flag it. You set the inactivity test, the notice behaviour and the exceptions, and the rule produces removal candidates for a person to review.

What ServiceNow software reclamation rules decide and what they leave to people

A rule produces removal candidates, and what happens to each one depends on your configuration and on a reviewer. It reads usage data for a product, applies the inactivity test you configured and produces candidates that a reviewer approves, skips or closes. Keep that separation in mind when you design it. A rule set too aggressively takes access away from people who need a tool at the end of a quarter, and a rule set too gently leaves paid licences idle for another year.

The usage data is the part that teams often underestimate. Whether a rule can see a product being used depends on how usage is collected in your environment. Desktop software, server software and SaaS applications reach the platform by different routes, so a rule that works well for one type can mislead for another. Confirm which usage source feeds each product before you trust its candidates.

Defining unused so it matches how each product is really used

Teams often start with a simple question: has anyone used this recently? That works for a tool people open every day. It fails for tools used in bursts, such as reporting or design software used at the end of a project, where a long quiet stretch is normal and not a sign of waste.

Some rule configurations let you combine an inactivity period with a minimum amount of use inside a set window. Which options appear depends on your release, so check what your instance offers rather than assuming. Write the definition down per product family rather than once for the whole estate:

  • Daily-use productivity tools: a short inactivity window, reviewed often.
  • Project or seasonal tools: a longer window, with the expected quiet periods written into the review notes.
  • Specialist or engineering tools with few named users: review the named users before reading the usage figures.
  • Anything tied to a contractual minimum: do not reclaim below that level until someone has checked the contract.

Choosing a reclamation type and the usage window behind it

The reclamation type decides what the rule measures. Total Usage Time is the default: it adds up the hours a product was used over a window of one to six months and flags it when the total falls below the hours you set. The six-month option is only available for installed software. Last Used Date ignores hours and checks how recently the product was last used.

Read the window alongside the threshold. A product that was busy early in a six-month window can still pass while sitting idle now, so a shorter window usually gives a clearer picture of current use. Last Used Date tends to suit tools that are either in use or dormant. For the wider picture, read how reclamation works in ServiceNow.

Setting notification and grace periods before anything is removed

A rule that removes access without warning produces the complaints that get it switched off. Notifications give the assigned user or their manager a chance to say the software is still needed. The rule has a Notify user option and a Days before auto-reclamation field, so review both in your own instance. How ServiceNow notifications and email handling are set up is the place to start, and the usual notification and email mistakes are worth reading before go-live.

The grace period is a judgment call. It has to be long enough that a manager away for a week can still respond, and short enough that unused licences do not wait a full renewal cycle. Ask the people who will receive the messages what they can realistically act on, then test with one product before you roll the approach out. A notice that does not reach its recipient gives that person no chance to respond, so send a test message and confirm it arrives.

Suites, components and SaaS applications each need their own check

A software suite is usually one parent item with components beneath it. A rule that evaluates components separately can flag a component as unused while the suite is in active use, or the reverse. Before you trust a rule for a suite, check how the parent and its components are each evaluated, and walk one known suite through by hand. The software model is what sets out how products and their components relate, so read that first if the parent and child items look inconsistent.

SaaS and single sign-on applications bring a different problem. For each direct SaaS or SSO integration, the activity that counts is defined differently, such as a login or a specific action, so a rule can report a subscription as unused when that signal was not collected. Confirm that the usage signal for each SaaS application is actually arriving before you rely on its candidates. If your vendor portal holds the real seat assignments, decide up front which system is the record of who holds a seat. The integration patterns for software license optimization describe how that data normally reaches the platform.

Exceptions you can build into a rule and what each one changes

Four settings narrow what a rule flags or stop it creating removal work. Unticking Create reclamation candidate still pulls usage in, so you can watch a product without generating removal candidates. The percent utilised target, which appears for engineering licences, sets how much of its rights a product must use.

With a 60 percent target, a product used at under 60 percent gets a candidate for the rights that sit unused. For SAP named users, minimum transaction codes let a named user avoid reclamation by keeping enough of the listed codes active.

Filter conditions set on a suite parent carry down to its components, and the filter field on a component is no longer editable. A filter set at rule level applies to all the products in the rule, and it is available for installed or subscription software.

Reviewing removal candidates and existing rules after an upgrade

A removal candidate needs a decision. Typical outcomes are approving the removal, skipping the item for this cycle, or closing the candidate. The labels and their effects depend on your release, so confirm them in your instance before you write a review procedure around them. Record the reason for each skip, because without it the same items come back cycle after cycle and nobody remembers why they were kept.

Upgrades deserve their own check. An upgrade can change how existing rules behave, and a rule written against one release may need review against the next. Before an upgrade, note your current rules and their thresholds. After it, compare the candidate list from a test instance with the list you had before. Any difference is either a change you understand or a regression to report. You can find the wider set of guides in the software license optimization section.

SaaS and SSO rules start from default inactivity thresholds

Some SaaS integrations use a 60-day analysis period. Treat any fixed period as a starting point, and compare it with how often each team actually opens the application before the first run.

Frequently asked questions about reclamation rules

What is a reclamation rule and what does it flag?

A reclamation rule is a configured test that checks usage data for a piece of software and marks it as a removal candidate when it meets your definition of unused. It flags items for review. Whether software or access is actually removed depends on how your instance is configured and what the reviewer decides. With Notify user selected, the rights are reclaimed automatically if the user does not reply within the Days before auto-reclamation period, so check that setting before you rely on the rule.

Should users be notified before a licence is reclaimed?

Usually, yes. A notice gives the user or manager a chance to confirm a real need, which avoids disputes after removal. Set the grace period by asking how long a manager needs to respond, and send a test notice to confirm it arrives before you rely on it.

Why should automatically created rules be reviewed?

Automatically created rules use default assumptions about usage, thresholds and scope that may not match your estate. For SaaS and single sign-on applications in particular, a default can flag a product whose usage signal is not being collected. Read each one and confirm its scope before it runs against live data.

Do existing rules carry over unchanged after an upgrade?

Do not assume they do. Behaviour can change between releases, so compare candidate lists before and after the upgrade in a test instance and check the release notes for your version.