What to delegate to a virtual assistant first (and what to keep)

Start with work that repeats, follows clear rules and can be checked before it affects a customer or your money. Inbox triage, diary holds and document chasing are usually easier first handovers than payment approval or tax correspondence. At Ramp Remote, we recommend defining a small, complete responsibility before expanding the role.

The aim is not to remove every administrative task from your day at once. It is to create a reliable handover that both people understand. This guide gives you a task-sorting method, a first-fortnight sequence and a practical way to decide when checking can become less frequent. The sequence is an example you can adapt, not a promise of results within a fixed period.

Which tasks are worth handing to a virtual assistant first?

Test each task with four questions. Does it repeat often enough to justify a process? Can you explain the rules in writing? Can a mistake be corrected before it causes material harm? Does the final decision require your judgement, authority or professional qualifications? A task does not become suitable simply because you dislike doing it.

Take appointment coordination. An assistant can collect availability and place a provisional hold using written rules. Accepting a meeting that displaces an important customer visit may need your decision. Separate those steps instead of keeping the entire task or handing it over without limits. The same distinction applies to invoices: preparing a draft is different from approving a payment.

“Never” describes an unsafe method, not a judgement about the person's ability. A qualified or properly authorised employee may take on more responsibility through a different role and control process. For a first administrative hire, keep the boundaries narrow enough that you can explain and verify them.

How do you audit your week to find work you can delegate?

Write down the tasks you actually touch for several working days. Record the trigger, the output, the system used and what makes the task difficult. “Admin” is too broad. “Collect missing purchase-order numbers before the bookkeeper raises invoices” describes something that can be assigned, taught and checked.

Include interruptions as well as planned work. A customer asking for a copy invoice, a supplier requesting an address and a colleague needing a meeting moved may each be small, but they belong to identifiable workflows. Group similar requests so the assistant can manage a queue rather than receiving disconnected instructions through several chat channels.

For each task, note whether it requires access to confidential information, a decision from another person or a particular working hour. Record your own observed frequency rather than guessing an industry average. Use a 15-minute audit of how much of your week is admin as a starting framework, then expand the record if one week is unusually quiet or busy.

Choose a first bundle with a common outcome. For example: organise incoming enquiries, prepare replies and maintain a list of questions for the owner. That is easier to manage than combining inbox triage, payroll, social media and purchasing in the first assignment. The bundle should have a clear finish point each day.

What should a first-time owner hand over in week one?

Begin with observation and preparation. Show the assistant a completed example, explain the exceptions and ask them to walk through their understanding. You are checking the instructions as much as the person. A question at this stage is useful evidence that an assumption needs to be made explicit.

1. First working day: confirm access, working hours, communication channels and a sample task. Use a small set of records you can inspect together.

2. Next stage: have the assistant label or sort a queue and explain the proposed next actions. Keep outgoing messages as drafts.

3. Later in week one: add diary holds, document requests or CRM updates where the rules and review process are clear.

4. Week two: consider limited routine sending or approved data entry after reviewing the initial work. Keep exceptions and financial approval with the responsible person.

This is a suggested order, not a deadline for increasing authority. If a process is unclear, stay at the preparation stage. For bill entry in Xero or MYOB, a bookkeeper should specify the fields, supporting evidence and review route. Do not use an administrative handover to bypass accounting controls or assume that software access proves accounting competence.

Keep a short task board in Asana, Trello or ClickUp, or use a simple shared list if that is what your team already understands. Each item needs an owner, a due date and a status. “Waiting” should identify the person or information being waited for. A growing list of unexplained waiting items is a signal to improve the process.

What should you keep doing yourself?

Keep decisions that set commercial policy, approve money or require professional judgement with the responsible owner or qualified adviser. An assistant can assemble information and flag deadlines without deciding the answer. For example, they can organise the documents attached to an ATO letter and alert you to its due date; that is different from responding as your tax representative.

The ATO distinguishes primary and authorised contacts. Inland Revenue also has a formal process for access as a nominated person. Being hired as an assistant does not itself establish either authority. Ask your accountant which responsibilities and access, if any, are appropriate for the specific work.

Payment approval and changes to supplier bank details deserve a separate verification process. Keep approval limits explicit and avoid combining preparation, verification and payment release in one unchecked handover. If the owner is unavailable, nominate a suitable backup approver rather than asking the assistant to guess.

Also retain decisions about sensitive complaints, employment matters and legal commitments unless a properly qualified and authorised person is responsible. The assistant can help organise the workflow around those decisions. That support is useful without presenting the role as a replacement for professional advice.

How do you hand over a task so it comes back right?

Use a short handover card with the goal, trigger, inputs, steps, example, deadline and approval rule. Add a definition of done. “Update the CRM” leaves room for interpretation; “record the customer's requested appointment date, add the source email and assign the follow-up to the account owner” can be checked.

Record a Loom walkthrough if showing the screen is clearer than writing several paragraphs. Pair the recording with a short written checklist so the assistant does not need to replay it for every task. Use approved sample information and avoid recording passwords or unrelated personal details. See writing SOPs and Loom walkthroughs for a reusable structure.

Ask the assistant to complete one example while explaining the choices. If you correct something, update the instruction or example at the same time. Otherwise the correction remains trapped in a chat message and may be missed by the next person. Keep one current version of the process with a clear owner.

How do you share logins and approvals without losing control?

Prefer individual user accounts and appropriate roles. Xero's role guidance explains how access differs between roles, including Standard, Draft sales and purchases, and Viewer. Have the subscriber or authorised administrator invite the assistant and choose permissions for the actual task. View-only access still exposes information; it does not mean the information is harmless to share.

Google Workspace and Microsoft 365 provide delegation options for supported accounts. Gmail delegation gives email access without sharing the owner's password, while Outlook delegate access depends on the account and permissions. Ask your administrator to configure access and test it using the assistant's own account. Document the business limits as well as the technical permissions.

For systems that genuinely require shared credentials, use an approved shared password manager such as 1Password and review who can access the item. A password manager is not a substitute for least-privilege roles where those exist. Keep personal identity accounts and payment approvals outside the general handover.

Apply the same thinking to HubSpot or Pipedrive: decide which records the assistant needs, what they may change and whether exporting data is necessary. Record access when it is granted and remove it when the responsibility ends. Test a normal task and a task the assistant should not be permitted to complete before relying on the setup.

When is a task ready to move from checked to trusted?

Look for consistent handling of both normal work and exceptions. The assistant should know what good work looks like, identify missing information and escalate outside their limits. A quiet chat channel is not enough evidence; check completed examples and the unresolved queue.

Reduce checking gradually for a specific task, not for the whole role at once. Keep periodic sampling and an easy way to ask questions. Review the process when a tool, customer requirement or policy changes. Increasing trust should make the work clearer, not remove accountability.

Use 60 tasks a virtual assistant does, by business type to expand a well-run role, and compare what a virtual assistant costs in Australia and NZ once the scope is defined. If you are also weighing automation, read AI versus a human assistant; for the first inbox handover, see how to get your inbox under control.

Take your shortlist of responsibilities to Ramp Remote and explore a virtual assistant for Australian and NZ businesses. Browse anonymised Philippines-based candidates in Talent Space, then discuss the experience, working hours and approval boundaries your first handover requires.