Manager Closeouts

OverviewCopy Anchor Link

Manager Closeouts are Service Day summaries for managers. They bring the resolved Primary Daypart context, POS value and freshness, task and incident attention, readiness, deliberate Staff Reviews, operational notes, media, and draft state into one publish flow.

Canonical source: Manager Reports feature contract. This guide covers the user workflow; the contract and ADRs own schema and lifecycle details.

Filing a Manager CloseoutCopy Anchor Link

Managers should file one closeout for each location they oversee for each Service Day.

1. Navigate to Reporting → Shift Reports → Manager Closeouts.
2. Confirm the context at the top: Service Day, location, resolved Primary Daypart, and the POS value, freshness, and source when available. The report uses Service Day grain; Primary Daypart is compatibility context, not a second report obligation.
3. Enter or confirm the sales value when the POS value is unavailable or needs a manual correction.
4. Review task completion, incidents, readiness, and the pre-shift briefing.
5. Rate FOH, BOH, and Support.
6. Select staff deliberately for Staff Reviews. Lineup candidates provide a role-aware starting point; correct a role only within the available roles. A review may contain a rating, an observation, or both.
7. In Operational Notes, make the explicit follow-up decision. When follow-up is selected, at least one operational note category (Optimization, FOH Notes, BOH Notes, Customer Feedback, or Other Notes) is required with meaningful text, though no single category is mandatory on its own. 1% Better and positive Staff Reviews can coexist with No operational follow-up. Recovered operational notes keep the detailed path active. Clear those notes explicitly before selecting no operational follow-up; saved text is never silently discarded. Low operational ratings reveal the relevant note fields.
8. Attach photos or video under Media if needed.
9. Review the final publish summary, including deliberate review count, notes and follow-up state, media, draft status, blockers, and audience.
10. Click Publish Manager Closeout. If incomplete tasks require an override, the dialog shows the exact preflight items and remediation; provide a trimmed reason of 10–500 characters. The server rechecks the preflight before accepting the command.

Drafts, Autosaving & Publish PreflightCopy Anchor Link

You do not need to manually save drafts. The report continuously autosaves your progress while you type (stripping identity parameters for safety). You can safely close the page and return later; a recovered draft reloads without discarding its values.

• Drafts: Editable working state for the Manager Closeout, saved locally/server-side per location and Service Day.
• Publish Preflight: The server-authoritative check highlights incomplete tasks and other readiness information before publishing. A retryable failure keeps the override reason available for retry.
• Published: A finalized report revision available through report surfaces and governed by the report retention contract.
• Service Day: Publishing a report and closing Service Day are separate actions. Use the Service Day Workspace when the operation is ready to close.

RelatedCopy Anchor Link