How to onboard Indonesian remote workers (7-day checklist, 2026)

Day -7 (one week before start) is contract execution day. The Indonesian employment contract (PKWT for fixed-term, PKWTT for permanent) is signed in Indonesian, in writing, and counter-signed by the local entity (or EOR). The NDA, IP assignment, and confidentiality clauses are bundled with the employment contract and signed together: Indonesian law treats employee IP as belonging to the employer by default, but explicit assignment is best practice for cross-border clients.

Statutory registration follows contract execution. The local entity registers the worker with BPJS Kesehatan (health) and BPJS Ketenagakerjaan (employment) within 14 days of contract start, runs the PPh 21 tax registration (e-NPWP, e-SPT), and enrolls the worker in the company payroll system. THR accrual and severance accrual are computed from the contract start date and booked monthly on the local entity's books.

Deliverables on day -7: signed PKWT/PKWTT (Bahasa Indonesia, signed by both parties), signed NDA + IP assignment, signed data-processing agreement (UU PDP 2022 compliance), BPJS registration receipt, NPWP confirmation, and the worker's contact information verified (WhatsApp, email, primary bank account). Owner: HR + legal + payroll. Sign-off: VP Operations or equivalent.

Day -5 is hardware and access day. The worker receives a company laptop (typically 14-inch business class, Windows or macOS, 16GB RAM, 512GB SSD) shipped via a courier that supports Indonesian addresses (JNE, SiCepat, AnterAja, or Ninja Xpress). A USB headset, an external monitor, and any required peripherals ship with the laptop. Lead time for tier-1 city delivery is 2–3 days; tier-2 city delivery is 3–5 days.

Account provisioning is parallel. The worker is added to the company SSO (Okta, Azure AD, Google Workspace, JumpCloud), given credentials to the production dashboards (KPI dashboard, time tracking, quality system), and added to the team communication channels (Slack, Microsoft Teams, or Discord). Test logins are verified end-to-end before shipping so the worker can log in immediately on day 1.

Deliverables on day -5: laptop shipped with tracking number, headset and peripherals shipped, SSO + dashboard + communication access provisioned, test login verified, and shipping confirmation sent to the worker. Owner: IT + operations. Sign-off: IT lead + operations manager.

Day -3 is the home setup verification gate. The worker takes photos of their workspace (desk, lighting, no visible distractions), runs a speed test (target: 20 Mbps down / 10 Mbps up, latency under 80 ms to nearest regional server), and confirms power backup (UPS, dual-SIM, or MiFi for redundancy). A short video call is scheduled to walk through the setup live with the operations team.

Common issues caught at this gate: insufficient bandwidth (4G only, no fiber, congested evening hours), noisy environment (kids, roommates, street noise), unstable power (PLN outages in some regions), and inadequate desk/ergonomics (kitchen table, bed). For workers in rural or tier-3 locations, the home setup is the single biggest risk to ramp; many programs require tier-1 or tier-2 city residence for that reason.

The 60-second home setup checklist (mirrored from Zipang's 5-gate funnel): (1) stable desk and chair at proper height, (2) wired or strong WiFi connection meeting bandwidth minimum, (3) quiet environment for voice work or video calls, (4) backup power (UPS, dual-SIM, or MiFi), (5) lighting for video calls (no backlight), (6) no visible personal data on screen during screen-share. Deliverable: signed home setup attestation, photos, and speed test results uploaded to the worker's profile. Owner: operations. Sign-off: operations supervisor.

Day -1 is the kickoff call. A 60–90 minute video call covers: company overview, role expectations, KPI framework, communication norms (Slack channels, response time SLAs, weekly 1:1 cadence), shift schedule, time-off policy, escalation paths, and a Q&A. The worker is introduced to the direct supervisor, the team lead, the QA lead, and 1–2 peers. The call is recorded (with consent) for the worker to re-watch.

The expectations alignment document is sent after the call. It covers: (1) daily throughput target for week 1, (2) accuracy target for week 1, (3) response time SLA for the queue, (4) escalation path for ambiguous cases, (5) weekly 1:1 schedule, (6) on-call or weekend rotation expectations, (7) leave and THR policy. The worker acknowledges receipt in writing.

The kickoff is the single biggest retention lever in week 1. Workers who report a 'clear' or 'very clear' kickoff show 12-month retention of 88%+; workers who report an 'unclear' kickoff show 50–60% retention regardless of role. The investment in a structured kickoff is operationally cheap and pays back in reduced attrition.

Day 1 is live training day. The worker attends a 4–6 hour training session (typically split morning and afternoon) covering: SOP walkthrough, tooling demo, sample cases, edge case discussion, and a written assessment. The training is led by the team lead or a senior operator, with the QA lead on call for clarifications.

After training, the worker takes a graded assessment. For customer support, this is a written test of 20–30 sample cases scored on accuracy, tone, and SOP compliance. For data entry, it is a timed input test (e.g., 100 records) scored on accuracy and throughput. For AI annotation, it is a rubric-scored test on a calibration batch. The pass threshold is typically 80%+ for week 1; the test is graded within 24 hours and feedback is sent by end of day 1.

Day 1 also includes a 'supervised first shift', a 2–4 hour window where the worker handles real production traffic under direct supervision (1:1 pairing with a senior operator). This is the test that 'is the worker actually ready' in a way that a written assessment does not measure. The output of the supervised shift is QA-reviewed and counts toward the day-1 throughput target.

Days 2 and 3 are shadow shifts. The worker handles production traffic with a senior operator on standby for escalation. Target throughput is 50–70% of full production by end of day 2, 70–80% by end of day 3. The shadow operator provides real-time coaching on edge cases, escalation triggers, and tooling shortcuts.

Tool fluency is the focus on day 2. The worker is expected to be fully proficient in the production tool (Zendesk, Intercom, HubSpot, Salesforce, Labelbox, Scale, custom in-house) by end of day 2. Common keyboard shortcuts, macro insertion, internal search, and the QA dashboard are all in scope. A 30-minute tool-fluency quiz on day 3 confirms the worker's comfort with the stack.

By end of day 3, the worker should be at 70–80% of full production throughput with 90%+ accuracy on QA-reviewed samples. The operations supervisor reviews the day-3 numbers and either (a) progresses the worker to production ramp on day 4, or (b) extends shadow shifts by 1 day. The 1-day extension is rare (5–10% of cases) and is paired with a 1:1 coaching block.

Days 4 to 7 are production ramp. The worker handles unsupervised production traffic at progressively higher throughput targets: day 4 at 80%, day 5 at 85%, day 6 at 90%, day 7 at 95–100% of full production. Each day's output is QA-sampled (typically 10–20% of throughput) and scored on accuracy, tone, SOP compliance, and response time.

The weekly 1:1 is scheduled for day 5 or 6. The supervisor and worker review the week-1 numbers, discuss any blockers, set the week-2 targets, and document the 30-day plan. The 30-day plan covers the formal end-of-probation review (typically at day 30, sometimes day 60 or 90) and the criteria for converting the worker from probation to ongoing status.

By end of day 7, the worker should be at 95–100% of full production throughput with 90%+ accuracy. The week-1 KPI is met. The 30-day reserve in the operator's invoice covers any day-1 to day-30 underperformance with a free replacement; the 90-day reserve covers day-31 to day-90. After day 90, the worker is in steady-state, and the program has a clear baseline for the next 6–12 months of operation.

The week-1 KPI framework is short. Five numbers matter: (1) throughput, units of production per shift (tickets resolved, records entered, annotations completed), (2) accuracy: QA-sampled score on a 0–100% scale, (3) response time, time to first response / time to resolution for support roles, (4) attendance, % of scheduled shifts actually worked, (5) escalation rate, % of cases escalated to senior operator or supervisor.

Targets for week 1: throughput 80%+ of full production, accuracy 85–90%, response time within SLA, attendance 95%+, escalation rate 10–15% (declining to 5–8% by week 4). The supervisor reviews these daily during week 1; the operations manager reviews them weekly; the client sees a weekly rollup starting in week 2.

KPI finalization happens in the week-1 1:1. The supervisor and worker agree on the steady-state targets for weeks 2–4 and for the 30-day review. Documented targets make underperformance visible and operational, not subjective. The same KPI framework rolls forward month-to-month with annual escalation tied to cost-of-living and skill-tier movement.

The client manager briefing is a 30–45 minute call in the first week of the worker's ramp. The briefing covers: (1) the worker's background, prior roles, and English band, (2) the supervisor and team structure, (3) the week-1 KPI numbers and how they compare to targets, (4) the 30-day plan and 30-day review criteria, (5) escalation paths and on-call expectations, (6) cultural and time-zone context, (7) any specific client-side processes the worker needs to follow.

The briefing has three goals. First, set realistic expectations: ramp takes 2–6 weeks to full production; week-1 numbers are not steady-state. Second, give the client a clear escalation path: which supervisor, which email, which Slack channel, what response time SLA. Third, surface any client-side friction early: tooling the client owns, dashboard access the client provisions, communication norms the client expects.

For multi-seat programs (10+ workers ramping in parallel), the briefing becomes a weekly client call with a rollup deck: week-1 KPI by worker, week-1 issues and resolutions, week-2 plan, monthly rollup trending toward steady-state. The same deck format is used in QBR (quarterly business reviews) for the first 6 months, then simplified to a monthly rollup.