NORTHLINE | Remote Team Onboarding Guide

Prompt

Create an editable English onboarding guide for a fictional remote team: an onboarding timeline, async collaboration norms, the account access request process, first-week tasks and a 30-day review. Use clear tables and a dark blue and light cyan palette, and note that the sample content should be adapted to actual policies.

Result

docx
NORTHLINE | Remote Team Onboarding Guide

Version 1.0 · Last updated: [insert date] · Next review: [insert date]

1. About this guide

Northline Collective is a fictional, remote-first product team. This guide is the single starting point for a new joiner's first 30 days: the onboarding timeline, how we work asynchronously, how account access is requested, the first-week tasks and the 30-day review.

How to use this guide

Managers: copy this document, replace every [bracketed] field with real names, dates and tool links, and share it with the joiner at least three business days before Day 1.

New joiners: work through Section 5 in week 1 and bring the Section 6 self-assessment to the 30-day review.

People Ops: keep Sections 2 and 4 aligned with the current handbook, systems list and legal requirements.

Who's who during onboarding

2. Onboarding timeline

The timeline runs from five business days before Day 1 to the Day 90 check-in. Each phase ends with a milestone that must be met before the next phase starts; if it is not met, the manager and joiner agree a revised date in the tracker.

An editable Word document (A4, 10 tables, dark blue #0B2545 + light cyan #9FE3EE / #E8F8FB palette) for a fictional remote-first team, Northline Collective.

What's inside

  1. About this guide — purpose, how to use it, a "who's who" table (manager, buddy, People Ops, IT, department head) and the sample-content callout.
  2. Onboarding timeline — pre-boarding → week 1 → weeks 2–3 → week 4 → Day 30 → Day 60/90, each with focus, owner and exit criteria.
  3. Async collaboration norms — 8 norms (written by default, decision log, one stand-up, overlap windows, meeting hygiene, response times, focus time, escalation) with channel and expected response.
  4. Account access request process — 8-step least-privilege flow plus a systems table with access level, route, approver and typical lead time.
  5. First-week tasks — 20-item checklist from pre-boarding through Day 5, with owners and tick boxes.
  6. 30-day review — format, a 7-area review table with evidence and lead, self-assessment prompts, possible outcomes.
  7. Keeping this guide current — review cycle and a change-log table.

Every timeline, tool, approver and lead time is labelled as sample content, with the adapt note in the intro callout, a lead-time callout and the page footer. Fields to replace are in [brackets].

Verified: all six requested sections present, 10 tables with header shading, palette hex values confirmed in the file, 20/20 checkboxes, all tables fit the 17 cm text block, footer on every page. Note: no DOCX renderer was available in the cloud Computer, so I checked structure and colour values rather than a pixel preview — the first open in Word or Google Docs is the visual check.

How it was made

Mode
Document
Template
Policy draft
Try this prompt