The installation is booked, but the job file is missing a customer detail. Someone has followed up, although nobody knows whether the latest reply reached the right person. Meanwhile, your operations manager is answering another question about a different job that looks almost identical.
That is a useful example of solar administration overload: work keeps moving between people without moving closer to completion.
Adding a virtual assistant can help with capacity. Getting the workflow clear makes that capacity useful. For an Australian solar business considering support from the Philippines, the starting point should be a practical question: what needs to happen next on each job, and who is allowed to do it?
The following framework is an operational recommendation. Check the current requirements for your network, state and incentive program when applying it.
Start with the handoffs
Review a small sample of recent jobs. Include smoothly completed jobs and jobs that required repeated follow-up. For each one, write down where it waited, which information was missing and who eventually resolved the issue.
You are looking for repeatable friction: incomplete sales notes, unclear document ownership, unrecorded customer promises or a status that nobody updated after a phone call.
Turn those observations into a shared job tracker. Every open job should have a current stage, a named owner, a next action, a due date and a recorded blocker. Keep the tracker connected to the underlying evidence so people can verify a status rather than rely on somebody remembering the conversation.
Separate preparation from professional responsibility
A support person can organise information, chase an outstanding document and flag a mismatch. That is different from making a design decision or certifying work.
For systems seeking small-scale technology certificates, the Clean Energy Regulator sets accreditation requirements for designers and installers, alongside applicable licensing and other requirements. The responsible professionals must remain involved in the work that requires their qualifications. Clean Energy Regulator: rooftop solar installers and designers.
Create a responsibility table before you outsource. List who prepares the file, who reviews it, who can approve a change and who signs any required declaration. For PV design support, agree the permissible support scope with the responsible accredited designer. A remote team member should have a clear route to raise a technical question instead of guessing.
Give each stage a clear completion test
“Admin done” tells the next person very little. A useful completion test describes what is ready and what evidence supports it.
For a sales handover, your test might be that the agreed scope, customer details, available site information and unresolved questions are recorded. For document review, it might be that the file has been checked against the applicable checklist and every missing item has an owner.
Keep network approvals visible as their own stage. Energex, for example, tells installers to verify customer details and obtain approval before installation. Its requirements are a useful reason to track the application and its outcome explicitly; other networks need their own workflow. Energex: connection information for installers.
Build the evidence pack as the job progresses
Avoid making “collect everything later” your normal process. Decide when each required record becomes available and who will place it in the job file.
The CER requires the relevant documentation to be completed and signed before STCs are created. It can also request required documents for up to five years after certificate creation. That makes a retrievable evidence pack part of ongoing operations. Clean Energy Regulator: creating STCs.
Give your support team a document index, consistent file names and an exception queue. Their role is to identify what is missing and route it to the right person. A blank field should remain an unresolved issue until a reliable source supplies the answer.
Keep distinct milestones separate. An installation record, a network approval, a metering update and a certificate claim are different records. Your dashboard should show the particular step that still needs attention.
Choose a small first workload
An offshore administrator's first assignment should have a defined beginning and end. For example: review tomorrow's proposed handovers, compare each file with the approved checklist, and report missing items to the operations coordinator.
Provide completed examples and difficult examples. Explain what a good escalation looks like: the job reference, the missing information, the source already checked and the decision needed.
Start with supervised work. Review a sample together and update the instructions when the same ambiguity appears twice. Expand the workload when the team can complete the existing task consistently and knows when to stop and ask for a decision.
Use automation to reduce chasing
Simple automation can create reminders, flag a missing field or alert an owner when a job has waited too long. AI can help draft an internal summary or a customer update using verified information.
Keep human review where an error could mislead a customer, change a technical decision or affect a claim. Never let a generated answer stand in for missing installation evidence.
Set data access deliberately. For organisations covered by the Australian Privacy Principles, sharing personal information with an overseas contractor can engage cross-border disclosure obligations. Review the applicable requirements alongside your access controls and service arrangements. OAIC: APP 8 guidance.
Measure whether the queue improves
Track a few measures before changing the process: the number of jobs awaiting information, their age, first-pass file completeness and the number of times a file returns for correction.
Measure internal preparation time separately from time waiting on customers, networks or other external parties. Otherwise, a team can appear slow because a delay sits outside its control.
Compare similar work over a sensible period. Count review time and rework as part of the cost. A meaningful improvement could be fewer repeat questions or a more predictable close-out queue; it does not need an extravagant productivity claim.
Start with the bottleneck that consumes the most attention. Give it a clear owner, a small checklist and a visible finish line. That gives local specialists, offshore support and automation a shared process they can improve together.
Planning a solar support team? Bring a sample of your current workflow and identify the first handoff worth improving.
