Small business outsourcing workflow guide

Write a first-week task list for a newly assigned virtual assistant

A first-week task list that gives a new assistant one owned queue, visible checkpoints, and a review that catches gaps before they harden.

Write a first-week task list for a newly assigned virtual assistant

Start with the queue the assistant will own

Start with the one queue the assistant will own in the first week, not the full list of tasks the business hopes to hand over. Write the queue name, the channel it arrives through, and the person who answers questions about it. A new assistant needs a narrow surface where repetition can build judgment. A list of ten unrelated duties produces motion without a reliable result.

Describe the queue's normal volume and the hours when it peaks so the first day does not arrive as a surprise. Record what a routine item looks like and what makes an item unusual. Include one recent example that was handled well and one that needed a second review. The assistant should see the standard before meeting the exceptions.

Name the first deliverable and its check

Choose a deliverable that can be finished inside two working days and checked by someone else. A daily summary, a cleaned contact list, or a batch of verified order notes all work because each has a visible end. Write the acceptance check in the same sentence as the task. A task without a check becomes a conversation about whether it was done.

Keep the deliverable small enough that the assistant can repeat it on the second day without starting over. The repetition is what reveals whether the written instruction is complete. If the assistant asks the same question twice, treat it as a gap in the list rather than a gap in the person. Fix the list before adding another duty.

Show the check to the person who will perform it and ask them to describe what a passing result looks like. If they describe something different from the written check, the two of you have found a hidden disagreement. Rewrite the check until both descriptions match. A check that only the owner understands cannot be used to train or to review.

Set check-in points that do not depend on memory

Put two short check-ins on the calendar before the week begins, one at the end of the first morning and one before the second day closes. Each check-in should ask what the assistant completed, what blocked the work, and what the list failed to explain. Fifteen minutes is enough when the questions are fixed. A check-in that drifts into new assignments defeats its purpose.

Record the answers in the same note so the next conversation can build on them. The assistant should be able to read the note before the next shift and see what changed. Do not rely on a chat thread that will scroll away by Friday. A written checkpoint turns a friendly conversation into a usable record.

Record the tools and access the work requires

List every tool the queue touches, the access level needed, and the person who grants it. Separate read access from send access and from the ability to change a record. A new assistant rarely needs the full permission set on the first day. Grant the narrowest access that lets the first deliverable be finished and checked.

Confirm that each login works before the assistant is asked to use it under time pressure. Record the date access was granted and the date it should be reviewed. A tool that opens but cannot save is a hidden stop that the task list should expose. The access list belongs with the task list, not in a separate message.

State what the assistant must not touch

Write a short list of decisions the assistant may not make, such as refunds above a set amount, bank-detail changes, or a promise of a delivery date. Explain what to do instead of guessing, and name the person who receives the handoff. A prohibition without an alternative creates a dead end. The assistant needs a safe next action for every restricted case.

Include examples that look routine but are not, such as a customer who asks to change the account on file. The list should be short enough to remember and specific enough to apply. Review it with the assistant during the first check-in. A boundary that is never discussed is usually discovered through a mistake.

End the week with a written review

Ask the assistant to write half a page about what the queue taught them in the first week. Prompt them to name one instruction that was unclear, one tool that slowed the work, and one question they answered without help. The owner should add what the first deliverable proved and what it did not. This is a review of the list, not a performance rating.

Use the review to remove one task and clarify one instruction before the second week begins. A first-week list that never changes is either perfect or unread. Record the change and the reason so the next new assistant inherits a better version. The goal is a list that survives a second person, not a document that flatters the first.

Hand over the second week with one change

The second week should add one related duty rather than a second unrelated queue. Choose something that uses the same tools and the same judgment, such as handling a follow-up on the items the assistant already reviewed. Write the new acceptance check beside the old one. A gradual increase protects quality while the assistant is still learning the business.

Ask the assistant to update the task list with what they now do differently. The edit is a sign that the list is becoming a working tool rather than a trainer's handout. Keep the original version so the owner can see how the role grew. A role that cannot show its own evolution is hard to train again later.

Sources and next steps

Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.

Related guides

Free role planning call

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to prepare a practical Philippines staffing conversation.

Contact Us