F&B Weekly and Monthly Report Assistant

The Problem

Restaurant weekly and monthly reports often become itemized data dumps. Store metrics may be present, but the report still lacks a clear loop from problem identification to action priority. When data is missing or metric definitions are inconsistent, teams may rely on intuition, making it harder to support decisions on staffing, inventory, promotions, and store operations.

How It Works

The skill structures reporting into four steps: problem definition and information collection, framework matching and deep analysis, solution generation and prioritization, and execution and review iteration. It loads relevant methods from references/ based on the scenario, uses cases/ for typical, challenging, and successful patterns, and favors ready-to-fill templates in assets/. Output follows a numbers-first rule: each conclusion should carry a key metric where possible, and actions should specify who does what and how quickly it can show impact. Missing data assumptions are marked explicitly.

Boundaries

It is best for restaurant operators, regional managers, or project owners preparing weekly reports, monthly reports, work summaries, and OKR progress updates. It is not intended as a financial audit, legal compliance, or real-time operations monitoring tool. Users still need to provide baseline business data, goal definitions, and time windows; otherwise conclusions may rely on industry benchmarks and should be reviewed before execution.