---
title: "How to Run a Year End Access Review for Company Software: Leavers, Admin Rights and Evidence"
url: https://businesslang.com/guides/how-to-run-a-year-end-access-review/
published: 2026-11-18
updated: 2026-11-18
---

# How to Run a Year End Access Review for Company Software: Leavers, Admin Rights and Evidence

> Run a year end access review for company software: remove leavers, check admin rights, clean up dormant and shared accounts, and document results for audits.

- URL: https://businesslang.com/guides/how-to-run-a-year-end-access-review/
- Type: Buying Guides
- Category: Security and IT
- Author: Matthew Collins, Business Operations and Management Expert; Aram Petrosyan, Senior Procurement Manager
- Published: 2026-11-18
- Last updated: 2026-11-18
- Topics: access review, user access review, offboarding, admin rights, least privilege, identity management, security, small-business
- Cite as: Matthew Collins and Aram Petrosyan, "How to Run a Year End Access Review for Company Software: Leavers, Admin Rights and Evidence", Businesslang, November 18, 2026, https://businesslang.com/guides/how-to-run-a-year-end-access-review/

**Short answer:** To run a year end access review, export the user lists from every business application and compare them with your current employee and contractor list from HR. Remove or disable accounts for leavers and anyone who no longer needs access, disable accounts unused for 45 days or more, and check every admin account: each should belong to a named person who still needs it, ideally as a separate admin account with multi-factor authentication. Ask each manager or tool owner to confirm their team's access, fix shared and service accounts, then record what was reviewed, what changed, who approved it and when, and keep that evidence for audits and customer questionnaires.

Over a year, access to company software drifts. People change roles and keep their old permissions. Contractors finish projects but keep their logins. Someone gets admin rights "just for this one task" and never gives them back. Leavers are removed from email but not from the CRM, the file sharing tool or the accounting system. Each of these is a small risk, and together they are one of the most common ways company data ends up in the wrong hands.

A year end access review resets the baseline. This guide explains how to run one across your business applications: removing leavers, cleaning up dormant and shared accounts, checking admin rights, getting sign off from the people who know who needs what, and documenting the results.

## What an access review is and why year end is a good time

A **user access review** (also called an access recertification) is a periodic check that every account in a business application belongs to someone who still needs it, with the right level of access. Reviewers confirm or remove each account, and the outcome is recorded.

Security frameworks treat this as a basic control. The CIS Critical Security Controls v8.1 ask organizations to keep an inventory of all accounts and validate that active accounts are authorized on a recurring schedule, at a minimum quarterly (Safeguard 5.1), to "delete or disable any dormant accounts after a period of 45 days of inactivity, where supported" (Safeguard 5.3), and to "establish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user" (Safeguard 6.2). The NIST Cybersecurity Framework 2.0 includes identity and access management outcomes under its Protect function, and NIST's Small Business Quick-Start Guide encourages small businesses to manage who has access to their data and systems.

Year end works well for a full review because:

- staff changes from the whole year can be cleaned up at once;
- renewals often fall early in the year, so removing unused accounts can cut seat counts before you pay for them;
- auditors, insurers and enterprise customers often ask for evidence of an access review in the last 12 months.

| What a review catches | Why it matters |
|---|---|
| Leavers with active accounts | Former staff or contractors can still reach company data |
| Role changes with old permissions | People keep access they no longer need |
| Excess admin rights | Admin accounts are the highest value target for attackers |
| Dormant accounts | Unused accounts are easy to take over unnoticed |
| Shared logins | No one is accountable for actions taken with them |
| Unused paid seats | Money spent on licenses nobody uses |

## Step 1: Set the scope and the owners

List the applications in scope. Start from your software inventory; if you do not have one, our guide on [how to build a SaaS software inventory](https://businesslang.com/guides/how-to-build-a-saas-software-inventory/) shows how to build it. Prioritize:

| Priority | Examples | Review depth |
|---|---|---|
| Critical | Email and identity provider, finance and accounting, payroll and HR, banking portals, cloud hosting admin, customer databases and CRM, password manager | Every account, every permission level |
| Important | File sharing, project management, support desk, marketing tools with customer data | Every account; admin roles in detail |
| Low risk | Tools with no company data or integrations | Leavers and admins only |

For each application, name a **business owner** who approves access and a **technical admin** who exports user lists and makes changes. One person, often in operations or IT, coordinates the whole review.

Set a deadline, typically two to four weeks, and tell managers in advance what they will be asked to do.

## Step 2: Get the source of truth from HR

Ask HR for a current list of all employees and contractors, with:

- full name and work email;
- status (active, on leave, leaver) and leaving date;
- job title, department and manager;
- role changes during the year.

Include contractors, interns, agency staff and external partners with company accounts. They are the group most often missed in offboarding.

## Step 3: Export user lists from every application

From each application's admin console, export the list of users with as much of the following as the tool provides:

| Field | Why you need it |
|---|---|
| Name and email | Matching to the HR list |
| Role or permission level | Checking least privilege and admin rights |
| Account status | Active, suspended or invited |
| Last sign in or activity date | Finding dormant accounts |
| Created date | Spotting accounts added outside the normal process |
| License type | Linking accounts to cost |

Remember that single sign-on does not cover everything. Some tools have local accounts created before SSO was set up, or a backup admin login. Check both.

## Step 4: Remove leavers and fix role changes

Match each application's users against the HR list. Then:

1. **Leavers.** Disable or remove every account belonging to someone who has left. Before deleting, transfer files, records or ownership the business needs, and check whether the tool requires data export first.
2. **Unknown accounts.** Investigate any account that matches nobody on the HR list. It may be a contractor, a shared account, a test account or something worse.
3. **Role changes.** For people who changed jobs during the year, remove access tied to their old role.
4. **People on leave.** Suspend rather than delete if your policy allows, so access can be restored on return.

Record every change as you make it. If leavers turn up in many tools, your offboarding process needs fixing; our [employee onboarding checklist](https://businesslang.com/guides/employee-onboarding-checklist/) can be mirrored into an offboarding checklist that lists every tool.

## Step 5: Clean up dormant, shared and service accounts

- **Dormant accounts.** Using last sign in dates, disable accounts with no activity for 45 days or more, as the CIS Controls recommend, unless there is a documented reason such as seasonal staff. Ask the owner before disabling accounts that run important functions.
- **Shared accounts.** Replace shared logins with named individual accounts where the tool allows. Where a shared account must remain, record who owns it and who uses it, keep the credentials in a business password manager and change the password when anyone with access leaves.
- **Service accounts and integrations.** List accounts and API tokens used by integrations, automation tools and AI assistants connected to your apps. Each needs an owner and a reason; remove those no one can explain. Also review third party apps connected to your Google Workspace or Microsoft 365 accounts and revoke unused ones.

## Step 6: Check every admin right

Admin accounts can change settings, export data and create new users, so review them more strictly than anything else.

For each application, list every user with admin or owner rights and check:

| Check | Good practice |
|---|---|
| Is the admin a named person who is still employed? | No admin rights for leavers, shared accounts or unknown users |
| Do they still need admin rights for their job? | Remove admin rights that were granted for a past task |
| How many admins are there? | As few as possible, but at least two for continuity on critical systems |
| Is multi-factor authentication on? | Required for every admin account |
| Is admin work done from a separate account? | The CIS Controls v8.1 recommend dedicated admin accounts, separate from everyday accounts used for email and browsing (Safeguard 5.4) |
| Is there a break glass account? | One emergency admin login, stored securely, tested and documented |

Pay special attention to your identity provider, email system, finance and payroll tools, banking portals and cloud hosting: one compromised admin there can expose everything.

## Step 7: Ask managers and owners to certify access

Send each manager a list of their team's access across critical and important applications, and each tool owner the full user list for their tool. Ask them to mark every line **keep**, **change** or **remove**, with a short reason for anything unusual.

Keep the request simple:

| User | Application | Access level | Last sign in | Manager decision | Reason or comment |
|---|---|---|---|---|---|
| Example user A | Accounting | Admin | 2 days ago | Change to standard | Admin no longer needed after migration |
| Example user B | CRM | Standard | 120 days ago | Remove | Moved to operations in June |
| Example user C | File sharing | Standard | Yesterday | Keep | |

These rows are illustrative placeholders. Chase late responses: an unanswered certification should not count as approval. For critical systems, consider removing access that is not certified by the deadline, after warning the owner.

## Step 8: Make the changes and confirm them

The technical admin applies every approved change, then confirms it by exporting the user list again. Check that:

- removed users no longer appear as active;
- downgraded users have the new permission level;
- freed licenses are released or the seat count is reduced before renewal.

Reducing seats can save money at renewal; our guide on [how to plan your software budget](https://businesslang.com/guides/how-to-plan-a-software-budget/) explains how to capture that saving.

## Step 9: Document the results

Keep a simple record for each application. This is the evidence auditors, cyber insurers and customer security questionnaires usually ask for.

| Record | Example |
|---|---|
| Application and scope | CRM, all users and roles |
| Review dates | Started December 1, completed December 19 |
| Source lists used | HR list dated December 1; CRM user export dated December 2 |
| Reviewer and approver | Tool owner: sales lead; changes by operations manager |
| Findings | 3 leavers, 2 dormant accounts, 1 unnecessary admin |
| Actions taken | All removed or changed on December 12 |
| Exceptions | One shared support login kept; owner named; password rotated |
| Evidence | Before and after exports saved in the review folder |

Store records in one folder per year with restricted access, since user lists are personal data.

## Using tools to make reviews easier

Most small businesses can run an annual review with admin console exports and a spreadsheet. Tools help as you grow:

| Need | What helps |
|---|---|
| Fewer places to remove leavers | Single sign-on through your identity provider, with automated deprovisioning where supported |
| Automatic reminders and approvals | Identity governance or SaaS management platforms with built in access reviews |
| Finding tools outside SSO | SaaS discovery from spend data and browser extensions |
| Answering access questions without IT | AI copilots on top of governance data, such as the one described in our guide to [Corma's Cormie copilot](https://businesslang.com/guides/corma-cormie-ai-copilot-saas-access-governance/) |

Before buying, check whether your identity provider or existing tools already include access review features. Our guide on [vendor risk management](https://businesslang.com/guides/vendor-risk-management-b2b-purchasing/) covers the questions to ask any security vendor.

## Year end access review checklist

1. List applications in scope and rank them by risk.
2. Name a business owner and technical admin for each.
3. Get the current staff and contractor list from HR.
4. Export user lists, roles and last sign in dates.
5. Remove leavers and fix role changes.
6. Disable dormant accounts and clean up shared and service accounts.
7. Review every admin account; require MFA and separate admin accounts.
8. Get manager and owner sign off.
9. Apply and confirm changes; reduce seat counts.
10. Document results and fix the offboarding gaps you found.

## The bottom line

A year end access review compares every application's users with HR's list of current staff, removes leavers and dormant accounts, tightens admin rights, gets sign off from the people who know who needs access, and records the results. Do it once a year for all business software and quarterly for critical systems, and use what you find to fix offboarding so next year's review is shorter. Start with your identity provider, email, finance and payroll tools, where a single forgotten account carries the most risk.

## Frequently asked questions

**Q: What is a user access review?**

A: It is a periodic check that every person with access to a business application still needs it, at the right level. Reviewers confirm or remove access, and the results are recorded as evidence.

**Q: How often should access reviews be done?**

A: At least once a year for all business applications, and quarterly for critical systems such as finance, payroll, email, cloud administration and tools holding customer data. The CIS Controls v8.1 ask organizations to validate that active accounts are authorized on a recurring schedule, at a minimum quarterly.

**Q: Who should approve access in a review?**

A: The person who knows whether access is needed: usually the employee's manager for their team, and the tool's business owner for the application as a whole. IT or operations runs the process and makes the changes, but should not be the only approver.

**Q: What counts as a dormant account?**

A: An account with no sign in or activity for a set period. The CIS Controls v8.1 recommend deleting or disabling dormant accounts after 45 days of inactivity, where the system supports it.

**Q: Do I need special software to run an access review?**

A: Not at small business scale. Exporting user lists from each admin console into a spreadsheet and comparing them with HR's staff list works. Identity governance or SaaS management tools help when you have many applications, frequent joiners and leavers, or auditors who want automated evidence.

**Q: What should we do with shared accounts?**

A: Replace them with named individual accounts wherever the tool allows. Where a shared account is unavoidable, record who uses it and who owns it, store its credentials in a business password manager, and change the password whenever someone with access leaves.


## Sources

1. [CIS Critical Security Controls Navigator v8.1, Controls 5 and 6 (checked November 18, 2026)](https://www.cisecurity.org/controls/cis-controls-navigator)
2. [Indiana University OmniSOC: CIS Controls Version 8.1 guide (checked November 18, 2026)](https://omnisoc.iu.edu/resources/crosswalks/cis_controls__v8.1_guide__2024_0801.pdf)
3. [NIST: The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29 (checked November 18, 2026)](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf)
4. [NIST SP 1300: NIST Cybersecurity Framework 2.0, Small Business Quick-Start Guide (checked November 18, 2026)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.1300.pdf)
