Empty Chairs, Live Invoices: The Monthly Seat Sweep Your UK Team Can Actually Keep Up With

Most software bills do not arrive with a dramatic reveal. They turn up as a line on a finance spreadsheet, a direct debit you half recognise, or a renewal notice that lands while everyone is busy. By the time it reaches a small UK team, the damage is rarely one big mistake. It is a collection of small ones: a leaver whose account was never closed, a contractor who drifted away, a shared login nobody owns, and a trial that someone upgraded in a hurry and then forgot.

The result is the seat you forgot. It is not usually malicious, and it is rarely anyone's fault in particular. It is just what happens when software administration sits between payroll, IT and whoever holds the company card. The good news is that you do not need a enterprise-grade licence management platform to fix it. You need a short, repeatable habit.

Why dormant seats hide in plain sight

SaaS accounts are easy to create and awkward to retire. A new starter needs access on day one, so someone invites them. A leaver leaves, payroll updates, and the software account stays active because nobody owns the joining-up of those two lists. A contractor finishes a project and their login remains, quietly counting as a paid seat. A shared inbox login gets passed around like a office key, never tied to a named person.

Trials add another layer. A team signs up for a fourteen-day trial, upgrades with a card because the trial was about to expire, and then the project changes direction. The subscription keeps running. The account looks active because the service is active, but nobody is really using the seat.

These accounts are not always obvious in an admin console. Some platforms show last login, some show last activity, and some show almost nothing useful. That is why the sweep should be simple enough to repeat, rather than perfect enough to postpone.

A twenty-minute monthly sweep

Pick a fixed point in the month, ideally just after payroll cut-off. Pull the current staff list from whoever runs HR or payroll, including contractors and regular freelancers. Then export the user list from your main software admin consoles: Microsoft 365 or Google Workspace, your finance tool, design software, project management, password manager, and anything else with per-seat pricing.

Put both lists side by side in a spreadsheet. Mark anyone in the software list who is not on the staff list. Then look at last activity where the platform provides it. Do not expect every tool to give you a neat answer. A rough signal is enough to start a conversation.

Flag, do not delete. The point of the monthly sweep is to produce a short list of accounts to check, not to conduct a dramatic purge. Assign each flagged account an owner: usually the person who manages that tool, or the manager of the team that used it. Ask a simple question: is this seat still needed?

Keep a second tab for trials and free accounts that might turn into paid ones. A calendar reminder is unglamorous, but it works. If someone upgrades a trial, note who owns it and when it renews. That one habit prevents a surprising number of zombie subscriptions.

What to check before you hit delete

Deleting an account feels satisfying, but it can also remove access to data, email, files or integrations that someone still needs. Before you delete, check four things.

First, data ownership. Does the account hold documents, projects or records that need to be transferred? Second, identity. Is the account tied to a shared mailbox, an alias, or a distribution list that other people still use? Third, integrations. Does the account own an API connection, a scheduled report, or an automation that will break if the user disappears? Fourth, licence type. Sometimes you can downgrade or suspend a licence without deleting the account, which is often the safer first step.

A sensible order is: disable sign-in, transfer ownership of files and mail, reassign any integrations, then delete after a short cooling-off period. For shared logins, the better fix is usually to replace them with named accounts or a password manager that records who has access. If you must keep a shared mailbox, give it a named owner and document who can get into it.

Evidence without the ceremony

Access reviews have a reputation for turning into paperwork festivals. They do not have to. For most small UK teams, a lightweight record is enough: one row per account, showing the date checked, the system, the account identifier, the status, the action taken, and the owner.

A screenshot of the admin console showing last activity, saved alongside that row, is plenty. An exported CSV is even better. Store it in a shared folder rather than someone's inbox, and keep it for a sensible period. The aim is to show that you checked, not to build a forensic archive.

This is also where the SealSoft idea of a seal is useful. A seal is not decoration. It is a mark that something has been checked and can be trusted. Your monthly seat sweep is the same idea in miniature: a small, dated record that says someone looked, someone decided, and the decision has an owner.

Make it boring, then make it stick

Count the seats you reclaim and multiply by the monthly or annual cost. That number is the argument for keeping the habit. Report it in a short monthly note to whoever pays the software bills. No slide deck required. A sentence and a total will do.

The teams that get this right are not the ones with the most sophisticated tooling. They are the ones who make the sweep dull enough to survive a busy month. Twenty minutes, a spreadsheet, a few admin consoles, and a shared folder for the evidence. That is enough to stop empty chairs from quietly renewing at your expense.