How Do You Brief an Executive VA for a San Francisco Team?

What makes an executive VA brief usable on the first day?

A good brief answers questions the assistant would otherwise ask mid-task: what is the outcome, who decides, where is the current information and what happens if the plan changes? “Manage my calendar” is a request. A usable brief says what can move, who may be contacted and when the executive must approve a change.

Start with one page for each recurring area of support. For the calendar, list working hours, protected focus time, meeting-length preferences, required attendees and preparation lead time. For inbox work, name priority senders, approved response patterns and messages that must be escalated. For projects, point to the board or tracker the team already treats as current.

Keep the brief specific without making it brittle. A leadership team may want an assistant to prepare an agenda and propose two meeting times, but not accept a commercial commitment. That boundary preserves executive judgment while allowing routine coordination. VSI’s executive support role covers calendar, inbox, agenda, follow-up and document organization work; use the role details to shape the actual scope.

• Outcome: what “complete” looks like, not just the task name.
• Authority: actions the assistant may take, require approval or must escalate.
• Source of truth: the approved calendar, tracker, document folder or CRM record.
• Quality check: the detail to verify before marking work done.
• Security: role-based access through approved tools; never passwords in chat.

Review VSI executive support duties

View VSI virtual assistant services

How do you turn that brief into a Pacific-time async handoff?

A San Francisco team does not need every request to become a meeting. It does need a predictable way to make decisions in Pacific time. Choose one channel for urgent exceptions, one shared task location for routine work and one named decision owner. State what a handoff message must include: the decision needed, deadline, relevant link and recommended next step.

The following is an illustrative workflow, not a required VSI schedule. A team could ask for a short Pacific-time start-of-day note covering calendar conflicts and top priorities. Routine requests remain in the shared queue. At an agreed mid-day check, the assistant surfaces only blockers needing a decision. A closing update records completed items, open approvals and tomorrow’s first actions. Timing should match the team’s agreed hours and tools.

For example: “Client onboarding deck: draft is in the shared folder; legal review is missing; please choose version A or B by 2 p.m. PT; once approved, I will update the tracker and schedule the review.” That gives the executive an action and leaves a clear record in the agreed workspace.

Keep exceptions deliberate. A sensitive message, purchase, contract term, priority calendar collision or out-of-scope change should go to the designated owner. Review the rules weekly after the team sees where questions cluster.

• Start-of-day note: top priorities, calendar risks and decisions needed first.
• Shared queue: task owner, due point, source link and next action.
• Escalation: context, impact, decision owner, deadline and a proposed option.
• Closing update: completed work, blockers, open approvals and next action.

See how VSI matching and onboarding work

What should the team review during the first week?

Use the first week to test the brief against real work. Compare the handoff to the actual calendar, inbox and project queue. If updates arrive without a needed link, add that rule. If the executive is repeatedly approving a low-risk action, decide whether the authority can be documented. If no one can find the latest project status, simplify the source of truth rather than adding another report.

Bring the practical setup into discovery: recurring calendar patterns, one active project, approved systems and the person who can resolve exceptions. VSI typically matches a virtual assistant within 72 hours of consultation and aims for onboarding within a week, depending on requirements. The first two weeks are designed to find the right fit, so the brief and cadence can be refined rather than treated as permanent from the outset.

Confirm commercial terms separately from work instructions. The first Team Lead VA is $12 per hour*; additional VAs are $9 per hour*. An upfront four-week retainer is required as part of your agreement. It is prepaid credit toward your VA service, not an extra service fee. The dollar amount is confirmed in the agreement based on agreed hours and rates. We have two weeks to find the right VA for your business. Your retainer remains unused service credit while matching is underway. If we cannot find the right person within the two-week matching period, we refund your retainer. Your retainer is used only once you have the right VA, paying for their agreed service at the agreed hourly rates. Once used, billing is weekly with no long-term contract. Testimonials are not a forecast of any team’s results.

• Did the assistant have enough context to complete routine work without guessing?
• Did escalation messages reach the right person in time?
• Which approval rules should be clarified, tightened or delegated?
• Is the end-of-day update concise enough for an executive to act on?

Review current VSI pricing

Watch VSI client testimonials

Common questions

How long should an executive VA brief be?

Start with a concise brief covering outcomes, authority, source systems, escalation and reporting. Add task instructions only when recurring work needs them.

Should an executive VA have authority to move meetings?

Follow written calendar rules. Routine moves may be delegated within stated limits; priority meetings and external commitments can remain for approval.

How do I prevent async handoffs from becoming status noise?

Use one format: completed work, decisions needed, blockers and next actions. Include links to the current calendar, task or document.