A role-scope card is a short working document that tells a new virtual assistant what the job includes and where it stops. It is written before the first login so the first request is not also the first discussion of scope. The card is not a job description and not a policy manual. It is the page the manager and the assistant can both point to when a task is unclear.
Start with the work the role will actually touch
A role-scope card begins with the tasks the assistant will handle in the first month, written as verbs. Use words such as prepare, sort, confirm, and draft instead of job titles or broad categories. A title hides what the role does, while a verb shows the action a reviewer can check. The card should let a new assistant point to a task and know whether it belongs to the role.
Ask the manager and the reviewer to describe the role separately before comparing notes. The manager usually describes the intended scope, while the reviewer describes the work that actually arrives. Record where the two lists differ, because that gap is often the first source of confusion. Resolving it before the start date is cheaper than correcting it during a live task.
Group the tasks by the system they touch rather than by the department that owns them. One task may cross a shared drive, a client portal, and an email inbox. Recording the system helps the team plan access and shows where a missing login could block the work. It also makes the reviewer's place in the flow easier to see.
Name the decisions the assistant may make alone
List the small decisions the assistant may make without asking, such as naming a file from the agreed convention or ordering a routine queue. Keep the list short and concrete so the permission does not become a general license to improvise. Each entry should describe a decision a reviewer could later reconstruct. If the team cannot describe the decision that way, it probably needs review.
For each allowed decision, record the rule the assistant should apply and one worked example. The example is the fastest way to show where the boundary sits in real work. If the team cannot produce an example, the decision likely belongs on the escalation list. Examples also give the reviewer a consistent standard during the first week.
Record decisions that are allowed only after a documented check, such as sending a reminder from an approved template. The check might be a recipient review, a spell check, or a comparison with the source record. Naming the check makes the permission auditable without turning every task into an escalation. It also tells the assistant what evidence to leave behind.
Name the decisions that always escalate
Every role needs an escalation list that covers money, clients, legal positions, and access. A request to approve a refund, change a commitment, or share a document with a new recipient should stop at a named person. Use plain examples so the assistant can recognize the situation quickly. A list of abstract categories is harder to apply under time pressure.
Record the route with a name and a backup rather than only a department. An unanswered escalation is often caused by an unclear owner, not a difficult question. The card should say who decides and how quickly a response is expected. That detail turns a policy into a route the assistant can actually use.
Separate a question from an escalation in the wording of the card. A question asks for information, while an escalation asks for a decision that changes the work. The assistant should be able to send questions to the reviewer and decisions to the owner. A short label on each request keeps the two paths from blending together.
Record the tools, accounts, and access level
List each tool the role will use and the level of access required for the named tasks. Distinguish between view, edit, share, and administrative rights because the difference matters when a task changes. The card should show the minimum access needed, not the access that would be convenient. Least privilege is easier to grant at the start than to withdraw later.
Record who grants access and who removes it when the role ends or changes. An access list without an owner becomes stale as soon as the first person changes job. Keep the grant and removal steps in the same section so the review covers both directions. The removal step should name a date and a person, not only a process.
Note any tool the assistant may not use even when a login is available. A shared inbox or client portal may contain information outside the role's scope. Write the exclusion next to the tool rather than leaving it to the assistant's judgment. A clear exclusion protects the client and gives the assistant a reason to stop.
Write the stop rule in plain language
Write the stop rule as one sentence the assistant can repeat without reading the card. A useful version says to stop when a request needs a decision, a new recipient, a different system, or a changed promise. The wording should be specific enough to apply under pressure. A long explanation is less likely to be remembered than a short rule.
Give the rule a visible place in the workspace, such as the top of the task form or the first page of the role guide. A rule buried in a long document is not a control. The assistant should be able to point to it when a request arrives. Visibility also helps the manager reinforce the rule during review.
Explain what happens after a stop, including who is contacted and what the assistant should record. A stop that leaves the task in limbo creates pressure to continue without approval. The card should name the reviewer, the channel, and the expected response time. The record should capture the question and the decision that followed.
Review the card at the end of week one
Compare the card with the tasks that actually arrived at the end of the first week. Mark the tasks that were missing, the permissions that were wrong, and the decisions that caused a question. Treat the comparison as the agenda for the next update rather than a performance score. The assistant's experience is evidence about the card, not only about the assistant.
Keep a short change log at the bottom of the card with the date and the reason for each revision. A later reader should be able to see why a rule was added. The log also prevents the team from removing a control that was added after a real mistake. Two or three lines per month are usually enough.
Ask the assistant which part of the card was hardest to use and which part was never needed. The answer may reveal a rule that is too detailed or a section that belongs in another document. A card that is accurate but unusable will be ignored during a busy day. The review should simplify as well as correct.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Small Business Administration — Hire and manage employees guidance on setting expectations and managing a new working relationship.
Related reading
Write a first-month check-in script for a virtual assistant
A repeatable check-in script that surfaces blockers, review load, and role drift without turning the meeting into a status recital.
Set a working-hours and availability agreement with a virtual assistant
A working-hours agreement that covers time zones, response windows, peak coverage, and the difference between urgent and ordinary requests.
Create a mistake-review ritual for a new virtual assistant
A blame-free mistake review that separates the task defect, the instruction gap, and the review miss so the same error does not return.
