Staff Service Day Reports

OverviewCopy Anchor Link

Staff Service Day Reports capture what happened during service: sales where your role owns them, how each area performed, what to improve, and who deserves recognition. File one report per Service Day at your location, even when you work multiple Dayparts.

Drafts save automatically as you type, so you can start filling it in mid-service and finish later. Drafts sync to your account and can be resumed on another device for the same Service Day and location.

Filing a Staff ReportCopy Anchor Link

At the end of your service:

1. Go to Service Day → Tasks → Submit Staff Report (or open it from Today or Review → Staff Reports).
2. Confirm the Service Day, location, assigned Dayparts from the published Daily Lineup, Primary Daypart, and role shown at the top. Required fields are marked, and errors show up in a summary near the submit controls.
3. Tap Submit Report when you're done.

You owe one Staff Report per Service Day per location — even if you worked Lunch and Dinner, file a single report. The Primary Daypart is the compatibility context for the report; the form also shows assigned Dayparts from the published Daily Lineup. Goal Sales is read-only context from the published Daily Lineup and combines goals across all assigned Dayparts when available. The form is organized into 5 numbered sections:

01. Service Day DetailsCopy Anchor Link

• Service Day — defaults to the current Service Day.
• Position — suggested from lineup assignments or your primary reporting role. Correct it if needed using Server, Bar, Host, Expo, Bus, Kitchen, Manager, or Other. Your corrected role determines whether sales are required.
• Primary Daypart — the compatibility daypart used by the existing report record. Assigned Dayparts from the published Daily Lineup are shown separately.

Your location and assigned Dayparts come from the server-owned report context.

02. SalesCopy Anchor Link

Sales fields follow your role:

• Actual Sales (required) — required for Server and Bar roles. Enter the actual sales you own for this Service Day. This is a required manual value; it is not a POS attribution.
• Actual Sales (optional) — optional for Other roles. Enter a manual value only when you have one.
• Not applicable — roles without sales responsibility (Host, Expo, Bus, Kitchen, and Manager) have no sales input.
• Goal Sales — read-only context from the published Daily Lineup when available. If the lineup is unavailable, the form says so instead of inventing a value.

03. RatingsCopy Anchor Link

Rate each area of the operation on a 1–5 scale. All four ratings are required to submit. 1 means a serious breakdown requiring follow-up; 5 means exceptional execution worth recognizing.

04. NotesCopy Anchor Link

• Manager follow-up — explicitly choose whether a manager follow-up is needed. When follow-up is selected, at least one written detail (Incident Notes or General Notes) is required. Choosing No follow-up means there is no notable issue requiring manager attention; recognition and 1% Better can still be included.
• Incident Notes — describe incidents when follow-up is needed; link serious issues to Incident Reporting.
• General Notes — anything else worth flagging.
• 1% Better — one specific improvement, independent of the follow-up choice.
• Recognition — name a teammate who stood out, independent of the follow-up choice.

Follow-up details remain visible when a saved draft is recovered, so review them before submitting.

05. Photos & VideoCopy Anchor Link

Attach photos or short videos from the Service Day — receipts to follow up on, plate presentation, damaged equipment, or anything visual that supports your notes. When an attachment cannot be previewed, its filename or link remains available as an alternative.

Identity-Safe DraftsCopy Anchor Link

The status line above the Submit Report button shows:

• Saving draft… while autosave is in progress
• Draft saved when everything is synced
• Unsaved changes if you've edited since the last save

Drafts strip client-provided identity context (userId, teamId) to protect multi-user devices. If you return to a half-finished report, a Restore draft banner offers the server-saved version. Upon successful submission, the saved draft state is automatically cleared.

RecognitionCopy Anchor Link

Naming a teammate is how staff recognize each other publicly. Recognition can be submitted with either follow-up choice.

After You SubmitCopy Anchor Link

• Management can read the submitted Staff Report through the reports and compliance surfaces; submitted reports are not Operations Inbox feed entries.
• A summary is posted to your team's Slack channel (sales context where applicable, ratings, key notes, your 1% Better, and recognition).
• The report satisfies your Staff Report obligation for the Service Day.

RelatedCopy Anchor Link