research
Measuring the share of SaaS accounts still active after a project ends
A method for matching SaaS accounts to projects, checking which remain active after closure, and measuring the delay before access is removed.
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
Projects create accounts, workspaces, and guest invitations that outlive the work they supported. A campaign ends, a client leaves, or a pilot finishes, and the SaaS tenant keeps its users because nobody owns the close step. The unused accounts may cost money, but the larger risk is access that nobody is watching. This study measures how many project accounts remain active after the project end date and how long they stay that way. The result is a process measure, not an estimate of licence waste across the whole estate.
Question and scope
The study asks what share of SaaS accounts created for a project remain active after the recorded project end, and how many days pass before access is removed. The unit is one account or workspace membership tied to a project. The population is every project closed during the study window that used a supported SaaS product. The result describes those projects and does not generalise to accounts created for ongoing operations. Record the products that were excluded and the reason so the scope can be checked.
Include guest accounts, shared workspaces, and service accounts created for the project. Exclude personal accounts that the company cannot administer, but record how many exist. Note the products in scope and whether each has an owner in the register. A study that counts only the main user account will understate the access that survives. Keep the guest and service account counts separate in the report.
Define project end
Use one recorded date as the project end, such as the closure date in the project tracker or the final invoice date. Write the choice into the protocol and apply it to every project. Do not use the date people remember or the date the last email was sent. A consistent date makes the delay measurable. Note the project tracker field and the invoice field used for the date.
Record any extension or handover period separately. A project that moves into support may legitimately keep some accounts, but the decision should be written. Note the person who approved the extension. The study should separate a planned continuation from an account nobody closed. Record who approved the extension, where the approval is stored, and when the extended period ends or the account must be closed.
Build the account list
Export the account and workspace membership lists from each product, including the creation date, last sign-in, role, and owner. Match the export to the project register by name, client, and date range. Record the match method and any ambiguous cases. An account that cannot be tied to a project belongs in a separate unknown group. List the products that could not be matched and the owner who was asked.
Ask the project lead to confirm the list for each closed project. Add the accounts they remember that are missing from the export. Check the billing records for seats that were never reduced. The reconciled list should show every account the project created and every account it left behind. Add the billing seat count beside the access count for each product.
Match accounts to projects
Create a table with the project, the product, the account identifier, the creation date, and the project end date. Mark whether the account is still enabled at the audit date. Add the last sign-in date and the role. These fields let the reviewer see both the access and the evidence of use. Record the last sign-in date and whether it falls before or after the project end.
Treat a shared account used by several projects as a separate case because its close date may not belong to one project. Record the current owner of that account. Note any account that was reused for a later project. The table should make the exceptions visible rather than forcing them into a simple count. Note the accounts that were reused and the project they moved to.
Sample and verify status
For each project, sample at least five accounts and verify the status directly in the product console. Compare the console status with the export. Record any account that is disabled but still licensed, or enabled but never used. The sample catches the differences between billing state and access state. Record the console page or export used for each verification, and note the person who checked it.
Review the full list for projects with fewer than five accounts. Ask the product owner to confirm the accounts that cannot be checked. Record the verification date and the person who checked. A study that relies only on an export cannot distinguish a disabled account from a deleted one. Add the deletion date where the product retains a tombstone record.
Separate legitimate retention
Some accounts remain active for a valid reason, such as audit access, a legal hold, or a support contract. Ask the project lead to name the reason and the end date. Mark these accounts as retained rather than overdue. A retained account without an end date is still a finding because nobody will close it later. Record the end date and the owner for each retained account.
Check whether the contract requires data access after the project ends. Record the clause and the retention period. Confirm that the account role is read-only where possible. The study should credit a documented retention decision and count an undocumented one as a gap. Note the contract clause and the retention period beside the account, and confirm the access level is read-only.
Measure time to deactivate
Calculate the days between the project end date and the account disable date for each closed account. Report the median and the range rather than a single average. Group the results by product and by project owner. A long tail often points to one team or one product with no close step. Report the median and the ninetieth percentile so the tail is visible.
Count accounts that were never disabled as a separate category. Note the accounts that were disabled within the agreed window. Compare the result with the offboarding policy if one exists. The measure should show where the delay accumulates, not just how many accounts remain. Count the accounts disabled before the project end as a separate early-close group, and note who requested the early close.
Interview the owners
Ask three project leads and one product administrator how they close accounts at the end of a project. Look for the step where the process depends on memory. Ask who receives the request and what evidence confirms completion. Record the answers without attributing them to individuals. Record the role of each interviewee, the date of the conversation, and the product they support.
Compare the described process with the account data. If the process says the project lead requests closure but the data shows no request, the gap is in the handoff. Ask what would make the close step easier. The interview explains the number and suggests the smallest useful fix. Note the fix each person suggested and whether it is already in place.
Report and set a close rule
Report the share of accounts still active, the median delay, and the retained accounts with a documented end date. Add one example of a project that closed cleanly and one that did not. Send the report to the product owners and the project leads. Keep individual names out of the summary. Include the retained accounts and the unknown accounts in a short appendix.
Agree a close rule that fits the business, such as disabling project accounts fourteen days after the closure date unless an extension is recorded. Name the person who triggers the close and the person who verifies it. Add the rule to the project closure checklist. The rule should be short enough to follow. Record the trigger, the verifier, and the evidence that closes the account.
Limits and next cycle
The study measures accounts that appear in the product exports and the project register. It cannot see accounts created outside the approved products or workspaces that the company does not administer. It also cannot prove that a closed account was not used before it was disabled. State these limits in the report. Note the products that were added or retired during the period.
Repeat the study after the close rule has run for a quarter and compare the same products and project types. If the share falls but the median delay rises, inspect the verification step. Keep the table and the protocol with the SaaS register. The measure becomes a control when it is repeated on a schedule. Keep the protocol and the table with the SaaS register so the next run starts quickly.
Sources and next step
Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the vault administrator, SaaS project account, domain contact, loaner handover, and mobile app measures discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.
Compare this study with the vault administrator audit and the SaaS project account 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 the share of saas accounts still active after a project ends 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 the share of saas accounts still active after a project ends, 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 account | Study protocol |
| Sample | Five per project | Study protocol |
| Clock | Project end to disable | Study protocol |
Sources
- NIST Cybersecurity Framework 2.0Identity, access, and asset management outcomes used to frame the measures.
- CISA Cross-Sector Cybersecurity Performance GoalsBaseline access and account controls for small organisations.
- NIST SP 800-53 Rev. 5, Security and Privacy ControlsControl language for access enforcement, audit records, and review.
- GAO Assessing Data ReliabilityApproach for documenting sources, sampling, and verification.
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