research
Measuring access removal completeness after an employee departs
A method for checking whether every account, group, mailbox, and shared credential held by a leaver was removed within the policy window.
Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.
Research playbook
On this pageJump to section
Key stats
Key takeaways
Access removal is usually measured by the date the main account was disabled. The harder question is whether every application, group, mailbox, and shared credential was closed. A leaver can lose the directory account and still keep a vendor portal, a shared drive link, or a forwarding rule. This study measures the completeness of access removal after a departure and the time each system took to close.
Question and scope
The study asks what share of a leaver's known access was removed within the policy window after the last working day. The unit is one leaver. The population is every employee who left the company during the study window. Record the systems in scope and the policy window. Record the result in the study file with the date and the reviewer.
Include the identity account, the application assignments, the groups, the shared mailboxes, and the physical access records. Exclude contractor departures unless the same process applies, but record how many occurred. Note the leavers whose manager was also unavailable. A study that counts only the directory will overstate completeness. Keep the evidence beside the case reference so another reviewer can check it.
Define access removal
Define removal as the loss of the ability to authenticate or use the access, not only a status change in a list. A disabled account with an active session is not removed. A group membership that remains after the account is disabled is not removed. Write the definition before collecting so each system is scored the same way. Apply the same rule to every item in the sample before summarising the result.
Separate the removal of personal access from the transfer of shared access; a shared mailbox may need a new owner before the leaver's permission is removed. A shared credential may need rotation rather than deletion. Record which action was required for each item. Note any exception and the name of the person who approved it. Record the result in the study file with the date and the reviewer.
Build the leaver frame
Export the leavers from the HR system for the study window. Match each person to the offboarding ticket and the last working day. Include the department, the manager, and the systems the role used. Record the export date and the filter used. A list built from the ticket system alone may miss a departure that was never logged, so check the identity provider as well.
Add the leavers who appear in the identity provider but not in the HR export, such as contractors or temporary staff. Ask the manager whether the person is still working. List the leavers with no offboarding ticket and the reason. The frame should show the gaps before the measurement starts. Store the raw export with the query that produced it.
Collect the access record
For each leaver, export the account status, the group memberships, the application assignments, and the mailbox permissions; capture the time of each change and the person who made it. Store the raw exports before summarising. A screenshot of one system is not a completeness measure. Compare the result with the previous period before drawing a conclusion. Keep the evidence beside the case reference so another reviewer can check it.
Check the systems that do not integrate with the identity provider; include the vendor portals, the local accounts, and the shared credentials in the vault. Note the systems that cannot produce a timestamp. An untimed change can still be counted, but the report should say so. Write the decision into the method note for the next reviewer. Apply the same rule to every item in the sample before summarising the result.
Check each system
Verify the removal directly in each system rather than trusting the checklist; try to sign in with the old account or check the last access log. Confirm that the account cannot reset a password through a personal address. Record the result as removed, pending, or not applicable. Check the record against the source system before closing the item. Note any exception and the name of the person who approved it.
Check the group memberships that grant access to files and sites; a disabled account in an active group can still expose data through a shared link. Review the mailbox rules, the forwarding addresses, and the delegated permissions. Record each item and the evidence. Keep the sample sheet with the report so the count can be reproduced. Store the raw export with the query that produced it.
Sample and verify
Select at least ten percent of the leavers and repeat the check with a second reviewer. Compare the independent results and discuss every disagreement. Record the agreement rate and the changes made to the definition. A measure that only one person can reproduce is not ready for a report. Name the owner of the next action in the review note.
Choose the sample across departments, roles, and systems; include at least one leaver with a complex role and one with a simple role. Ask the manager whether any access was missed. A manager who still sees the leaver in a tool is a finding the export may not show. Record the date of the check beside the evidence file. Compare the result with the previous period before drawing a conclusion.
Measure completeness
Report the share of leavers with all known access removed within the policy window; split the result by system and by department. Report the items that were removed late as a separate line. Do not collapse the systems into one number without showing where the gaps sit. Use the same definition for every item in the population. Write the decision into the method note for the next reviewer.
Add the median and the longest removal time for each system; note the leavers who had at least one item still active after thirty days. These cases carry the most risk and should be listed with the owner. The report should show both the rate and the tail. Note the systems that could not be measured in the report. Check the record against the source system before closing the item.
Report and remediate
Write a short report with the method, the population, the completeness share, and the exceptions; use leaver identifiers rather than names in the summary. Attach the raw exports and the verification sheet. Send the draft to the identity owner and give them time to correct the facts. Ask the technical owner to confirm the finding before publication. Keep the sample sheet with the report so the count can be reproduced.
Assign an owner and a due date to each system with a gap. Start with the items that are still active, then the systems that cannot produce evidence. Record the fix and the test that confirms it. A finding is closed only when the next sample shows the item removed. Keep the previous result beside the new one for comparison.
Interview managers and leavers
Ask five managers whether they knew what access their leaver had; record the answer without judging the person, because the answer shows whether the checklist reached the manager. Ask whether the handover included a shared credential. Compare the answers with the access record. File the export with the method note at the end of the study. Name the owner of the next action in the review note.
Ask the person who runs the offboarding ticket which step is hardest to finish. A system with no owner or no API is a common cause of late removal. Record the name of the system owner and the workaround. The interview should produce one process change, not only a list of complaints. Record the result in the study file with the date and the reviewer.
Repeat after system changes
Rerun the study after a new application, an identity migration, or a change to the offboarding process. A new system can add an access path that the checklist does not cover. A migration can change where the removal evidence is stored. Compare the new result with the previous one and investigate any drop. Keep the evidence beside the case reference so another reviewer can check it.
Keep the export, the sample sheet, and the report with the identity documentation. Set a quarterly review and a monthly check of the most recent leavers. Record the date and the reviewer. A stable completeness share with a short exception list is a better result than a one-time clean audit. Apply the same rule to every item in the sample before summarising the result.
Limits of the study
The study sees the access that the company knows about. It cannot see a personal account that was used for work or a credential that was shared outside the approved systems. It also cannot prove that a removed account was not used before the removal. State these limits so the report is read as a completeness review. Note any exception and the name of the person who approved it.
A manager may report access late, after the study window; repeat the study after a large departure or a system change. The method measures removal, not the risk created before it. Use the interviews and the access logs to interpret the result. Store the raw export with the query that produced it. Record the date of the check beside the evidence file.
Keep evidence usable
Store the exports, the sample sheet, and the report in one folder with the study date. Name the files by date and scope rather than by the person who ran the study. Give read access to the identity owner and the next reviewer. A folder that only one person can open will not survive a staff change. Compare the result with the previous period before drawing a conclusion.
Write a one-page method note that explains how to repeat the export and where to find the policy window. Add the limitations and the systems that were out of scope. Include the last run date and the next planned date. The note should let a new reviewer reproduce the result without asking the original author. Write the decision into the method note for the next reviewer.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the laptop support, password manager, vendor response, ticket triage, and access removal measures discussed here. The NIST SP 800-63B digital identity guidance supports the credential checks, NIST SP 800-53 Rev. 5 supports the access and audit records, and the GAO data reliability guidance supports the sampling approach. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the laptop support end date measure and the access removal completeness study before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.
Benchmark brief
What this research page must produce
A practical estimate for volume, review time, escalation rate, and assistant capacity.
A clear split between routine support, preparation work, and technical ownership.
What the measuring access removal completeness after an employee departs data shows
Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.
The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.
Workflow
Recommended operating workflow
Collect a baseline
Pull the last 30 to 90 days of examples related to measuring access removal completeness after an employee departs, including completed work and unresolved exceptions.
Classify the work
Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.
Set the operating number
Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.
Refresh the benchmark
Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.
Decision rules
| Metric | Use it to decide | Manager action |
|---|---|---|
| Weekly volume | Whether the workflow is worth assigning as recurring assistant work. | Approve a weekly capacity target and backlog threshold. |
| Access sensitivity | Whether the assistant can work directly or only prepare review notes. | Set least-privilege permissions and removal dates. |
| Escalation rate | Whether the workflow is stable enough to delegate. | Rewrite the SOP when exceptions exceed the agreed threshold. |
Consolidated statistics
| Statistic | Figure | Source |
|---|---|---|
| Unit | One leaver | Study protocol |
| Verification sample | 10 percent | Study protocol |
| Review cadence | Quarterly | Study protocol |
Sources
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsAccess enforcement and account management controls used in the audit.
- NIST SP 800-63B, Digital Identity GuidelinesCredential and authenticator lifecycle language for removal checks.
- CISA Cross-Sector Cybersecurity Performance GoalsOffboarding and account revocation baseline for small organisations.
- FTC Data Breach Response: A Guide for BusinessAccess control and evidence guidance for departed staff.
Measurement checklist
| Field | What to capture | Owner |
|---|---|---|
| Volume | Weekly request count, backlog age, and repeat issue patterns | Assistant prepares, manager reviews |
| Risk | Access level, customer impact, security sensitivity, and approval needs | Technical owner |
| Cadence | Daily, weekly, monthly, or quarterly review rhythm | Manager |
| Evidence | Sample tickets, logs, screenshots, and before-after examples | Assistant collects, owner validates |
| Escalation | Triggers, approval path, response time, and stop-work rules | Technical owner |
How to read the result
A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.
Source and refresh note
This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.
How should teams use this benchmark?
Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.
Get free benchmark review