Software asset management tools, a spreadsheet register and a managed service are three routes for keeping license records. The right one depends on your people and your records. Five decision rules and six supplier questions follow. Use them to pick a route, then test it on your own data.
Last reviewed 2026-11-14 by Manish Sharma.
A license is your firm’s permission to run a piece of software, under terms the vendor sets. An entitlement is the number of seats or installs you can show you bought. The job is to keep both records current and act on the gap between them.
This guide suits a buyer in India or the GCC who runs IT, procurement or finance for a growing company. Their license records sit in a spreadsheet or in one person’s head. The guide names no product and quotes no price. Device records are a separate choice, and they have their own guide.
Software Asset Management Tools Compared With a Spreadsheet and Managed SAM
You are choosing among three routes. The three lines below are Signisys’ working wording for each route, not a standard. Each line states what its route is and nothing more.
- Spreadsheet register: a shared file that people update by hand.
- Tool: an application made for license records.
- Managed service: another firm does the upkeep, while a named owner stays at your firm.

The choice rests on two things you already know better than any supplier does. One is who changes the records. The other is what your firm has to show from them. A firm with one editor and one contract holder has a different problem than a group with five entities.
The next two sections turn that into questions. The decision rules look at your own records. The supplier questions then test whatever route you lean towards. A managed service also gets the same six questions as a tool.
Key Takeaway Choose a route by looking at your people and your records first. Then ask suppliers your questions.
Decision Rules for Software Asset Management Tools vs a Spreadsheet
Here are five rules, each a question about your own records. A yes on a rule means you should look harder at a tool or a managed service, while a no points to a sheet. The rules point to a route. They do not score it, because a scored review of your records needs a different method.
When you answer each rule, use the files and the people in front of you.
Write down the name of whoever gave each answer, as that name is the first useful record you will have.
Rules 1 to 3: Editors, Sources and Renewal Dates
The first three rules cover who touches the records and how many lists you join. They also cover who hears about a renewal.
| No. | Question about your own records | Route to look at on a yes |
|---|---|---|
| 1 | Do several people, teams or entities change the records? | Look at a tool or a managed service. Then ask who reads the change history. |
| 2 | Must you join more than one source, such as purchase papers, install lists, seat lists and contracts? | Look at a tool or a managed service if one person has no way to match the lists in one sitting. |
| 3 | Does each renewal and notice date have an owner who gets told in time? Can you name who tells them today? | A yes with no name is a gap. Look at a tool or a managed service for the reminder work. |
When you weigh the options, start with rule 1. It bites where a branch buying team and a head office team both type into the file. If two copies of the sheet exist, with dates in the file names, count that as a yes.
Rule 2 is about effort. Ask the person who matches the lists how long one vendor took last time, then multiply by your vendor count.
Rule 3 carries a cost when a date is missed. Before anything else, check how each contract renews. A notice date that passes with nobody told may lock in another term. Start there if you can fix only one thing.
Rules 4 and 5: Entities, Countries and Upkeep After Go-Live
The last two rules cover how the firm is built and who does the work once the choice is made.
| No. | Question about your own records | Route to look at on a yes |
|---|---|---|
| 4 | Do contracts sit with several group entities or countries, so one view has to split by entity? | Look at a tool or a managed service if your own sheet does not show each entity apart today. |
| 5 | Does a named person at your firm have the hours to keep records current after go-live? | Look at a tool on a yes. On a no, ask whether the work goes to an outside team. |
Rule 4 fits groups with an Indian company and one or more Gulf entities. There, the same vendor holds a separate contract for each. The view that matters to finance is by legal entity and country. Our guide on how a license record goes wrong covers why group companies create gaps.
Rule 5 sits with a person. Records can go stale when nobody has the hours to update them, whichever route holds them. If no named person has the hours, the outside-team route deserves a look. The later sections show how to scope it. Answer rule 5 before you sit through any demo.
Six Questions to Put to Software Asset Management Tools Suppliers
Every supplier gets the same six questions. You answer each one on your own export during a trial. A demo built on the supplier’s sample data may tell you little about the rows your branches typed by hand. Ask for evidence you can open yourself.

A managed service provider gets the same six. Ask them what their own tools read, and what you can take away if you stop.
Discovery, Usage Data and Matching Installs to Purchases
The first three questions test how software and seats get into the record.
| No. | Question for the supplier | Evidence the supplier should hand over |
|---|---|---|
| 1 | Which sources can you read for installs and for cloud or software-as-a-service apps, and which must we switch on? | The written source list. Then one program you install on a spare machine, located in the record with its source named. |
| 2 | What usage data do you read, and from which sources? | One seat from your own list, shown with its last-used date. |
| 3 | How do you match installs to purchases, and on which field? | One product that sits in both of your lists, shown as a single row. |
For question 1, list your own cloud and software-as-a-service apps before the trial starts. Then you can see which ones the source list leaves out. The CIS Critical Security Controls give software inventory its own place. Control 2, inventory and control of software assets, appears in CIS Control 2 on software assets.
For question 2, ask where the supplier reads usage from: the shared sign-in service, the application itself or both. Then check the last-used date for one seat against what its owner tells you.
For question 3, write down the match field the supplier names. It might be a product name, a publisher or a part number. When that field differs, one product can show up as two rows.
Contract Records, Entity Views and Support in India and the GCC
The last three questions test contract records, entity splits and exit.
| No. | Question for the supplier | Evidence the supplier should hand over |
|---|---|---|
| 4 | What do you record per contract, and who gets told about a notice date? | Enter one real contract during the trial, then name the person who is reminded. |
| 5 | Can you split one vendor’s contracts by legal entity and country? | The hosting statement in writing, plus the support contact list for India and the GCC. |
| 6 | What can we take out on the day we stop? | The written exit steps, plus one agreed sample extract handed over the same day. |
Question 4 links straight back to rule 3. If the supplier fails to show a reminder reaching a named person, the date is still your problem.
Question 5 tests the paperwork. Read the hosting statement against your own firm’s rules on where records may sit. Check the support hours against the working week at each office. The week can differ between India and the GCC.
Question 6 is the exit question. Ask it before you sign, while the choice is still yours. Also keep the sample extract on file.
Four Trial Tests Before You Sign for License Records
Run four tests on your own data before you sign, whichever supplier you use. The tests below are Signisys’ working view, written as tests of your data and not as claims about any product.
For license management software, ask for a trial on a copy of your register, not a clean demo set. Then run the four tests in order.
Does the list match what you know is installed on a sample of your machines?
Does it hold your purchases as a baseline, showing the quantity you bought for each product?
Does it set the two side by side for one vendor and show a gap or a surplus?
Does it assign an action to a named owner, with a date?
Key Takeaway Test 4 matters as much as the other three. A gap that nobody owns stays a gap, however clear the screen looks.
If a supplier fails one of the four on your copy, note which one. Ask when it will be ready. Then take a dated answer in writing.
Spreadsheet, Tool or Managed Service: Which Question Settles It
One question settles each route, and the table below puts it first. Use it after the rules and the supplier questions, when you are ready to name a route and an owner. The table asks for yes or no answers.
| Route | Choose it when you can answer yes to | First question to settle |
|---|---|---|
| Spreadsheet register | Do all three conditions in the next section hold today? | Who is the named keeper, and who stands in when that person is away? |
| Tool | Does a named person at your firm have the hours to keep records current after go-live? | Which of the six supplier questions will you test first on your own export? |
| Managed service | Would handing the upkeep to an outside team save your people more hours than the hand-over takes? | Which tasks and records does the provider keep, and which stay with you? |
Advantages
Limitations
Three Conditions Under Which a Sheet Stays in Use
A sheet may hold when all three of these are true. They are Signisys’ view, not a standard.

- Each renewal and notice date already has a named owner who answers when asked.
- Contracts sit with one legal entity in one country.
- One person can match purchases to installs in one sitting.
If all three are yes, a sheet may hold for now. If any one is a no, go back to the rules above and see which one it touches. Device records have their own test, and the same choice for device records sets it out.
Managed SAM: Name the Owner and Decide What to Hand Over
Whichever route you choose, name an owner at your firm and decide who signs off each renewal. Decide whether the provider keeps the records and sends the reminders. The decision to renew stays with a person on your side.
If you weigh a managed service against a tool, decide which tasks and records the provider keeps. Then decide which stay with you. Ask for scope and reporting in writing before work starts.
Signisys can help run this as a managed service. That makes us a supplier, so weigh this guide with that in mind. To get an outside read of your records before choosing, ask for a review of your license records. The related work is described under license, vendor and renewal record work and consulting and managed services from Signisys.
Test Software Asset Management Tools on Your Own Export
Load a copy of your own register, then find one gap in it. Ask the supplier to show that gap on screen. If the gap shows, the trial is reading your data. If it does not, ask why before anything else.
Set the trial length with the supplier, then write it down. Keep the same copy for each supplier, so the results compare. Three other Signisys guides cover the surrounding work. Risks are covered in how a license record goes wrong. For set-up, read keeping contract dates in one place. The checks sit in a pass or fail check of your license records. Run the trial this way, and you decide on your own evidence.
No charge, with a fixed scope.
Software Asset Management Tools FAQ
Which decision rule should come first when you compare software asset management tools?
How do software asset management tools compare with spreadsheets on renewal records?
If a provider keeps the records, who at our firm still decides on renewals?
Who from our firm should sit in a supplier demo?
Security Insights, Delivered.
Practical, vendor-neutral analysis of threats, tools, and architecture decisions.
