You got the client. Great. Then you opened the shared drive and found a folder called "MISC FINAL v3 USE THIS ONE." The password doc has seven entries and none of them work. The client says the previous VA "handled everything" but cannot quite explain what everything was. Welcome to one of the most common situations in VA work, and one nobody really prepares you for.
This is not about blame. The previous VA may have been excellent. They may have left in a hurry. They may have never been told documentation was part of the job. None of that matters right now. What matters is that you are here, the client is watching to see if you can handle it, and the business still needs to run.
Here is how you do this properly.
The First 48 Hours Are for Access, Not Action
Before you touch anything, you need to know what you are touching. Spend the first 48 hours doing a full access audit. Not guessing. Not assuming the client has a list. Go tool by tool and map out exactly what exists, who currently holds the login, and what is missing or unverified.
Work through every category: email, calendar, social media accounts, project management tools, cloud storage, scheduling software, e-commerce platforms, CRM, any subscription services, and anything the client mentions offhand. For each one, note the current status. Does the login work? Is it tied to the previous VA's personal email? Does the client even know the account exists?
Use a simple spreadsheet. Three columns is enough: Tool, Access Status, Action Needed.
This audit does two things. It shows the client you are methodical, and it protects you. If something is already broken or missing before you start, you need that documented before anyone decides it became broken on your watch.
Related: How to handle client logins and passwords as a VA
The Conversation You Need to Have Before You Change Anything
Once you have the access picture, sit down with the client for a "what was working" conversation. This is not a critique session. You are gathering intelligence.
Ask them what they liked about how things ran. Ask what frustrated them. Ask what they are nervous about you changing. Ask if there are any recurring tasks the previous VA handled that have not been handed over yet.
Listen more than you talk. The client hired the previous VA for a reason, and some of what that person built might actually be solid. Your job in this conversation is to separate the things that need fixing from the things that just need inheriting.
Do not use this call to start listing problems you have spotted. Not yet. Take notes, confirm your understanding of current priorities, and close with what you are going to do in the first 30 days.
Hold a 30-Day Freeze on Big Changes
This is the rule that will save your reputation: do not redesign anything in the first 30 days.
You can fix things that are broken. You can fill gaps. You can document what exists. But restructuring the folder system, migrating to a new tool, or overhauling a workflow before you understand why it was built that way is a fast path to making things worse.
The 30-day freeze is not about being passive. It is about earning the right to change things with evidence rather than instinct. After 30 days you will know what the client actually cares about, what is causing friction, and what they will and will not adopt.
Ask for a Handover Call if the Previous VA Is Reachable
If the outgoing VA is willing to do a handover call, take it. Even 30 minutes with them can save you days of archaeology.
Come prepared. Have your access audit in front of you. Ask specifically about any automations running in the background, recurring tasks that are date-sensitive, and any client preferences or sensitivities they picked up that are not written down anywhere.
Keep the tone neutral and professional. They may be defensive. They may be perfectly warm about it. Either way, your goal is information, not a debrief on what went wrong.
If they are not reachable, do not fill the gap with speculation. Document what you cannot verify and flag it to the client.
Documenting as You Go Is Now Part of Your Deliverable
The reason you are inheriting a mess in many cases is that the previous VA never wrote anything down. You are going to be different.
From day one, document every process you touch. Not in a way that creates extra work, but as a natural part of doing the work. When you complete a task for the first time, write the steps. When you figure out why a workflow exists, note it. When you set up a new login, log it in the credential tracker immediately.
By the end of your first 90 days, the client should have a system they could hand to someone else without any chaos. That is not just good for them. It is what separates a VA who can be replaced in a weekend from one who has obvious ongoing value.
Related: Client onboarding for VAs, step by step
When to Charge a Cleanup Fee Instead of Absorbing the Mess
Not every inherited situation is just a matter of time and patience. Some are genuinely significant remediation work: broken automations, years of unorganized files, accounts that need a full audit and restructuring, subscriptions that have never been reviewed.
If what you are inheriting is going to require 10 or more hours of audit and cleanup work before you can even begin your regular duties, that is a scoped project and it should be priced as one.
Raise this early. Something like: "I want to flag that the access audit and initial cleanup is going to take roughly X hours before I can move into your regular support. I would suggest we treat that as a one-time project fee separate from your monthly retainer." Most reasonable clients will respect that conversation far more than finding out three weeks in that you have been absorbing unpaid hours.
Do not wait until you are resentful to bring it up.
A Short Inherited-Account Checklist
Run through this in your first 48 hours:
- Email accounts: confirmed access, recovery email updated
- Calendar: access confirmed, permissions correct
- Social media: all active platforms listed, logins verified or flagged
- Cloud storage: folder structure mapped, previous VA's personal files noted
- Project management tool: active tasks identified, previous VA removed or deactivated
- CRM or contact database: access confirmed, data integrity spot-checked
- Scheduling or booking tool: upcoming appointments reviewed
- Any active automations: identified and documented, not touched yet
- Subscriptions and billing: list of active subscriptions with login status
- Credentials master doc: created or updated with all of the above
Talking About the Previous VA Without Making the Client Feel Judged
Here is the thing about criticizing the previous VA: the client chose them. If you start pointing out everything that was done wrong, the client hears "you made a bad decision." That makes them defensive, and it shifts focus away from the work.
You do not have to pretend problems do not exist. You just need to frame them without blame. "This part of the system is not documented yet, so I am going to build that out" lands completely differently from "the previous VA never documented this." Same information. Very different dynamic.
Stay solution-focused. The client already knows something was off, which is why there is a new VA sitting in front of them.
Related: How to offboard a VA client cleanly
You Are Not Just Filling a Gap. You Are Setting a New Standard.
The clients who have been through a difficult VA transition are often the most loyal once they find someone who handles it professionally. They have seen the alternative.
Take the audit seriously. Freeze the changes. Document everything. Charge fairly for cleanup work. And never forget that how you handle this first stretch tells the client exactly what working with you long-term is going to look like.
If you want a structured way to set up your client systems from day one, the Virtueasy Onboarding Kit covers the documentation framework, credential tracking, and workflow setup that makes handovers like this one far less chaotic on both sides.