How to Onboard a Virtual Assistant for Your Real Estate Business (First 30 Days)

Setup & Access

Goal: Your VA has everything they need to see how your business operates. Nothing more yet.

The biggest mistake agents make in week one is trying to delegate tasks before the VA understands the business. Resist this. Week one is about infrastructure — access, visibility, and communication norms. Task delegation comes in week two.

Day 1–2: The Intake Call

Before you hand over a single login, spend 60–90 minutes on a structured intake call. Cover:

• Your current tools: CRM platform, email provider, calendar, transaction management software, and MLS access method
• Your transaction volume: How many active listings, pending contracts, and closings you're managing right now
• Your biggest time drains: The 3–5 tasks eating the most hours each week
• Communication preferences: Do you want daily summaries via email, a shared task board, or a quick check-in call?
• Response time expectations: What's urgent (same-hour response), what's routine (same-day), and what's background (this week)

Day 2–4: Platform Access

Grant access to the systems your VA will actually use. For Phoenix real estate agents, this typically includes:

• Email: Create a delegated access account or a shared inbox alias — not your primary credentials. Use Google Workspace or Microsoft 365 delegation rather than sharing passwords directly.
• CRM: Most platforms (Follow Up Boss, kvCORE, Chime, LionDesk) have role-based access. Set permissions to match week-one scope — read and update, not admin.
• ARMLS access: If your VA is licensed under ADRE, they can operate under ARMLS with your broker's approval. Coordinate with your broker early — this process takes a few days. An unlicensed VA cannot have independent ARMLS access for active listings.
• Transaction management: Dotloop, SkySlope, or DocuSign — create a VA seat with appropriate permissions. They should be able to view and edit files you've shared with them.
• Calendar: Google Calendar sharing or Calendly access for scheduling tasks. Delegate scheduling rights only, not the ability to accept external meeting requests on your behalf without approval.

Day 4–5: Communication Norms

Set the operating rhythm before the first task ever gets assigned. Vague communication is the number-one reason VA relationships underperform in the first month.

Define and document:

• Daily check-in format: A quick Slack message, a shared task board update, or a 5-minute call — pick one and stick to it during week one. You can reduce check-in frequency in weeks three and four.
• Escalation path: What does the VA do when they hit something they're unsure about? "Ask me first" is fine for week one. Document it explicitly.
• Turnaround expectations: If a task lands in the VA's queue at 9am, when should it be done? Same day? Within 4 hours? Make this explicit for routine tasks vs. urgent requests.
• Feedback loop: How will you let the VA know when something was handled well vs. when it needs to be redone? A simple "this was right, here's what needs to change" note attached to completed tasks beats vague frustration at the end of the month.

Week 1 output: Your VA has read access to your core systems, a clear picture of your business, and knows exactly how to communicate with you. No tasks delegated yet. You've set the foundation.

Process Handoff

Goal: Document 3–5 recurring tasks well enough that someone else can execute them. Hand off the first two.

Week two is where the actual work starts — and where most agents underinvest. The difference between a VA who operates independently and one who needs constant hand-holding is documentation. You need to do this once, and it pays dividends for months.

Document Your Workflows — With Screen Recordings

Pick your 3–5 most recurring tasks and record yourself doing each one. Loom, Screencast-O-Matic, or even a Zoom recorded to the cloud works fine. Narrate while you work. A 5-minute screen recording of you processing an email inbox or updating a CRM contact record is worth more than a 2-page SOP document that leaves ambiguity at every step.

For Phoenix real estate agents, the highest-value processes to document first:

• New lead intake: How does a new lead get into your CRM? What fields do you fill in? What follow-up sequence do you trigger?
• Listing prep checklist: What documents do you gather before an ARMLS entry? What information needs to be in the listing file before it goes live?
• Transaction intake: When a contract is accepted, what happens? Who gets notified, what file gets created, what deadlines get entered?
• Email triage: How do you decide what gets responded to immediately, what gets forwarded, and what gets filed?
• Vendor coordination: How do you schedule inspections? Who do you contact at which title companies?

Define Escalation Paths for Arizona-Specific Tasks

Phoenix transactions involve forms that carry legal weight: the BINSR (Buyer's Inspection Notice and Seller's Response), the SPDS (Seller's Property Disclosure Statement), and the Cure Period Notice. If your VA is licensed under ADRE, they can handle document preparation — but you still need a clear escalation path for anything that requires your judgment as the agent of record.

Document explicitly: what can the VA execute independently, what requires your review before going out, and what should come directly to you without the VA attempting it. This protects your license and prevents costly mistakes during the Arizona deadline windows.

Hand Off the First Two Tasks

Start with your two least-risky, most-recurring tasks. Good candidates: email triage and daily CRM updates. Bad candidates for week two: anything that touches client communication directly or requires judgment about contract terms.

For each handed-off task: share the screen recording, set the expectation, review the first two or three outputs together, and give specific feedback. This calibration in week two is what makes weeks three and four run smoothly.

Week 2 output: You have documented workflows for your top recurring tasks, and your VA is handling two of them independently. You're reviewing outputs and calibrating. The rest of your task list is still on you — for now.

Independent Tasks

Goal: VA runs 3–5 recurring tasks without prompting. You review outputs and refine SOPs.

By week three, your VA should be executing the two tasks from week two without supervision — and you're ready to expand the scope. The goal this week is to move from "I assign, they execute" to "they know the recurring work and handle it."

Expand the Task Scope

Add 2–3 more tasks to the VA's independent queue. Based on what you documented in week two, choose tasks that have clear inputs and outputs — not tasks that require real-time judgment calls. Suitable additions for week three:

• Social media scheduling (content you approve, they post)
• Transaction deadline tracking (entering key dates from accepted contracts into your calendar and transaction management system)
• Vendor follow-up calls (scheduling inspections, confirming title appointment times)
• MLS listing documentation assembly (gathering required photos, square footage, disclosure docs — pending your review before submission)
• HOA certification request coordination (ordering HOA certs from management companies for listings and transactions)

Review Outputs, Adjust SOPs

Look at what your VA produced this week and be specific about what needs adjustment. "This was wrong" is not useful feedback. "The SPDS should be attached to the file before you notify me it's ready" is. Update your documentation after each correction so the SOP improves rather than the same issue recurring.

You're looking for two things: execution quality (did they do the task right?) and proactive judgment (did they flag anything unusual, or did they just proceed with a task that should have been escalated?). The second one matters more. A VA who executes correctly but doesn't flag an unusual BINSR response you would have wanted to see is a liability in an Arizona transaction.

Shift to Async Check-ins

If week one was daily check-ins, week three should start moving toward end-of-day summaries rather than check-ins throughout the day. Your VA should be able to send you a written recap of what got done, what's pending, and any flags — once a day, in writing. You review it when convenient. This is the operating rhythm you'll maintain long-term.

Week 3 output: Your VA is running 3–5 tasks independently. You're reviewing outputs, not managing process. SOPs are getting sharper. You're starting to feel time coming back.

Full Integration & First ROI Review

Goal: Full workload delegation, weekly check-ins only, and an honest ROI look at month one.

Week four is where the model matures. Your VA knows your systems, your workflows, and your preferences. Daily oversight should be unnecessary by now. The job this week is to complete the delegation and do an honest accounting of whether month one delivered value.

Delegate the Full Recurring Workload

Move everything that should be delegated into the VA's queue by end of week four. This is not "hand off everything at once" — it's completing the transfer of the recurring tasks you identified in weeks one and two. At this point:

• Email inbox is triaged daily by the VA; you handle what needs your reply
• CRM is updated after every lead interaction; you see a clean database
• Transaction files are organized with deadlines entered; you review the BINSR/cure period calendar, not manage it
• Listings are prepped and documentation is assembled before you make any submission decisions
• Vendor coordination happens without you scheduling it

Move to Weekly Check-ins

Daily summaries can step down to a weekly review call or written summary — 15–30 minutes maximum. Your VA knows what's expected. Weekly touchpoints should cover: what's in progress, any flags or questions that need your input, upcoming deadlines in active transactions, and anything that needs a process change.

If you're still doing daily check-in calls in week four, the onboarding hasn't finished. That's a signal to go back to week three — find where the handoff broke down and fix the SOP, not the check-in frequency.

The 30-Day ROI Review

Do this honestly at the end of month one. The math is simple:

• Hours recovered: How many hours per week are you no longer spending on admin? Multiply by your effective hourly rate as an agent.
• Cost of VA: What did you pay this month?
• Net value: Hours recovered × hourly rate, minus VA cost. If you're recovering 10 hours/week at $150/hour, that's $6,000/month in recovered time — against a typical retainer of $1,400–$3,600/month.

If the hours recovered feel smaller than expected, identify where: did the handoff stall on a specific task? Did documentation fall short? Is the VA handling tasks that aren't actually high-time-cost for you? Fix the delegation, not the concept.

Also review quality. How many outputs required rework? Were any client-facing deliverables — emails, documents, follow-ups — handled in a way you wouldn't have approved before they went out? If yes, that's a documentation gap, not a VA capability problem (usually).

Week 4 output: Full delegation is complete. Weekly check-ins replace daily oversight. You've reviewed month-one ROI and identified what to improve in month two.