Software License Audit Checklist: Find Unused Seats Before Renewal

A software license audit should happen before every major renewal.
For annual contracts, start 30 to 45 days before the renewal deadline.
For expensive monthly tools, run a lighter version every quarter.

The goal is not to punish teams for using software.
The goal is to make sure each paid license still supports real work.

Step 1: Build a Current Tool Inventory

Start by listing every paid software tool your company uses.

Do not rely only on memory.
Pull data from accounting records, corporate cards, vendor invoices, expense reports,
and shared subscription accounts.

For each tool, record:

• Tool name
• Monthly or annual cost
• Contract owner
• Department owner
• Renewal date
• Current plan
• Number of paid seats
• Number of active users
• Business purpose
• Cancellation or downgrade deadline

This inventory becomes the baseline for every future software review.

If a tool has no clear owner, that is already a warning sign.
Software without ownership usually becomes harder to cancel, harder to downgrade, and easier to forget.

Step 2: Compare Paid Seats Against Active Users

Next, open each vendor admin console and compare paid seats against actual active users.

Do not ask, “Does anyone still need this?”
Ask, “Who has used this tool recently?”

Pull the last login date, recent activity, workspace activity, project activity, or usage report where available.

Flag users who:

• Have not logged in during the last 30 days
• Belong to completed projects
• Are former employees
• Are former contractors
• Only need viewer access
• No longer belong to the department using the tool
• Were provisioned during a temporary sprint

The exact activity window depends on the tool.
For some tools, 30 days is enough.
For quarterly planning tools or finance tools, you may need a longer review period.
The point is to use actual activity instead of assumptions.

Step 3: Verify Offboarding Leaks

Offboarding leaks are one of the easiest forms of software waste to miss.

When an employee or contractor leaves, teams often remove access from core systems such as email,
identity providers, payroll, or internal documents.
But many paid SaaS tools sit outside that central process.

A departed contractor may still have access to a project tool.
A former freelancer may still occupy a paid design seat.
A previous agency account may still exist inside a marketing platform.
A shared workspace may still include external users from an old project.

This creates both cost risk and access risk.

Before renewal, compare your active HR or contractor list against each paid user directory.
Any user who no longer belongs to the company, project, or vendor relationship should be reviewed immediately.

For a deeper process, use the Software Offboarding Checklist to review access cleanup, unused seats,
contractor accounts, and renewal exposure.

Step 4: Separate Editors From Viewers

Many teams overpay because they assign full paid access to people who only need occasional visibility.

Executives, clients, advisors, stakeholders, and cross-functional reviewers often do not need full editor permissions.
They may only need view-only access, comment access, or periodic exports.

Review each paid role carefully.

Ask:

• Who actually creates work inside this tool?
• Who only reviews work?
• Who only needs reports?
• Who only needs access during a specific project?
• Which users can be moved from editor to viewer?
• Which seats can be downgraded without blocking work?

This is one of the fastest ways to reduce software waste without disrupting operations.

The goal is not to remove useful access.
The goal is to stop paying editor-level prices for viewer-level behavior.

Step 5: Check Security and Identity Paywalls

Some software waste does not come from unused seats.
It comes from plan upgrades required to access basic security, identity, or administration features.

A team may move into a higher-priced plan because it needs SSO, SAML, OIDC, admin controls,
advanced permissions, audit logs, or access governance.
In some cases, that upgrade also brings minimum seat requirements or enterprise-style pricing.

The SSO Tax directory tracks examples of vendors placing SSO, SAML, OIDC,
or related access controls behind higher-priced plans.
This does not mean every vendor is doing something wrong,
but it does mean teams should separate security-driven upgrade costs from normal usage-driven software spend.

Before renewal, ask:

• Are we paying for a higher plan mainly because of SSO or access control?
• Are all seats on that higher plan actually needed?
• Is there a smaller plan that supports our real usage?
• Can we negotiate security features without unnecessary seat expansion?
• Are we paying enterprise prices for a small-team workflow?

This distinction matters because usage waste and security pricing friction require different negotiation strategies.

Step 6: Identify Duplicate Tools

Duplicate tools are another source of quiet waste.

A team may have two project management tools, three AI writing tools, multiple note-taking apps,
overlapping design platforms, separate meeting recorders, and several dashboards solving similar problems.

Duplication often happens because teams move quickly.

Marketing buys one tool.
Product uses another.
Engineering adds something else.
Operations adopts a separate workflow.
A founder tests an AI tool and keeps the subscription active.

Over time, the stack becomes expensive and fragmented.

During the audit, group tools by job-to-be-done:

• Project management
• Design collaboration
• AI writing
• AI meeting notes
• Customer support
• CRM
• Analytics
• Documentation
• Automation
• Security
• Finance

Then ask:

• Which tools solve the same problem?
• Which one is the system of record?
• Which tool has the strongest adoption?
• Which tool has the clearest owner?
• Which tool can be consolidated, downgraded, or removed?

A license audit should not only reduce seats.
It should also reveal whether your stack has too many tools doing the same job.

Step 7: Audit AI Subscription Spread

AI tools have changed how software waste appears inside small teams.

Traditional SaaS waste often came from old tools staying active too long.
AI subscription waste can happen faster because individual users can buy tools quickly,
expense them separately, and create overlapping workflows before the company has a clear AI stack policy.

A founder may pay for one AI assistant.
A marketer may use another.
A developer may use a coding assistant.
A sales person may add an AI meeting tool.
An operator may test another automation product.

Each subscription may look small.
But when AI tools spread across roles without ownership,
the company can end up paying for overlapping capabilities with no clear system of record.

Before renewal, audit:

• Individual AI subscriptions
• Team AI subscriptions
• Browser-based AI tools
• Meeting assistants
• Writing tools
• Coding tools
• Automation tools
• Design or image tools
• AI add-ons inside existing SaaS platforms

Then decide whether each tool should be kept, consolidated, replaced, or removed.

If AI overlap appears across the team,
use the AI Subscription Waste Calculator to estimate whether separate AI subscriptions are creating avoidable software waste.

Step 8: Calculate Your SaaS Waste Exposure

Once you have reviewed seats, users, offboarding leaks, duplicate tools, AI subscriptions,
and renewal pressure, calculate your overall waste exposure.

A simple review can answer:

• How many paid seats are inactive?
• Which tools have the largest gap between paid users and active users?
• Which contracts are renewing soon?
• Which tools overlap?
• Which AI subscriptions are unclear?
• Which upgrades are driven by security or plan restrictions?
• Which tools have no owner?

To make this easier, run the same data through the SaaS Waste Score Report.
It gives your team a directional score based on unused seats, duplicate tools, AI subscription overlap,
renewal risk, and software spend signals.

This does not replace a full audit. It helps you decide where to investigate first.