DueHarbor

Practical guide

Right-Size Software Seats Before the Renewal Date

Software seats are easy to add and hard to remove. Someone joins, a seat gets assigned. Someone leaves or changes teams, and the seat often stays. A trial group gets upgraded to a bigger plan and nobody moves them back. By the time the renewal comes around, the seat count on the order form reflects every addition from the past year and very few of the removals.

November 4, 2026 · 8 minute read

Why seat counts drift up

Software seats are easy to add and hard to remove. Someone joins, a seat gets assigned. Someone leaves or changes teams, and the seat often stays. A trial group gets upgraded to a bigger plan and nobody moves them back. By the time the renewal comes around, the seat count on the order form reflects every addition from the past year and very few of the removals.

The timing makes it worse. Many agreements let you add seats during the term but only reduce them at renewal. If the notice date passes before anyone looks at the count, the next term starts at the same quantity, and the extra seats are locked in for another year.

This guide covers how to review seats and plan tiers before a renewal, when to start, and how to make sure the new count actually lands in the next agreement. It is written for IT, ops, and finance teams. It is not legal or procurement advice, so check contract questions with your legal or procurement contacts.

Step 1: Find the notice date, then work backward

The date that matters is not the renewal date. It is the last day you can change the quantity or give notice, based on the agreement. Find it first. If it is hard to locate, see how to find the notice period in a software contract.

Then set your own dates, working backward:

  • Notice date: the last day to change seats or terms
  • Decide-by date: a few weeks before the notice date, so there is time to tell the vendor
  • Seat review start: far enough before the decide-by date to check usage and hear back from team leads

A seat review squeezed into the last week usually ends with the same count as last year.

Step 2: Give the review an owner

Seat reviews stall when everyone assumes someone else is doing them. Name one owner for each renewal, usually the person closest to the tool, and a backup. The owner does not have to approve the spend. They make sure the review happens and a seat count is decided before the deadline. For help choosing, see who should own software renewals.

Step 3: Compare what you pay for with what you have

Start with the paper side. Pull the current order form and note:

  • The contracted seat quantity
  • The plan or tier for each group of seats
  • Any minimum seat commitment
  • What the agreement says about reducing seats, and when

Then pull the assigned users from the tool's admin console. If you keep a license inventory, this is where it pays off. See software license inventory: what to record for every license for the fields worth tracking.

Step 4: Find the seats you do not need

Go through the assigned users and flag:

  • People who have left: check assigned seats against your current employee list
  • People who changed roles: they may no longer need the tool at all
  • Inactive users: no meaningful activity for a long stretch, checked over more than just the last week
  • Duplicate accounts: one person with two seats, often from a name or email change
  • Shared or service accounts: confirm each one is still needed and has an owner

Login data alone can mislead. Some people use a tool rarely but still need it, such as for quarter-end work. Before you remove anyone, ask the relevant team lead a direct question: do these specific people still need this tool? Reconcile their answer with the usage data before you finalize the list.

Offboarding is where many unused seats come from. If seats keep piling up after people leave, look at the renewal owner offboarding handoff checklist and add seat removal to your offboarding steps.

Step 5: Separate remove from downgrade

Not every extra cost is an unused seat. Sort each flagged seat into one of two actions:

  • Remove: the person no longer needs the tool
  • Downgrade: the person uses the tool, but only features covered by a lower plan

Mixing the two is how teams end up cutting access someone still needs. Keep them as separate lists so the decision is clear.

Step 6: Plan for the next term, not just today

The right count is not always the current active count. Ask team leads about planned hiring, contractors, seasonal work, or projects ending in the next term. Leave reasonable room for known growth, and remember that adding seats mid-term is usually possible, while removing them often is not.

Write down the proposed seat count, the plan for each group, and the reasoning. That gives the approver something concrete to sign off on.

Step 7: Get the new count into the agreement

A seat reduction is not real until it is on the paperwork. Before the notice date:

  • Tell the vendor the proposed seat count and plan in writing
  • Ask for a quote at the new quantity, including the unit price and effective date
  • Check whether reducing seats changes the unit price on the remaining seats
  • Make sure the signed order form for the next term reflects the new count

If the agreement only allows increases, ask whether a reduction at renewal is possible anyway, and consider asking for the right to reduce seats at the next renewal written into the new term. Check anything unclear with your legal or procurement contact. If the vendor is also raising the price, the same timing applies to that conversation; see how to prepare for a SaaS price increase at renewal. For a structured pass over each renewal, see the software renewal review checklist.

Step 8: Record the decision and set the next review

Once the new term is signed:

Seat counts drift again over a year, so a quick check in your regular review keeps the next renewal from starting from scratch. See how to run a quarterly renewal review meeting.

Common mistakes

  • Starting the seat review after the notice date has passed
  • Assuming seats can be reduced mid-term without checking the agreement
  • Cutting seats based on login data alone, without asking team leads
  • Treating unused and underused seats the same way
  • Agreeing to a lower count by email but signing an order form with the old one
  • Leaving seats assigned to people who left
  • Forgetting to set the next review once the renewal closes

FAQ

When should we review software seats before renewal?

Well before the notice date, not the renewal date. Leave enough time to check usage, hear back from team leads, get approval, and tell the vendor before the deadline.

Can we reduce software seats in the middle of a contract?

It depends on your agreement. Many allow adding seats during the term but only reducing them at renewal. Check your signed order form and agreement, and ask your legal or procurement contact if it is unclear.

How do we know which seats are unused?

Compare assigned users with your current employee list, check activity in the tool's admin console, and confirm with team leads. Do not rely on login data alone, since some people use a tool rarely but still need it.

Should we remove seats or move people to a cheaper plan?

Both, for different people. Remove seats for people who no longer need the tool. Move people to a lower plan when they use the tool but not the features of the plan they are on.

Who should run the seat review?

One named owner per renewal, usually the person closest to the tool, with a backup. Team leads confirm who still needs access, and whoever approves spend signs off on the final count.