You want to know what to actually do in the first month so this does not quietly go wrong. Here is the short version: one narrow task in week one with daily correction, the same task widened in week two, a second task once the first is steady, and a real review at day 30 that sets the shape of month two.
The engagement starts on an initial three-month contract, then moves to month to month. Three months is the runway you would give a new local hire to learn your systems, your clients and your standards, and it stops everyone treating the first few weeks as an audition.
What the first 30 days is actually for
It is not a trial period. It is the month in which your process moves out of your head and into someone else's, and that is the whole job.
Our guide on why offshore hires fail names five causes, four of them decided by the business before the person starts: the process only ever existed in someone's head, the first task was the wrong one, nobody gave feedback early, and the hire was isolated. The fifth is a brief we should have pushed back on, and that one is ours. Every week below answers one of them.
Be honest about the arc. On a narrow, rule-bound first task, useful work usually appears inside the first fortnight. A full role with judgement in it takes until month two or three, the same as any hire. Anyone promising day-one productivity is describing a task, not a role.
Your side of the deal is roughly fifteen minutes a day for the first fortnight, then about thirty minutes a week. Less than a local hire, because there is no office overhead. Not zero.
The week before day one
Five things, none of which take long. All get skipped by businesses that then wonder why week two was rough.
Write the process down, badly. A rough list of the steps, the ambiguous cases and how you decide them. It does not need to be good. Writing it is what shows you how much was never written, and that hour is the highest-return time you will spend on this hire.
Create named accounts with scoped access. Their own login in every system, on the permission level the role needs. Never a shared password, never your owner account, and nothing touching banking, payment authorisation or trust accounts. They prepare, you release.
Pick a first task that is narrow and checkable. Not the job. One task where right and wrong are visible immediately: reconciliations, claim preparation, product listings, take-offs on jobs you have already priced. Choosing badly here is one of the most common ways a first month goes sideways, so read the tasks worth handing over first.
Book the daily fifteen minutes now. Ten working days of it, in the calendar, before they start. If you cannot find that time, move the start date.
Write down the escalation rule. What they do when unsure, who they ask, and an explicit line saying that asking is the expected answer rather than a failure. Reluctance to say "I do not understand" to someone senior is real, and the fix is to make questions obviously welcome in writing.
One more thing before you grant access. Some work cannot go offshore however capable the person is, and the line usually sits at the advice, the sign-off and the registration, not at the preparation underneath them. What you cannot delegate maps it profession by profession, and some of that boundary is state law rather than federal, so check the position in your own state. Privacy obligations travel with the data too: if your organisation is covered by the Privacy Act 1988 (Cth), Australian Privacy Principle 8 sets conditions on disclosing personal information to overseas recipients. Read it before you grant access, not after.
Week one: one task, corrected out loud
Days one and two, they watch you do the task and write down what they see. They learn it, and you find out your process has steps that were never documented. Have them produce the written version and you correct that, rather than the reverse.
Days three to five, they do the work and you review every piece of it. Out loud, in the moment, plainly. If the date format is wrong, say the date format is wrong. This is the highest-value thing you will do all month, and the corrections are the training.
On day five, ask two direct questions: what is unclear, and what are you guessing at. New starters rarely volunteer this. Whatever they name is a gap in your documentation, not a gap in them.
The failure mode this week is politeness. Work comes back nearly right, you are busy, you do not want to seem harsh on someone new, so you quietly fix it. Ten repetitions later they believe their work is fine and you have decided the hire is not working.
Week two: same task, more of it
Resist the urge to add anything. Same work, wider scope, still reviewed daily but faster. Competence on a rule-bound task should be visible by about day eight. If it is not, look at the brief before the person: a task that turns out to need your judgement was never a week-one task.
This is also the week to fix isolation, the easiest cause to miss because nothing about it looks like a problem at the time. Put them in the team channel rather than on the end of an email chain. Introduce them, in writing and with your backing, to the people they will need to chase. Explain what the business is trying to do and why this work matters. Someone with no context cannot make a good judgement call, only a literal one, and then you complain they were not proactive.
By day fourteen you should be reviewing a sample plus anything they have flagged, not everything. Keep the daily call but let it shorten.
The second task, and the first judgement call
Add the second task once the first is genuinely steady, which is usually around day ten. Adding it in week one is how both end up done approximately.
Pick it deliberately. The natural next step is the work sitting either side of the first in your workflow, where the context already exists. If the first task was invoice coding, the second is supplier queries. If it was claim preparation, the second is chasing the rejections. Handing over your inbox is a worked example of that sequencing.
Week three is also when the first genuine judgement call arrives, usually as a question you did not anticipate. Answer it properly, then write the answer into the process document they have been maintaining since week one. Do that a handful of times and you have something no local hire ever left behind: a written version of how you actually decide things.
Watch for the opposite failure. If nothing has been escalated in three weeks, someone is guessing and hoping.
Week four: the review that decides month two
Book thirty minutes at day 30 and treat it as a real review, not a friendly catch-up. Three questions do most of the work.
- What is genuinely off your desk now, and what did you quietly take back without saying so?
- What still comes back wrong, and is that a documentation gap or a training gap?
- What are they still guessing at?
Then set month two out loud: what they own, what they prepare for your review, and what is not theirs yet. Write it down, because "you are doing great, keep going" is not a scope.
The initial three-month term exists so that day 30 is a checkpoint rather than a verdict. A month is long enough to see whether someone can follow a documented process. It is not long enough for anyone to have learned your business, and treating it as though it were is how good hires get talked out the door early. After that the engagement runs month to month, with no exit penalties at any point.
If it is not working at day 30, say so to us before you say it to anyone else. Most problems in the first month turn out to be an unclear brief or a task that needed judgement too early, and our HR manager will work through it with you and the team member. Where it genuinely is the wrong person, the replacement costs nothing and we do the awkward part. That is the fifth cause, the one we own, and we would rather have the hard conversation in month one than read a resignation in month three.
Where to start
If you already have a start date, block out the daily fifteen minutes and write the process down this week. Those two do more than everything else here combined. The day-by-day onboarding guide goes deeper on the first fortnight.
If you are still deciding, how it works covers what happens between the first call and day one, including who carries the recruitment and the risk. When you are ready, book a discovery call and bring the task you would hand over first. We will tell you on the call if it is the wrong one.
This is general information, not legal or financial advice. Privacy, professional registration and delegation obligations depend on your profession and, for some work, on the state or territory you operate in. Check your position with your regulator or adviser before handing work over.
The hire this plan is written for
Everything above assumes there is someone on the other end of the daily fifteen minutes. What we would put in place is one full-time dedicated team member, hired in the Philippines on your behalf and scoped to a single narrow first task rather than a whole role. The process document and the named accounts are yours to have ready before they start — that week is what month one runs on.
- Does the one narrow, rule-bound first task — reconciliations, claim preparation, product listings, take-offs on jobs you have already priced — and puts every piece in front of you for review through week one.
- Writes and maintains the process document: the version they produce from watching you do the task, corrected by you, then updated every time you answer a judgement call they could not have anticipated.
- Works to your written escalation rule, naming what they are unsure of rather than guessing, and answers the two day-five questions straight — what is unclear, and what they are guessing at.
- Widens the same task through week two rather than taking anything new on, then picks up a second task once the first is genuinely steady — around day ten, and usually the work sitting either side of it in your workflow.
- Prepares and never releases: work assembled and queued to your standard, with the payment, the authorisation and the sign-off left on your side of the line.
- The week before day one: the rough process written down, the named accounts created, and ten working days of the daily fifteen minutes in the calendar. Nobody can do that part for you.
- The daily fifteen minutes for the first fortnight and the thirty minutes a week after it. That time is the training, and it cannot be handed to anyone else.
- The correction itself, said plainly and on the day. Quietly fixing near-right work ten times is how a workable hire gets written off in month two.
- Anything that moves money or carries a signature: banking logins, payment authorisation, trust account access, and any sign-off your licence or registration attaches to you personally.
Frequently asked questions
How long does it take to hire an offshore virtual assistant?
Do offshore staff work Australian hours?
Do I have to train an offshore virtual assistant?
What system access should I give a new offshore hire?
Do I have to tell my clients my work is done offshore?
What if my offshore hire isn't working out after a month?
- Privacy Act 1988 (Cth), Schedule 1, Australian Privacy Principle 8 — cross-border disclosure of personal information — The conditions that apply before personal information is disclosed to an overseas recipient, which is why the privacy check belongs before you grant access
- Office of the Australian Information Commissioner — Australian Privacy Principles — What the Australian Privacy Principles require in practice when an offshore team member will handle personal information
- StaffingSolutions.io, How it works — The initial three-month contract moving to month to month with no exit penalties, the reference-checked shortlist you interview and select from, and who carries the recruitment and the risk between the first call and day one
- StaffingSolutions.io, Why offshore hires fail — The five causes of a failed offshore hire — four of them decided by the business before the person starts — and why isolation and unwelcome questions are so easy to miss
- StaffingSolutions.io, How to onboard a virtual assistant (day-by-day guide) — The first-fortnight timings used here: competence visible by about day eight, the second task at day ten, spot-checking by day fourteen, and what access to grant and withhold
- StaffingSolutions.io, What you cannot delegate offshore — Where the boundary sits — at the advice, the sign-off and the registration rather than the preparation underneath — and which parts of it are state law rather than federal
Alfie is a natural facilitator with a passion for building meaningful relationships. A true people person, he thrives on creating genuine connections and bringing people and businesses together, and he excels at fostering collaboration and teamwork. At StaffingSolutions.io he is usually the first person you speak to: he maps the role, writes the brief the recruiters work from, and stays on the account long after the placement.
Meet the team