Seats and renewals
What counts as an unused seat? 30, 60 or 90 days
How to choose an inactivity window for software seats, why 60 days is a sensible default, which tools need a longer window, and how to turn the number into a decision before renewal.
- Published
- 22 Sept 2026
- Read time
- 7 min
- Topic
- Seats and renewals
"Unused" sounds obvious until you try to act on it. Is a seat unused if nobody signed in this week? This month? This quarter? Pick a window too short and you take seats away from people on leave. Pick one too long and you pay for a year of seats that were dead in spring.
What "used" means
For seat decisions, the practical measure is the last sign-in date per person per tool. It is available from single sign-on through Google Workspace, Microsoft 365 or Okta, and from the admin panel or admin API of many tools. It does not tell you how much someone did inside the tool, and it does not need to. A person who has not signed in for two months is not getting value from their seat, whatever the reason.
Sign-in data is personal data about employees. Collect only what the decision needs: the last sign-in date and the seat assignment. Under the DPDP Act, 2023, the employer is the data fiduciary for this data, and employment purposes are a listed legitimate use under Section 7. This is general information, not legal advice.
Choosing the window
| Window | Good for | Risk |
|---|---|---|
| 30 days | Daily-use tools: chat, email, project trackers, code hosting | Flags people on long leave or on a short project break |
| 60 days | A sensible default for most per-seat tools | Few false flags; most people return to tools they need within two months |
| 90 days | Quarterly-use tools: reporting, tax, board, survey and some design tools | Seats stay paid for three months before anyone asks |
Use 60 days as the default and change it per tool. Then, for each flagged seat, make one of three calls: remove it, reassign it to someone waiting, or keep it with a note saying why.
Seats that look unused but are not
- Admin and owner accounts. Billing owners may rarely sign in but must stay.
- Shared service accounts used by integrations or automations.
- People on parental or medical leave. Mark them with a return date instead of removing them.
- Tools without SSO where people sign in with a password. Their sign-in may not be visible in your identity provider. Ask the tool's admin panel instead.
Worked example: one design tool
Neelgiri Labs, a fictional company, pays for 40 seats on a design tool billed annually. Prices are invented for the example.
| Measure | Value |
|---|---|
| Seats paid | 40 |
| Signed in within 30 days | 19 |
| Signed in within 60 days | 23 |
| Signed in within 90 days | 26 |
| Price per seat | ₹1,250 a month, billed yearly |
| Unused at 60 days | 17 seats, ₹2,55,000 a year |
Of the 17 seats, four belong to people who left the company, three to people on leave, and ten to people who tried the tool once. The decision at renewal: cut to 28 seats (23 active, three on leave, two spare for hiring), saving 12 seats, or ₹1,80,000 a year at these prices. The unused seat cost calculator runs this sum for any tool.
When you can act on it
Finding an unused seat and stopping the charge are two different things. Vendors handle seat reductions differently.
- Monthly plans: seats can usually be removed at any time, and the next bill drops.
- Annual plans: seats added mid-term are often charged pro rata, but seats removed mid-term are usually only credited at renewal. Plan reductions for the renewal date.
- True-up plans: some vendors count seats in use during the term and bill the difference later. Removing unused seats before the count date matters more than the renewal date.
Check each vendor's own billing help page for the current rules; our tool guides summarise how seat changes work for common tools.
Turning the number into a decision
A list of unused seats on its own changes nothing. It needs to reach the person who can act, before the renewal. Ayush Agro Foods' Seat Usage view lists seats unused for 30, 60 and 90 days by name, using sign-in data from Google Workspace, Microsoft 365 or Okta. The renewal alert then puts the count in front of the tool's owner 30 days early, with a choice to renew as is or reduce seats.
Next post
Annual vs monthly SaaS plans: when the discount costs more
Annual billing looks cheaper per seat, but it fixes your seat count, your exchange rate and your cash for a year. A break-even method you can run in five minutes.
Read nextMore in Seats and renewals
All postsGet every renewal to its owner 30 days early.
Seat usage from sign-ins, renewal dates and notice periods in one calendar, and a decision logged before the charge.
- Read-only access
- Data hosted in India
- Priced in rupees
- 14-day trial on your data