> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create the onboarding document

> Draft the internal onboarding document with Pi — the client's goals, the access and prework you need, and how you'll work — then review and share it.

The onboarding document is the internal alignment and prework doc you build in Week 1 and share with the client before the kickoff. It captures their goals, the access and prework you need from them, and how you'll work together. It's distinct from the [kickoff document](/sops/create-kickoff-doc), which is the client-facing strategy and timeline. Draft it with Pi, fill in the specifics, get it reviewed, then share it.

## Draft it with Pi

Dump this into Pi, modeled on a previous client's onboarding document:

```text theme={null}
create an onboarding document, modeled on a previous client's. cover:

- points of contact: ours ([your name] — day-to-day, strategy, deliverables) and theirs (day-to-day)
- what we need from them, access this week:
  - Google Search Console — add sam@synscribe.com and raymond@synscribe.com
  - Google Ads — same access
  - CMS (if they publish blogs) — same access
  - GitHub repo — to @boblynlim and @yehjxraymond
  - PostHog, or whichever product analytics they use
  - sales / demo call recordings or transcripts, if any
- how we work: monthly cycles (proposal, their sign-off, then ship), working in their codebase via PRs where possible, and a review at the end of each month
- what we'll do once we have GSC access: pull GSC and run a technical audit, locales especially
- what we'll bring to kickoff: a locale audit, initial keyword candidates, and crawl findings on canonical / hreflang / indexing
```

Pi drafts the document. Review it, fill in the specifics from the sales calls, and add the feature inventory for the client to check; see [Feature inventory sign-off](/sops/feature-inventory-signoff).

## What it should include

<Accordion title="Onboarding document checklist">
  * Points of contact on both sides
  * The client's goals, and what "winning" looks like to them
  * Any product confusion or inaccuracies to correct
  * How we work: monthly cycles, working in the client's codebase via PRs where possible
  * Publishing and compliance workflow: publish directly, or review-before-publish? Any compliant-language rules? See [compliant content](/platform/compliant-content-regulated-industry)
  * Competitors (Direct, Incumbent, Adjacent) for verification
  * The feature inventory for verification and sign-off; ask for images
  * Brand / design guidelines and product docs, if they have them
  * Access: web platform (GitHub / Framer / Webflow / WordPress / …), Google Search Console (add [sam@synscribe.com](mailto:sam@synscribe.com) and [raymond@synscribe.com](mailto:raymond@synscribe.com)), PostHog (or set one up; Mixpanel or another is fine)
</Accordion>

## Review and share

* Send the document to the `internal-<client>` Slack channel for Raymond to review, and revise on his feedback.
* After the onboarding call, share it with the client with full edit access, so they can correct the feature inventory and fill in their side.

**Next:** [Feature inventory sign-off](/sops/feature-inventory-signoff) · [Create the kickoff document](/sops/create-kickoff-doc) · [Month-1 onboarding](/sops/onboarding-month-1)