People & HR

How to onboard a new hire as Restaurant and Hospitality Founders

People & HRFor Restaurant and Hospitality Founders4 apps12 steps~24 min to set up

Hiring a new line cook, server, or front desk agent in hospitality means juggling a stack of disconnected steps: texting offer letters, manually setting up 7shifts or Homebase with their availability, adding them to Square or Toast as a new employee, walking them through your house rules on paper, and hoping someone remembers to give them access to the group chat. There's no checklist. There's no single place to put the training materials — they're split between a shared Google Drive nobody updates, a laminated binder behind the host stand, and institutional knowledge that lives in your head. A new hire's first week is chaotic because you haven't had two hours in a row to build a better system.

Build this on Starch → See the apps used

People & HRFor Restaurant and Hospitality Founders4 apps12 steps~24 min to set up

Outcome

What you'll set up

A structured onboarding workflow that automatically generates a new-hire task list, sends a welcome email with first-week instructions, and surfaces training materials the moment someone is added to your team

A team wiki built in Starch's Knowledge Management app where your house rules, uniform standards, table numbering, POS tip-out process, and health code requirements all live in one searchable place — so new staff stop asking you the same five questions

A scheduling link new hires use to book their orientation slot directly, without a chain of texts about when you're both free

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Knowledge Management Scheduling Task Manager

Data sources & config

Knowledge Management connects to Notion via Starch's scheduled sync so any existing SOPs or training docs you've stored there pull in automatically. The Scheduling app syncs directly with Google Calendar via Starch's scheduled sync to show real-time availability. Email Triage (Email Agent) connects to Gmail via Starch's scheduled sync to draft and send the welcome email. Task Manager runs standalone. For hospitality-specific tools like 7shifts or Homebase that don't have a formal scheduled-sync connection, Starch automates them through your browser — no API needed — to pull or push employee data.

Prompts to copy

Build me a new hire onboarding wiki that covers: our tip-out policy, uniform requirements, table numbering and section maps, how to clock in and out in 7shifts, how to process a comp in Square, and what to do if a guest complains. Add a section for kitchen hires and a separate one for front-of-house. Flag any page that hasn't been edited in 60 days.

Create an onboarding task list for a new FOH hire starting Monday. Include: complete I-9 paperwork by day 1, shadow a senior server for two dinner services, pass the menu quiz by end of week 2, get added to the staff group chat, and attend the Monday pre-shift by week 3. Set P1 priority on anything due in the first 48 hours.

Set up a scheduling link for new-hire orientation slots — 45 minutes, Tuesday and Thursday afternoons between 2pm and 4pm, buffer 15 minutes before and after so it doesn't run into dinner prep. Send the link in the offer confirmation email.

Draft a welcome email for a new line cook starting next Monday. Include their start time, what to bring for I-9 verification, who to ask for when they arrive, and a link to the kitchen onboarding wiki. Keep it under 150 words, direct tone.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Notion to Starch (scheduled sync) if you already have any SOPs, training docs, or staff handbooks there — Starch will pull them into the Knowledge Management app automatically so you're not starting from zero.

2 Open the Knowledge Management app and describe your wiki structure in plain language: 'I need a front-of-house section covering tip-out, table maps, and POS comps, and a kitchen section covering prep lists, allergen handling, and clock-in process.'

3 Paste or type your existing house rules, tip-out policy, and section maps directly into the wiki. Starch's AI will auto-categorize them, add headers, and flag which pages are missing information.

4 Set a staleness rule: 'Flag any wiki page that hasn't been updated in 60 days' — so the binder-behind-the-host-stand problem never migrates to your digital system.

5 Open the Scheduling app, connect your Google Calendar (Starch syncs it on a schedule), and create an 'Orientation' meeting type: 45 minutes, Tuesday and Thursday 2–4pm, 15-minute buffer, max 1 booking per slot.

6 Copy the scheduling link and add it to your offer letter template so every new hire books their orientation without a text thread.

7 Open Task Manager and describe your standard onboarding checklist: 'Create a task list for a new FOH hire — I-9 day 1 (P1), shadow two dinner services by day 5 (P2), pass menu quiz by day 14 (P2), attend Monday pre-shift by week 3 (P3).' Starch builds the list; duplicate it for each new hire.

8 On the day you send an offer, open Email Triage and prompt: 'Draft a welcome email for [Name] starting [Date] — include start time, what to bring for I-9, who to ask for at the door, and a link to our onboarding wiki.' Review and send in one click.

9 For adding the new hire to 7shifts or Homebase, Starch automates the data entry through your browser — describe the fields you fill in every time and it handles the repetitive clicks, no API required.

10 On the new hire's first day, pull up their Task Manager checklist and walk through it together in under 10 minutes — every item is already prioritized and dated, so the conversation is about the job, not the paperwork.

11 At the 30-day mark, prompt Starch: 'Which onboarding tasks are overdue for hires who started in the last 60 days?' Task Manager surfaces the gaps so nothing slips through the end of a busy dinner service.

12 After three months, ask Knowledge Management: 'Which pages have the most searches from new hires in their first two weeks?' The answer tells you where your training is thin and where to write more.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 — Onboarding Two FOH Hires Ahead of Summer Patio Opening

Sample numbers from a real run

Orientation scheduling (per hire)	0
Wiki pages auto-populated from Notion SOPs	14
Onboarding tasks generated per hire	11
Welcome emails drafted and sent	2
Time spent on onboarding admin (hrs, down from ~4)	1

You hired two servers in late March ahead of the patio opening on May 1. Normally that means two rounds of texting, two separate Square employee setups, printing updated table maps, and a 45-minute 'orientation' that's really just you answering the same questions you answered for the last three hires. This time: you connected Google Calendar to Starch (scheduled sync), set up the Orientation meeting type in the Scheduling app, and dropped the booking link in both offer emails. Both hires picked their own slots — no texts. You'd already built the FOH wiki section the week before by prompting: 'Build a front-of-house training section covering our 5-table section map, tip-out split (70/20/10 server/busser/bar), how to process a comp in Square, and our policy on phone use during service.' Starch organized it, flagged that the allergen page was missing, and you filled it in during a slow Tuesday lunch. On their first day, each hire got an 11-item Task Manager checklist with P1 flags on the I-9 and uniform policy sign-off. By day 3 they'd completed 8 of 11 items without a single text to you asking what came next. Total admin time: under an hour across both hires, including the welcome emails drafted in Email Triage.

Measurement

How you'll know it's working

Days from offer acceptance to first solo shift (target: ≤10 days for FOH)

Onboarding task completion rate at day 7 and day 30

Number of questions the new hire asks you directly in their first two weeks (a proxy for wiki quality)

Wiki page staleness rate (% of pages flagged as not updated in 60+ days)

Orientation no-show rate (should drop to near zero with a booking link)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Paper binder + group text

Zero cost but zero structure — the binder gets lost, the group text gets searched, and you re-explain the tip-out policy every three months.

Google Drive folder of training docs

Searchable if you remember what you named the file, but no AI triage, no staleness detection, and no connection to your calendar or task list.

Gusto or Rippling onboarding module

Strong for payroll paperwork and compliance checklists, weak on the operational training side — it won't hold your table maps, tip-out policy, or POS comps guide, and it won't draft the welcome email for you.

Notion standalone

Good wiki structure, but you're building and maintaining it manually with no AI to flag stale pages, generate task lists, or draft outbound emails — and it doesn't connect to your calendar or hospitality-specific tools without a lot of setup.

7shifts onboarding tools

Covers scheduling and shift notes for hourly staff, but it's scoped to scheduling — it won't hold your training wiki, send welcome emails, or track non-scheduling onboarding tasks like I-9 completion or menu quiz scores.

On Starch RECOMMENDED

One platform — knowledge management, scheduling, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch connect directly to 7shifts or Homebase to add new employees automatically?

7shifts and Homebase don't have a formal scheduled-sync connection in Starch today, but Starch can automate them through your browser — no API needed. Describe the fields you fill in when adding a new employee and Starch handles the repetitive data entry. It's the same approach that works for any web-based tool you can log into and click through.

What if my training materials are spread across a Google Drive and an old Notion workspace?

Starch syncs your Notion data on a schedule and can pull it directly into the Knowledge Management app. For Google Drive documents, connect Google Drive from Starch's integration catalog and the agent can reference those files when building your wiki. You don't have to copy-paste everything manually.

Can Starch handle the actual I-9 or tax form paperwork?

Not today. Starch is great at organizing the checklist that reminds you and the new hire that the I-9 is due on day 1, drafting the email that explains what documents to bring, and tracking whether the task got marked complete — but the actual form completion and e-signature workflow is better handled by a tool like Gusto or your state's labor portal. Starch can automate browser navigation to those portals if you need it.

Is Starch SOC 2 certified? We have health and HR data in here.

Starch is not SOC 2 Type II certified today. If your compliance requirements make that a hard requirement for storing staff data, that's worth knowing up front. For most independent restaurant and hospitality operators, the onboarding workflow described here is operational — task lists, wiki content, scheduling — rather than sensitive payroll or health records, which you'd keep in your payroll system.

How does the Scheduling app handle it if I need to cancel or move an orientation slot?

The Scheduling app syncs with your Google Calendar on a schedule, so if you block time or delete the event on your calendar, the booking page reflects the change automatically. You can also update availability rules directly in the app — for example, 'block all Tuesday slots for the next two weeks during the patio build-out.'

We turn over staff a lot. Is this worth building if it'll just need to be redone?

High turnover is exactly the reason to build it once. The wiki doesn't change when a server leaves — your tip-out policy is still your tip-out policy. The task list is a template you duplicate, not recreate. The scheduling link stays live. The one-time investment of building the onboarding system pays off the second time you hire someone, and every time after that.