Journeys
-
First hour: from sign-up to a published first week that everyone has. Standing. Start at Sign up, or Sign in to carry on.
-
Worker joins: from the invite or publish link arriving to the app installed for push. Standing. Start from a team past its first hour, with a week published and invites out:
-
Weekly build: from availability and time-off requests arriving to staff told of the published week. Standing as far as the schedule, Time off, Availability, the shift record and the staff side of publishing go. Starts with an owner past the first hour: this week posted, next week still to build, requests waiting.
-
Cover during the week: from a worker who cannot make a shift to everyone affected told. Standing.
Marlow's Kitchen is the same team and published week as the labour start, with shift confirmation on.
-
The shift: from a worker arriving and clocking in to the shift lead closing out the day. Standing. Starts mid-afternoon on a day with a published week, a team of eleven, a kiosk PIN for each, and some already on the floor.
-
Pay period close: from the period's end to the payroll file accepted in the employer's payroll. Standing. Start below.
-
Switching: from leaving an incumbent at the start of a pay period to the first paid period. Standing as far as the team comes over: Import, Staff's Invited view, invites, History, API keys, webhooks and the helpdesk. The pay calendar, payroll, first week, joining and close belong to other journeys. Starts with an owner past the first hour: a published week and a team of three.
-
Hiring: from a job post drafted to the new hire standing in the schedule build. Standing. Start Hiring.
-
Trial end: from the Trial-ending notice reaching the owner to every location working again. Standing. Start below.
-
Leaving: from the owner deciding to leave to the account on Free, or closed, exported and deleted. Standing. Start below.
-
Labour against sales: from the owner setting each location's labour target to a shift lead sending someone home. Standing. Starts with an owner past the first hour: a published week, a team of eleven, and today on the floor.
Google accounts the chooser offers:
- Maya Brooks, maya.brooks@gmail.example, locale en-US
- Aisha Khan, aisha.khan@gmail.example, locale en-CA
- Tom Hughes, tom.hughes@gmail.example, locale en-GB
- Léa Tremblay, lea.tremblay@gmail.example, locale fr-CA
- Chris Walker, chris.walker@gmail.example, locale en-GB
Any email address works through the emailed link; any mobile number works through the texted code. Read both below under Messages received. A US, Canadian or UK number is accepted.
What the provider tells sign-up
Sign-up reads the network's country, the browser's time zone and the browser's language. Where they name one country, sign-up asks nothing. Where they name two, it asks the owner to choose.
Hiring
Hiring starts from a restaurant past its first hour: a team, a draft week for next week, and an onboarding list. Nothing is posted yet. Start it in a market:
Act as
Start a journey to meet the team.
Clock
Now in the walk: October 22, 2026 at 3:44 AM (America/New_York)
The floor
Pay period close
Each start puts the walk at Marlow's Kitchen at the end of a pay period, with the clock before the period's end and the account past its first hour. It replaces what is here.
Trial end
Starts with an owner 24 days into the trial: a published week, 22 staff, a second location, and the trial ending in 6 days. It replaces what is here.
Leaving
Starts with an owner 10 days into a paid month: a published week, 22 staff, a second location and the card charged at the trial's end. It replaces what is here.
Stand-in files
A stand-in spreadsheet of ten rows, for Settings, Import: stand-in-team-sheet.csv stand-in-team-sheet.xlsx
A stand-in export from the incumbent scheduling product, for Settings, Import: one workbook of four sheets, or one CSV per list. stand-in-incumbent-export.xlsx locations staff time off timesheets
A stand-in spreadsheet of daily sales, for Settings, Import: stand-in-sales-sheet.csv stand-in-sales-sheet.xlsx
Integrations
The owner's webhook endpoint answers with success: yes.
The helpdesk, for an owner who asks support to move the team over: Open the helpdesk conversation
Messages received
Nothing has been sent yet.