Prepare a virtual assistant onboarding week that ends in a review

An onboarding week should end with a review, not just a completed checklist. Start with the access, the first task, the feedback, and the readiness decision. A checklist without a review leaves the manager guessing. Use the same format for every handover so the next reader can scan it. Keep the source link with the task so the next reviewer can check it. The client should know who is handling the question and when to expect an answer.

Keep the week focused on one or two real tasks. A new assistant who does one task well is more useful than one who attended every meeting. Record the exception and the person who approved it. Test the rule on one real task before applying it to the queue. Test the brief on one real task before applying it to the whole role. The assistant should record the owner and the date before the next shift.

Check the systems, the files, and the communication channels before day one. Record the owner of each access request. A new assistant without access cannot work. Separate what was observed from what was assumed. The assistant should record the owner and the date before the next shift. The client should know who is handling the question and when to expect an answer.

Provide the client context and the boundaries. A new assistant who does not understand the client will ask the same question repeatedly. Ask whether a new reviewer could act on the record without a conversation. Keep the original note beside the corrected version. The client should know who is handling the question and when to expect an answer. Keep the source link with the task so the next reviewer can check it.

Choose a real task with a clear deliverable and a reviewer. Send the brief and the example. Record the feedback and the next step. Keep the evidence with the record rather than in a separate log. Keep the source link with the task so the next reviewer can check it. The client should know who is handling the question and when to expect an answer.

Do not use shadowing as the only task. The assistant should produce something the reviewer can inspect. Keep the boundary visible in the place where the work is assigned. Use the same format for every handover so the next reader can scan it. A short note with the requester and the next action is easier to use. The handoff should say what the next person may decide without asking.

At the end of the week, record whether the assistant is ready for independent work, ready with review, or not yet ready. Name the evidence and the next review date. Update the template when the same question appears twice. Use the same format for every handover so the next reader can scan it. Keep the source link with the task so the next reviewer can check it. A short note with the requester and the next action is easier to use.

If the assistant is not ready, write the specific gap. Do not extend the week without a reason. Keep the original note beside the corrected version. Record the date and the source so the next reviewer can repeat the check. The assistant should record the owner and the date before the next shift. Test the brief on one real task before applying it to the whole role.

Ask the assistant what was missing. Update the checklist and the first-task brief. A week that improves after each hire is more useful than a perfect template. Update the template when the same question appears twice. The assistant should record the owner and the date before the next shift.

For the support model, review the [services page](/services) and the scope it describes. Use the [contact page](/contact-us) when the decision needs a written boundary. The [U.S. Small Business Administration](https://www.sba.gov/business-guide/manage-your-business/manage-your-finances) publishes public guidance on documenting recurring work. Keep the note with the task so the next reviewer can find it. The handoff should say what the next person may decide without asking. A short note with the requester and the next action is easier to use.