How to Write a Scope of Work for a Remote Assistant

Many remote assistant placements that disappoint don't fail because of the assistant. They fail because nobody defined the work. The leader had a vague sense of "help with admin", the assistant guessed at priorities, and after a few weeks both felt frustrated. A clear scope of work prevents this. It gives the assistant direction, helps you choose the right person, makes onboarding faster and gives you a basis for measuring success.

This guide explains how to write a scope of work for a remote assistant, step by step, with a template you can adapt. A scope of work is different from a job description: a job description attracts candidates, while a scope of work defines the specific outcomes, tasks, tools, boundaries and measures for a particular placement. For job description help, see our virtual assistant job description template.

Step 1: define outcomes

Start with what you want to be different in three to six months. Examples:

• "My inbox is at zero by the end of each day, and I only see emails that need me."
• "Every sales meeting is logged in the CRM within 24 hours with next steps."
• "The books are reconciled weekly, and month-end close is done by the fifth business day."
• "Prospective clients receive a response within one business hour."

Outcomes keep the scope focused on results rather than activity.

Step 2: list tasks

Brainstorm every task you'd like to hand off. A useful method: track your own work for a week, noting tasks that are repetitive, rule-based, time-consuming or outside your strengths. Then group tasks into categories, such as calendar, inbox, travel, CRM, finance, research, projects and personal.

For each task, note:

• Frequency: daily, weekly, monthly or ad hoc.
• Volume: rough amount of work.
• Complexity: routine or judgment-heavy.
• Priority: must-have from day one, or later.

Step 3: prioritize and phase

Not everything should start on day one. Phase the scope:

• Phase 1 (first two weeks): routine, well-defined tasks with clear SOPs.
• Phase 2 (weeks three to six): tasks requiring more context and judgment.
• Phase 3 (after two months): complex or sensitive responsibilities, as trust builds.

Phasing reduces overwhelm and lets you adjust based on early results. See the first 30 days success plan.

Step 4: tools and access

List every system the assistant needs, with the level of access:

Follow least-privilege principles: give the minimum access needed for each task. See the least-privilege access checklist.

Step 5: boundaries and decision rights

Define what the assistant can decide alone, what needs approval and what's always yours. Include communication rules (what goes out in whose name), spending limits, payment boundaries and confidential topics. See decision rights and approval limits.

Also note what's out of scope. This prevents scope creep and protects the assistant from requests they're not equipped or authorized to handle, such as legal advice, clinical decisions or signing contracts.

Step 6: schedule and availability

Define when you need the assistant available, the overlap with your working hours, response time expectations and how coverage works during absences. With ExecWing, each placement is dedicated, on a customized schedule based on your needs and budget. See US–Philippines time zones and working hours for overlap planning.

Step 7: communication rhythm

Set how you'll work together:

• Daily: a short check-in or written update.
• Weekly: a one-on-one and planning session. See the weekly check-in template.
• Monthly or quarterly: a review of the scope and results.

Also define channels: chat for quick questions, email for external matters, the project tool for tasks.

Step 8: success measures

Turn outcomes into measurable indicators:

• Inbox response times.
• CRM update completeness.
• Reconciliation timeliness.
• Meeting scheduling turnaround.
• Error rates on key tasks.
• Hours the leader recovers, by their own estimate.

See KPIs for virtual assistants for more examples.

Step 9: documentation

List the SOPs needed for each task and who will create them. Video recordings can speed this up. See video SOPs for delegation.

Sharing the scope with the assistant

Once the assistant starts, walk through the scope together in the first week. Explain why each outcome matters, not just what the tasks are. Invite questions and suggestions; assistants often spot tasks that could be done more efficiently or missing steps in a process. Store the scope where both of you can see it, and refer to it in weekly check-ins so priorities stay clear.

Step 10: review and update

A scope of work is a living document. Review it after 30 days, then quarterly. Add tasks as trust grows, remove tasks that aren't valuable, and update measures.

Sample scopes by role

Scopes look different depending on the role. Brief examples:

Executive assistant to a CEO: outcomes include a managed inbox, a calendar that protects focus time, smooth travel and prepared meetings. Tasks: inbox triage and drafting, scheduling, travel booking, meeting preparation and notes, expense reports, board materials coordination. Out of scope: signing documents, approving payments, HR decisions.

Revenue assistant for a sales team: outcomes include a clean CRM, more meetings booked and faster follow-up. Tasks: lead research, list building, CRM hygiene, meeting scheduling, follow-up sequences under approved templates, pipeline report preparation. Out of scope: pricing discussions, contract negotiation.

Bookkeeping assistant: outcomes include weekly reconciliations and timely month-end close. Tasks: transaction categorization, reconciliations, AP and AR support, receipt management, month-end checklists. Out of scope: tax filings, approving or releasing payments.

Operations assistant: outcomes include smooth vendor management and up-to-date trackers. Tasks: vendor coordination, order processing, scheduling, data entry, reporting. Out of scope: contract signing, hiring decisions.

Estimating the time required

A scope helps you estimate how much time the work requires, which informs the schedule. Add up the frequency and volume of each task, include time for communication and learning, and leave room for ad hoc requests. Don't aim for perfection: the first month will show where estimates were off. Your provider can help translate the scope into a customized schedule.

Scope of work template

• Role title and supported leader(s).
• Purpose: one or two sentences.
• Outcomes (three to six months).
• Tasks by category, with frequency and phase.
• Tools and access table.
• Decision rights summary.
• Out of scope list.
• Schedule and availability.
• Communication rhythm.
• Success measures.
• SOPs needed.
• Review dates.

Scopes for teams and enterprise

When an assistant supports several leaders or a department, the scope should clarify priorities between them and who resolves conflicts. In larger programs, scopes can be standardized by role and adjusted per team. See designing assistant pods by department and dedicated pods.

A worked example

A founder of a growing agency wants "help with everything." Instead, she writes a scope: outcomes include a clean inbox, client meetings scheduled within a day of request, and invoices sent on the first business day of each month. Phase 1 covers calendar and inbox; Phase 2 adds client onboarding and invoicing preparation; Phase 3 adds vendor management. She lists tools with access levels, defines spending and communication boundaries, and sets weekly check-ins. The scope helps ExecWing match an assistant with agency experience, and after 30 days, they review progress and move to Phase 2 on schedule.

Common mistakes

Vague scope. "Help with admin" isn't a plan.

Everything on day one. Phase the work.

No out-of-scope list. Scope creep follows.

No measures. You can't improve what you don't track.

Never reviewing. Update the scope as the role grows.

Frequently asked questions

How long should a scope of work be?

Usually two to four pages. Enough detail to guide work, short enough to read.

Who writes it?

The leader, often with help from the provider. The assistant can refine it after the first weeks.

Is a scope of work a contract?

Not necessarily. It's an operational document. Contractual terms are handled separately.

Can ExecWing help define the scope?

Yes. We discuss scope during your fit call and use it to match candidates.