1) Confirm setup and ownership first
Check locations, roles, people records, pay settings, punch readiness, and policy modes first so the live week is built on the same staffing and payroll truth.
This guide follows the real weekly rhythm: set up locations and team records once, then build, publish, run shifts, capture time, review payroll and tax context, read finalized POS Server Checkout context when connected, and keep people ops connected in order.
Keep the first decision on setup, weekly build, clean time capture, and payroll closeout before opening live Schedule, the pricing page, or rollout planning.
Check locations, roles, people records, pay settings, punch readiness, and policy modes first so the live week is built on the same staffing and payroll truth.
Move through draft build, conflict review, publish, midweek adjustments, timekeeping cleanup, and payroll review in sequence so managers do not jump from draft creation straight into labor or tax review.
Once workflow fit is clear, move to the live app, pricing review, or rollout planning based on whether the next question is launch timing, buying scope, or direct follow-up.
The guide follows the real schedule cycle so setup, weekly build, team actions, and payroll closeout stay connected.
People, pay, policy, and punch readiness come first because draft quality and payroll accuracy both depend on the same staffing data.
Manager playbooks and team runbooks are split so ownership stays clear and staff do not have to read admin steps before they find their own daily actions.
Support notes stay at the bottom so operators can stay in the weekly workflow first, with rollout and technical review available only when that becomes the next question.
This quick launch map shows where owners, managers, and team members start in the Schedule week.
Start with setup, policy readiness, and the weekly build-to-closeout playbook so staffing truth, labor review, payroll exports, and people follow-through all stay connected.
Move into the manager playbook and screen-by-screen runbooks once setup is stable so weekly draft, publish, timekeeping, swaps, alerts, and closeout work stay in the right order.
Jump to the team runbooks only after the publish flow is clear so requests, acknowledgements, time-clock use, and pickup behavior match the live manager process.
Complete this checklist once so weekly scheduling, approvals, compliance, and labor reports work end-to-end.
Run this sequence every week to keep schedule quality, time capture, payroll review, and people follow-through aligned before the week closes and the next publish cycle starts.
| Phase | Where To Go | What To Do | Done When |
|---|---|---|---|
| 1) Week Prep | Schedule board, Staffing targets | Set target week, review prior publish versions, confirm staffing targets and role coverage priorities. | Coverage expectations are clear before creating drafts. |
| 2) Draft Build | Auto-schedule, Schedule board | Generate draft shifts (role groups, pars, days, stagger), then edit manually and drag/drop where needed. | Draft contains the full week with minimal open shifts. |
| 3) Conflict Pass | Schedule board, Rules, Compliance | Resolve time-off overlaps, availability conflicts, and policy blocks before publishing. | No unresolved issues remain for publish target roles. |
| 4) Publish + Snapshot | Schedule board (Publish by role / all roles) | Publish schedule, verify version snapshot was created, and keep rollback option available. | Team sees published shifts and managers can roll back if needed. |
| 5) Midweek Operations | Time off, Trade board, Callouts | Process time-off, trades, pickups, and callouts fast to protect coverage quality during service days. | Requests are actioned and open shifts are reassigned or escalated. |
| 6) Clock + Accuracy | Time clock, Timesheets | Ensure personal or shared clock-in/out discipline, correct exceptions, and tag manager edits with notes. | Actual hours are clean enough for payroll, labor variance, and end-of-period approvals. |
| 7) Cost + Closeout | Labor actuals, Labor forecast, Payroll, Tips context, POS integration | Review scheduled vs actual, labor %, overtime, payroll gross, finalized POS Server Checkout tip context, liabilities, and exported payroll files before close. | Financial week is reconciled, payroll/tax context is ready, and next week planning inputs are ready. |
These operating runbooks keep each manager area tied to the weekly schedule rhythm.
Schedule board
Auto-schedule
Staffing targets
Team, Roles
Time off
Trade board, Callouts
Rules, Compliance
Quality scan, Notifications
Labor actuals, Timesheets, Payroll
Labor forecast, Pay rates, Tips context, HR, POS integration
These steps show how staff handle personal scheduling work day to day.
My work home
Availability
Trade board
Time off
Time clock, Timesheets
Notifications, Announcements
These routines keep schedule quality, labor, timekeeping, payroll, and team performance stable.
Keep the workflow focused on schedule build, timekeeping review, payroll closeout, and people follow-through, then move to pricing or rollout when those questions come next.
The Schedule product page gives a shorter buyer overview before the full workflow manual.
The integrated platform guide explains how Scheduling connects with POS closeout, labor records, operations follow-through, and the wider platform.
The Resources hub provides labor explainers, scheduling buyer context, hiring guides, and playbook templates when the next step is still educational.
Move to Reader or Training when the next question is training cadence, standards reinforcement, onboarding support, or leadership reading instead of scheduling screens and payroll flow.
Engineering is the right destination when the next question becomes architecture, implementation detail, or rollout constraints. Pricing review and rollout conversations work best after workflow fit is clear.
The operator guide above stays focused on labor planning, timekeeping, payroll review, and team workflows. For deeper architecture, rollout, or integration questions, use Engineering or direct implementation follow-up without making the operator manual harder to read.
Technical review is useful when the question becomes payroll integration, POS imports, permissions, multi-location access, or deployment details.