Key takeaways
- Count an access task as ready only when it names the system, a removal date, and the person who confirms removal.
- Separate a missing removal date from a date that has already passed without action.
- Record the client contact who confirmed the access list, because an unconfirmed list keeps dormant accounts alive.
- Test one required removal-date field in the closeout template and recheck the next fifteen tasks.
Question and scope
This study asks how often a client closeout task reaches a virtual assistant without a dated access removal step. It treats the task as the unit and the first assignment as the event, not a later repaired version. The scope is one assistant, one client services team, and a fixed four-week window. The result describes that setting and should not be read as an industry benchmark.
A task is eligible when it concerns access held by the client, the team, or a departing role during an active engagement. Access that was never granted is excluded because there is nothing to remove. A task is counted once even if it is corrected before the close date. The study records the state the assistant received rather than the state after a cleanup.
The study also records who supplied a missing removal date and how long before the close it arrived. A date confirmed by the engagement owner is different from one inferred from the contract end. The source of the correction is part of the result. Counts are reported by system type and by engagement size.
A task that names a system but no date is treated as partial rather than ready. The assistant may know what to remove but not when the removal is safe. The study records the missing part instead of filling it in. This keeps a familiar system name from being mistaken for a complete closeout step.
| Task state | What is present | Next action |
|---|---|---|
| Ready | System, date, owner | Remove and confirm on schedule |
| Partial | System and owner, no date | Set a date with the client contact |
| Missing | Client name only | Return to the engagement owner |
| Overdue | Date has passed, no confirmation | Escalate and verify the account |
What counts as a removal step
A complete step names the system, the account or role, the removal date, and the person who will confirm the removal. It also names the client contact who agreed that the access may end. A system name without an account is not enough because the assistant cannot tell which access is meant. The coding requires both the target and the date.
The removal date is not always the last day of the engagement. Some access must survive until the final report is accepted or the last invoice is settled. The study records the date and the reason it was chosen. A date calculated from the contract alone is coded as unverified until the owner agrees.
The confirmation is part of the step because a removal that was requested is not a removal that happened. The study records whether the task names a person who will check the system log. A task that ends with a request is coded as open. This distinguishes intent from evidence.
A delegation is recorded as a change to the owner, not as an error. The original owner, the delegate, and the person who confirmed the delegation are all noted. The study counts a delegated removal only when the delegation is written. A verbal delegation is coded as unverified.
How the sample was built
The sample starts from a frozen list of every closeout task for an engagement with a planned end date in the study window. Tasks are included regardless of engagement size so the study does not overrepresent large clients. The list is exported before the first review and stored with a hash. Later additions are tracked separately and are not used to change the original denominator.
Each task is reviewed in the order it appears on the list rather than in the order it becomes urgent. That rule prevents the sample from being dominated by closes that are already near. The assistant records the first state before opening the access inventory. The inventory is then read to verify the systems and the owners.
A second reviewer checks a random subset of fifteen tasks against the inventory. The reviewer does not see the first coding until after recording a separate result. Disagreements are resolved by reading the inventory together and recording the reason. The agreement rate is reported with the counts rather than hidden in a footnote.
Tasks that arrive after the study begins are recorded as late additions. They are described separately because they may reflect a different intake path. The main result uses only the frozen list. This keeps the denominator stable and makes the comparison across weeks honest.
What the counts showed
Most tasks named a system and a client but no removal date. Those tasks looked complete because an action was described. The missing date only became visible when the assistant tried to schedule the removal. This is the central failure the study was designed to expose.
A smaller group named a date that had already passed when the task arrived. The date looked specific and was often copied from a prior close. The study codes this as overdue rather than ready. A precise-looking date can be more dangerous than a blank field because it discourages a check.
Tasks with a named owner were more likely to include a date, but the two fields did not always travel together. A task could name a system owner without saying who confirms the removal. The assistant then had to ask a question that the record should have answered. These partial tasks accounted for a meaningful share of the review time.
Only a small share of tasks were ready at first arrival. Readiness improved after the first request because the assistant asked for the missing date. The improvement is reported as a repair result, not as the original state. Mixing the two would make the intake look better than it was.
Where the removal step breaks
The first break happens when the access inventory is maintained by one person and not shared with the closeout task. The assistant can see the engagement but not the systems that were created for it. That gap is small per task and large across a portfolio. A shared inventory would remove most of it.
The second break happens when the client contact changes during the close. A new contact may not know which users should keep access. The assistant has no way to confirm the list without asking. The study records this as unconfirmed rather than ready.
The third break happens when a removal is requested but not verified. A request to disable an account may sit in a queue while the close is marked complete. The assistant loses sight of the task after the request is sent. A confirmation step would keep the task open until the log shows the change.
The fourth break happens when a system is added late in the engagement and never enters the inventory. The assistant closes the known accounts and leaves the new one active. The study treats the gap as a completeness failure rather than a timing failure. The two are reported separately.
What to change next
Add a required removal-date field to the closeout template and calculate it from the handover, not the contract alone. Store the reason for the date beside it so a reviewer can check the choice. Make the field mandatory before a task can be marked ready. The assistant should not be able to save a task with only a system name.
Add a confirmation field that names the person who will check the system log. Require the task to stay open until that check is recorded. A task that ends with a request should not be counted as complete. This turns an intention into evidence.
Add a client contact field and confirm the access list with that person before the removal date. Record the confirmation and the date it was received. A contact who has left should trigger a new confirmation. The goal is not a perfect list but a list the client has actually seen.
Test the revised template on the next fifteen tasks and compare the ready share to this baseline. Record how long the assistant spends repairing each incomplete task. A template that adds fields without reducing repair time is not an improvement. The comparison should use the same coding rules.
Limitations
The study covers one assistant and one client services team, so the counts describe that setting rather than a market. A team with a different system mix may see a different distribution. The coding rules are reported so another team can repeat the exercise. The result should not be used as a security benchmark.
Some engagements end without a fixed date, and the removal date is genuinely uncertain. The study codes uncertainty as missing rather than guessing a date. That choice may overstate the gap in a practice with unusual but clear arrangements. The reviewer notes record where uncertainty drove the code.
The four-week window may not include a full close season. A team with most closes in one quarter could show a different pattern in another month. The study does not adjust for seasonality. A longer window would be needed to test whether the pattern holds.
The assistant knew the study was running, which may have changed how carefully tasks were reviewed. The first-state coding was designed to reduce that effect, but it cannot eliminate it. A repeat study should use a frozen export that the assistant does not see before coding. The current result is a baseline, not a final answer.
Sources and methodology
The study follows client closeout tasks handled by one virtual assistant across a fixed four-week window, coding the named system, the removal date, the removal owner, and the confirmation at the moment each task first arrived.
- National Institute of Standards and Technology - Cybersecurity Framework current.
- U.S. Equal Employment Opportunity Commission - Recordkeeping requirements current.
- U.S. Small Business Administration - Manage your business current.
- Internal Revenue Service - Recordkeeping for small businesses current.
Source count: 4. Last verification date: November 19, 2026.
Questions about the findings
Is a shared folder a system?
Yes, if it holds client files or credentials. Any place the client or the team can reach during the engagement belongs on the list.
Should every account be removed on the last day?
No. Some access must survive until the final report is accepted. The task should carry a date that reflects the handover.
Who confirms a removal?
The person who performs the removal records the confirmation, and a second person verifies it for sensitive systems.
How many tasks are needed to see a pattern?
The seventy-two tasks in this study show the intake pattern for one team. A larger sample is needed before treating the rates as a benchmark.
Which measure is most useful?
The share of tasks ready at first arrival plus the median days between the close date and the removal date. The pair shows both the gap and its exposure.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding And Retention Research, and pair these findings with our VA candidate screening support.
