The First 30 Days With Your Indonesian Hire: A Week-by-Week Onboarding Plan

People quit in month two because month one was chaos. A week-by-week plan for onboarding an Indonesian remote hire, with the local details built in.

Published September 3, 20266 min read

Calendar page showing upcoming onboarding date.

One of the largest pain threads we have seen from employers of remote workers, 358 comments deep, is about virtual assistants who do not stick around. Owners hire, train for a few weeks, start to relax, and the person quits. The thread reads like a mystery, but the timing gives it away: almost every departure story traces back to a first month that was chaos. People rarely quit a job in month two because month two went wrong. They quit because month one told them what working for you would be like.

So treat onboarding as a retention decision, made in the first 30 days, mostly by you. Here is a week-by-week plan for onboarding an Indonesian hire, with the Indonesia-specific details woven in where they belong, because a generic onboarding checklist will miss the things that actually cause friction: three time zones, Friday prayers, and a holiday week that empties the country.

Week 1: access, one real task, and the schedule conversation

Day one has two jobs: get them working, and get the schedule agreed in writing.

A desk calendar showing the month's schedule.

Working first. Set up their accounts before their first day (email, your project tool, the software the role lives in), then give them one small, real task within the first 48 hours. Real means it touches actual work: categorise last week’s transactions, draft replies to three genuine customer emails, clean one product listing. A first week spent only reading documents tells your new hire the job is not ready for them. A first week where something they did shipped tells them the opposite.

Then the schedule. This is the conversation most Western employers skip, and it is where month-two resignations are planted. Agree these four items explicitly, and put them in a shared document:

  1. The working window, stated in their local time. Indonesia has three time zones (WIB, WITA, WIT), so “Jakarta time” and “Bali time” are already an hour apart. A window written in your time zone silently drifts into their evening.
  2. Overlap hours, separated from total hours. Decide how many hours you genuinely need them online at the same time as you, and let the rest of their hours sit in their own daytime. Forty total hours with two overlap hours is a sustainable job. Forty hours forced into your business day is a night shift, and night shifts quit. Our guide to Indonesian time zones and overlap planning covers how to pick the window for your region.
  3. Who moves on daylight saving. Indonesia does not observe it, so twice a year your overlap shifts by an hour. Decide now whether they move or you do.
  4. Indonesian public holidays, especially Idul Fitri. Put next year’s dates in your calendar in week one. More on this below, because it is the one that catches employers by surprise.

Two rhythms worth knowing from the start: many Indonesian workers take a midday break for Friday prayers, so avoid planting your standing meeting in Friday’s midday hours, their time. And Idul Fitri (Lebaran) is not a day off, it is the holiday around which the whole year turns. With the official joint-holiday days and travel to family, treat Lebaran week as effectively out of office nationwide, and plan deadlines around it the way you would plan around Christmas week.

Week 2: they write the SOP, you correct it

The standard advice says document your processes before hiring. Almost nobody has, and it turns out the better sequence is the reverse: your new hire documents the process as they learn it, and you correct the document.

Each task you hand over this week, have them write up as they do it: steps, screenshots, where the files live, what to do when something looks wrong. Then you review the write-up and fix what they misunderstood. This does three useful things at once. You find out exactly what they absorbed instead of discovering gaps months later. They learn faster, because writing a process forces the questions reading never surfaces. And by the end of the month you own a real SOP library that survives even if this hire does not.

It also sets a norm that matters more than any single procedure: in this job, confusion gets written down and resolved, instead of nodded along to. That norm is worth a great deal with any new hire in a culture where pushing back on the boss does not come easily by default.

Week 3: first solo cycle, with a written daily handoff

This week, they run a full cycle of the core work without you in the loop during the day: the whole weekly bookkeeping cycle, the inbox end to end, the content calendar for the week.

A cup of coffee and books in a quiet office corner.

Replace the instinct to schedule a daily check-in call with a written daily handoff. At the end of their working day, they post a short note in a shared channel or doc: what got done, what is blocked and on whom, what they will do tomorrow, and any questions. You read it during your own workday and reply in theirs.

The written handoff beats a daily call on every axis that matters here. It leaves a record you can scroll back through when something goes sideways. It costs nobody sleep, which a synchronous call across a 12-hour gap always eventually does. It builds exactly the written-English muscle the role runs on. And it gives you a daily sample of their judgement: after two weeks of handoffs you know whether they flag problems early or bury them, which is the single most predictive thing you can learn in a trial period.

Week 4: the review and the raise path

End the month with a real conversation, not a form. Cover what is going well, what needs to change, and whether the schedule agreed in week one is actually working, because sometimes the overlap window that looked fine on paper is quietly eating their evenings, and they will not raise it unless you ask.

Then talk about the raise path, this month, not after a year. It costs you nothing to say: here is what the next six and twelve months look like if this goes well, here is roughly what growth in this role pays, and THR (the customary religious-holiday bonus, about a month’s pay) is part of how we intend to treat this relationship. Our salary guide gives you the market bands to anchor that conversation honestly. A worker who can see the future of the role has a reason to stay through the inevitable rough patches. A worker who cannot see past next month, and whose first month was chaos, is already reading job posts.

The pattern behind all four weeks

Each week hands over one thing: access and rhythm, then process, then autonomy, then a future. None of it is expensive and all of it is deliberate, which is exactly what the chaotic first month is not. The 358-comment thread is full of employers who did the hiring well and the landing badly.

If you are still at the hiring step, our full guide to hiring a virtual assistant in Indonesia covers posting, screening, and trial tasks, and you can browse Indonesian workers directly when you are ready. Just do not stop planning at the offer letter. The offer gets you a start date; the first 30 days decide whether you are still working together at day 300.

All articles

Ready to hire?

Browse verified Indonesian workers and hire directly. One flat fee, no take-rate, no agency markup.

Onboarding a Virtual Assistant: The First 30 Days · OnlineJobs Indonesia