Written by Kenn, Founder & CEO of NextLevel Growth
Strong onboarding replaces assumptions with shared expectations. It protects the client, the assistant, and the quality of the work.
Confirm the scope
List the tasks included, the tools involved, expected outputs, schedule, and items outside the agreement. Clarify which tasks require approval and which can be completed independently. A written scope makes it easier to discuss new requests without conflict.
Set communication rules
Agree on the main communication channel, normal response window, meeting schedule, time zone, and emergency definition. Decide how decisions are recorded after calls. Consistent communication reduces repeated questions and prevents important instructions from disappearing across several apps.
Handle access safely
Use the client's approved password manager or access-sharing process. Avoid sending passwords through ordinary messages. Request only the permissions required for the assigned work and confirm how access will be removed when the engagement ends. Never copy client data into personal tools without permission.
Build a source of truth
Create an organized workspace for procedures, templates, status, deadlines, and links. Each recurring task should eventually have a short checklist. Keep file names and folders predictable. Documentation allows work to continue even when someone is unavailable.
Review the first week
Schedule an early check-in to discuss priorities, blockers, workload, and quality. Correct misunderstandings before they become habits. End the week with a brief summary of completed work, pending decisions, and recommended next actions.
A practical first-day setup
On the first day, confirm the main contact, working hours, priorities, communication channel, and required accounts. Review one example of completed work so quality expectations are visible. Create a shared task list and record any questions that block progress. Do not request every possible permission immediately. Start with what is needed for the first approved tasks and expand access only when the scope requires it.
Protect both sides
Use written instructions for recurring work and record important approvals. The client should know where files are stored and how access can be removed. The assistant should know which information is confidential and which actions require permission. Do not mix client data with unrelated personal projects. Clear records protect the working relationship when someone forgets a conversation or a responsibility changes.
Report without creating noise
A useful update is short and specific. State what was completed, what is in progress, what is blocked, and what decision is needed. Include links to the relevant files or tasks. Avoid sending many small messages unless the issue is urgent. Agree on a daily or weekly format so the client can understand progress quickly.
Improve the process after two weeks
Review which instructions were unclear, which tasks took longer than expected, and which approvals caused delays. Turn repeated explanations into checklists. Confirm whether the workload still matches the agreement. Suggest improvements carefully and explain the benefit. Good onboarding is not finished after account access is granted. It continues until both sides can work with fewer avoidable questions.