Onboarding guide template
A first-week onboarding checklist in plain Markdown – what to do before day one, accounts on day one, the product on days two and three, a first task, and the people to meet.
Template
The start page of an internal knowledge base in plain Markdown – what the company does, where each kind of doc lives, how decisions are made, and who to ask.
Publishing this from your own stack? See Display for internal docs.
Preview
Owner: People Ops · Last reviewed: 1 October 2026 · Readers: everyone at Fernhill
TL;DR: This Space holds how Fernhill works. Read Your first week on day one. If a page here is wrong, comment on the line or edit it. Every page shows who changed it and when.
Fernhill makes planning software for garden centres and plant nurseries. We are 64 people in Bristol, Leeds and remote across the UK. Our customers run 1,900 sites.
| Folder | What is in it | Who can edit |
|---|---|---|
| Start here | This page, Your first week, the org chart | People Ops |
| How we work | Meeting notes, planning recaps, decision log | Everyone |
| Policies | Expenses, travel, leave, security | People Ops, Finance |
| Teams | One folder for each team's own pages | That team |
team-wiki.md# Fernhill handbook – start here
**Owner:** People Ops · **Last reviewed:** 1 October 2026 · **Readers:** everyone at Fernhill
> **TL;DR:** This Space holds how Fernhill works. Read *Your first week* on day one. If a page here is wrong, comment on the line or edit it. Every page shows who changed it and when.
## What we do
Fernhill makes planning software for garden centres and plant nurseries. We are 64 people in Bristol, Leeds and remote across the UK. Our customers run 1,900 sites.
## Where things live
| Folder | What is in it | Who can edit |
|---|---|---|
| Start here | This page, *Your first week*, the org chart | People Ops |
| How we work | Meeting notes, planning recaps, decision log | Everyone |
| Policies | Expenses, travel, leave, security | People Ops, Finance |
| Teams | One folder for each team's own pages | That team |
## How we decide
1. Write the decision as a doc in the team's folder. Your agent can write the first draft.
2. Share it with the people who must agree. They comment on the lines they question.
3. The owner records the outcome in the *Decision log* with a date.
## Who to ask
- **Payroll, leave, benefits:** Mette K. in People Ops
- **Laptops and accounts:** IT, in the #it-help channel
- **Expenses:** Finance, see the *Expense and travel policy*
- **Anything else:** your manager or your onboarding buddy
The first page a new person opens. It says what the company does, which folder holds which kind of doc, and who can edit each folder. A reader finds the right page in one step instead of asking in chat.
More templates
A first-week onboarding checklist in plain Markdown – what to do before day one, accounts on day one, the product on days two and three, a first task, and the people to meet.
A company policy in plain Markdown – a TL;DR, limits in a table, how to claim, the rules, how to ask for an exception, and a dated change log.
Any agent, any model. Behind your company’s sign-in, at one flat price.
Free to start · Unlimited viewers