The Day 1 VA Kickoff Meeting: How to Run the First 60 Minutes That Shape the Entire Working Relationship

The first hour with a new VA is the most important hour of the entire engagement. Whatever norms you establish, or fail to establish, become the default. Founders who skip a structured kickoff or run it without an agenda spend the next three weeks doing ad hoc corrections. Their VAs spend the first two weeks guessing what good looks like, and guessing wrong often enough that trust erodes before it’s built.

The Six-Part Kickoff Agenda gives you 60 minutes of structure that shapes the entire working relationship: Role Vision, Communication Norms, First Week Tasks, Working Style, SOP Walkthrough, and Open Questions. Each section is ten minutes. Each section has a specific outcome. Run it in order.

Step 1, Role Vision (Minutes 0–10): What Success Actually Looks Like

Most VAs start a new role with a vague understanding of what “doing well” means. They know the task list. They don’t know the standard they’re being measured against.

Role Vision fixes that in the first ten minutes. Share three specific, measurable outcomes you expect at 30, 60, and 90 days. Not “manage my inbox well”, that is not a success criterion. Instead:

• Day 30: Inbox is processed to zero by end of each working day. All emails are replied to within 24 hours or flagged for my review with a draft.
• Day 60: You’re handling first-touch client emails independently. I review before they go out for the first 30 days, then spot-check only.
• Day 90: The inbox runs without my input on routine correspondence. I receive a weekly digest each Friday.

Concrete milestones give the VA something to aim at. They also give you a shared language for feedback conversations throughout the 60-day arc. “Where are we against the Day 30 target?” is a more useful question than “how’s it going?”

End this section with: “Does this match your understanding of the role?” Gaps in expectation surface here, in the first ten minutes, rather than in a frustrating Week 3 conversation.

Step 2, Communication Norms (Minutes 10–20): The Operating System for the Working Relationship

Communication norms are the most important thing you establish in this meeting, and the most frequently skipped. Without explicit norms, VAs guess, and guesses about how you want to be communicated with are almost always wrong.

Cover six things in this section:

Primary channel. “Slack is where we work. Email is for client communication only. If you message me on email for internal matters, I may not see it for 24 hours.”

Response time expectations. “My expectation is that Slack messages are acknowledged within two hours during your working hours. Not necessarily resolved, acknowledged, with an estimated timeframe.”

Update cadence. “Every working day, send me a brief end-of-day message: what was completed, what’s in progress, and whether anything is blocked. Three bullet points is enough.”

Escalation protocol. “If something is time-sensitive, put [URGENT] at the start of the message. I’ll treat that as a priority. Don’t use urgent casually, if everything is urgent, nothing is.”

Your availability. “I’m available for a quick call between [hours]. Outside that, I respond within two hours on weekdays. Don’t expect responses on weekends unless you’ve flagged it as urgent.”

How to handle blockers. “If you’re stuck on something for more than 30 minutes, message me. Don’t sit on a blocker for hours. A quick question from you is always better than stalled work.”

After the call, send these six norms as a brief written document. The VA who can refer to this document doesn’t need to ask you for the same information twice in Week 1.

Step 3, First Week Tasks (Minutes 20–30): Specific Deliverables with an Explicit Quality Bar

Never end a Day 1 kickoff without a task list. This is the moment to open your project management tool and walk through the first week together, not just the what, but the standard.

For each task, cover three things:

What it is, a one-sentence description of the deliverable.

When it’s due, a specific date and time, not “end of week.” “End of week” is a different deadline depending on where in the world your VA is and how they define the work week.

What good looks like, one or two sentences describing the quality standard. This is especially important for judgment-based tasks like writing, research, or client communication. For example: “Good looks like professional tone, under 150 words, with a single clear call to action. Here’s an example of an email I’ve sent before, match that register.”

If there’s a template, format, or reference document for any task, share the link now, during the meeting. Not in a Slack message 20 minutes later that gets buried. Reducing follow-up questions is a direct quality-of-life improvement for both of you, and it signals that you came prepared.

Step 4, Working Style (Minutes 30–40): How You Work and How to Work With You

This section exists because no two founders operate the same way, and the fastest path to alignment is explicit communication rather than letting the VA discover your preferences through trial and error over six weeks.

The Working Style Card is a one-page document you fill out once and give to every new VA at the Day 1 kickoff. Build it before this meeting. Here is the template:

---

Working Style Card, [Your Name]

My peak focused hours: [When you do deep work and should not be interrupted except for urgent matters]

How I prefer to receive questions: [Batched at end of day / Immediately as they arise / In writing, not verbally on a call]

How I prefer to give feedback: [Directly in the task comment / In a weekly review call / Via Slack message on the same day]

My non-negotiables: [Things that matter intensely, e.g., client emails must be reviewed before sending; deadlines are hard commitments, not targets; no surprises on active client projects]

What frustrates me: [Be honest, e.g., vague status updates that don’t answer “where is this?”; work submitted without a self-review note; finding out about a blocker three days after it arose]

What I value most in a working relationship: [e.g., proactive communication; flagging issues early; asking questions rather than guessing and getting it wrong]

My working hours and timezone: [Your standard availability]

---

After sharing the card, ask the VA two questions: “How do you prefer to receive feedback?” and “Is there anything about how you work that would be useful for me to know?” Listen fully. Take a note. This is not a formality, what they tell you will shape how you interact for the next 60 days and determine whether the relationship scales.

Step 5, SOP Walkthrough (Minutes 40–50): Walk Through One Core Process Together

The SOP Walkthrough is where theory becomes practice. Choose the most important process you’re handing off, the one the VA will execute most frequently in Week 1, and walk through it together on the call.

Don’t present it. Walk through it. Open the SOP document and read each step aloud, then ask the VA to narrate the step back to you in their own words. When they narrate it back, you learn immediately whether the SOP is clear or whether it has gaps.

The narration method catches two things systematically: steps you’ve skipped because they seem obvious to you (but aren’t to someone new), and steps that are ambiguous enough that a reasonable person could interpret them in two different ways and execute them differently.

When you hit a step they can’t narrate clearly, stop. Fix the SOP in real-time, update the document while they watch. “I realize I didn’t explain what to do if the client hasn’t replied within 48 hours, let me add that now.” This live editing signals that the SOP is a working document, not a rigid script handed down from above.

End the walkthrough with: “Walk through this process independently this week. If you find any step that’s unclear, update the document with a note and flag it for me to review.” That single instruction makes the VA a co-owner of the process documentation from Day 1, which is the foundation of a good systems-oriented working relationship.

Step 6, Open Questions (Minutes 50–60): Make It Explicitly Safe to Ask

The final ten minutes belong entirely to the VA. The question you open with matters: “What do you need to know before you start that we haven’t covered yet?”

Founders often rush or skip this section because they’re satisfied with the prior 50 minutes. Don’t. The VA has absorbed a significant amount of new information in a short period. There are almost always questions they’ve been holding back, not wanting to interrupt the flow. The value of making it explicitly safe to ask is that those questions surface now rather than three days into their first task.

A follow-up prompt that works consistently: “Is there anything about the role, the business, or how we work together that you’re still uncertain about?” The word “uncertain” reaches things the VA might not have framed as questions but which are blocking their confidence.

If they say “no, I think I have everything”, probe once. “Most people starting a new role have at least one thing they’re unsure about. Anything at all?” In most cases, one more question comes out. In the cases where it doesn’t, you’ve still signaled that asking is welcomed.

Close the meeting with a specific next step, not a vague handoff: “Your first task is due [date and time]. I’ll check in via Slack at [specific time] tomorrow. If anything comes up before then, message me directly, don’t wait.” Give them a concrete time to expect contact from you. Uncertainty about when they’ll next hear from you is low-grade anxiety that has no benefit to anyone.

Your Next Step

Fill out your Working Style Card before your next VA’s Day 1, it takes 20 minutes, you’ll use it with every VA you ever hire, and it eliminates an entire category of alignment failures that normally take three weeks to surface. Then block 60 minutes on your calendar for the morning of Day 1 and protect it. The meeting that shapes every other meeting is the one most founders skip.