“Keep the important work here and send the admin offshore” sounds straightforward until someone must decide what counts as important. Booking an appointment may be routine; promising a completion date that the business cannot meet is a commercial decision. Preparing a technical document and approving it are also different tasks.
Start with the work itself. Some activities require physical attendance in Australia. Others require a particular qualification, business authority or relationship context. Many can be performed remotely by a capable, properly supported person.
A Philippines-based VA can own substantial operational work. An Australian address does not establish expertise, and an offshore address does not prevent it. This framework helps decide which steps belong where without relying on those assumptions.
Split the outcome before allocating the role
Choose one customer outcome, such as a complete installation handover. List the steps from gathering records through checking, resolving exceptions, approving the result and communicating it.
Describe each step as an observable action. “Prepare the equipment schedule from approved drawings” is more useful than “help the designer”. “Confirm available appointment options under the booking rules” is clearer than “handle customers”.
Then identify what must be present for the step to succeed: information, skills, physical access, authority and a way to resolve uncertainty. This usually reveals that a single outcome contains work suitable for several people.
Use your actual team members' capabilities when assigning those steps. If the required expertise is absent, the answer is to obtain it or change the task, rather than assume a local manager can approve it.
Apply four tests to each step
Physical presence. Must someone inspect, install, meet or handle something at a particular place? Keep that activity with an appropriately qualified person who can attend. Remote preparation and coordination may still support it.
Required authority. Does the task require a licence, accreditation, professional judgement, signature or commercial approval? Identify the actual requirement and the person authorised to fulfil it. Location alone does not answer this question.
Information and access. Can the task be completed using the approved information and access arrangements? Resolve privacy, security and contractual restrictions before allocating live records. An operational preference cannot override a binding restriction.
Context and consequences. How much unwritten knowledge does the decision require, and what happens if it is wrong? Retain a step with its current owner while the necessary context is being documented and tested. Revisit that choice as another person develops the required capability.
These are discussion tests, not a numerical outsourcing score. Record the reason for each decision so temporary training limits are distinguishable from continuing physical or professional requirements.
Work through a solar handover example
The table below is a proposed division of work for a hypothetical solar business. It does not replace the requirements applying to a particular installation.
| Step | Possible allocation | Condition before the work proceeds |
|---|---|---|
| Obtain installation evidence | Site team captures it; remote coordinator tracks missing items. | Evidence comes from the actual work and meets applicable requirements. |
| Prepare the review pack | Trained VA organises records and flags inconsistencies. | Current source documents, a checklist and clear version control are available. |
| Resolve a technical discrepancy | Responsible qualified designer or installer. | The person has the relevant competence and authority; the VA does not guess the answer. |
| Communicate a verified milestone | Trained customer coordinator, local or remote. | The milestone is confirmed and the message stays within delegated authority. |
| Agree an exceptional commercial remedy | The business's authorised decision owner. | The facts, options and applicable obligations have been considered. |
For rooftop solar systems seeking STCs, the Clean Energy Regulator sets accreditation requirements for designers and installers, licence requirements for installers and on-site attendance requirements. Those responsibilities cannot be replaced by an administrative completeness check. Read the CER's installer and designer requirements.
Our PV design support guide explains how preparation, review and sign-off fit together. The point is to free specialists from avoidable document chasing while keeping their substantive responsibilities clear.
Keep relationship ownership while delegating useful contact
An account owner can retain responsibility for a key relationship while a VA handles agreed updates, appointment coordination and information requests. Customers need accurate answers and continuity; they do not benefit from every message waiting for the owner.
Write down the boundary. A coordinator might confirm standard meeting times and explain approved service information. A disputed commitment, unusual scope change or request beyond their authority goes to the named owner with a clear decision requested.
Give the owner a response expectation and a backup. Otherwise the business transfers the chasing work offshore but leaves the same decision bottleneck untouched. The hybrid team responsibility guide provides a structure for those handovers.
Check information handling separately from customer-service capability. For organisations subject to the Australian Privacy Principles, overseas access can raise cross-border disclosure questions. OAIC guidance says providing personal information to an overseas contractor is a disclosure in most circumstances. It may instead be a use within the entity's effective control in limited circumstances. Assess the actual arrangement before sharing personal information; a confidentiality clause alone is not a complete assessment. OAIC: cross-border disclosure guidance.
Test one transfer against a clear finish point
Select a bounded step with a reversible training path. Give the proposed owner worked examples, approved tools and a way to ask questions. Begin with representative training cases, including one that must stop for another person's decision.
Assess the resulting work against the same standard used by the current team. Include clarification, checking and correction time. If the local specialist must redo the whole task, investigate whether the instructions, source quality or skills are sufficient before increasing volume.
Review the waiting time for local decisions as well as the remote worker's handling time. Delegation cannot increase completed work if the final reviewer remains unavailable.
Record the allocation and revisit the reasons
Keep a short decision record for each transferred step: expected output, owner, required capability, permitted actions, information access, stopping points and backup. Add the reason any part remains local and the event that should trigger review.
That event might be a qualification change, a new service, successful training or different customer requirements. Change the allocation only after checking the conditions again.
Talk to Nexus about mapping one workflow into practical roles for your Australian team, Philippines-based support and the specialists who must own particular decisions.
