Weekly Owners’ Report Template: What to Review from Food Cost Metrics
If you run an izakaya or a family restaurant, your margins move week to week. A repeatable weekly report helps you catch issues early, connect them to inventory and menu decisions, and keep your food cost percentage on target.
Start with the numbers that explain the “why”
Don’t treat food cost percentage like a single score. Use it as a trigger, then read the underlying components: what went up, where it came from, and how it affected the menu mix. Your weekly report should answer three questions.
- What changed? Identify the biggest movers in COGS and food cost percentage.
- Where is it coming from? Tie changes to specific ingredients, menu items, or POS categories.
- What will we do next? Choose actions you can test within 7 days.
Your weekly report template (copy this into your workflow)
-
Executive summary (30 seconds)
Write one sentence each for: your target status, the main driver, and the next decision. Keep it short so it’s usable when you’re busy.
- Food cost % vs last week
- [Enter %]
- COGS driver
- [Ingredient/Menu]
-
Ingredient price + usage check
Compare ingredient price movement to your actual usage. If usage rises and price stays flat, you may have a portion or recipe drift. If price rises and usage stays flat, you need repricing or substitution.
Top price increase (JPY)[Enter]Usage change (by weight or case)[Enter] -
Menu mix and contribution review
Food cost percentage can look stable while your menu mix shifts. Review which items contributed most to COGS, not only what sold the most.
Checklist
- Identify 3 items with the biggest COGS contribution.
- For each, note: price stability, portion stability, and recipe match.
- Decide whether to adjust portioning, recipe, or menu engineering.
-
Waste, returns, and prep drift
If COGS rises without a clear price or usage reason, audit waste and prep. Weekly notes from kitchen and bar staff are often the fastest way to find the mismatch.
- Waste notes (what changed)
- [Enter]
- Corrective action
- [Enter]
-
One-week test plan
Choose only one or two changes you can validate next week. Examples include portion adjustments, a temporary menu substitution, or a price review for a high-volatility ingredient.
Test (action + scope)[Enter]Expected impact[Enter]This is where you convert metrics into decisions, and keep learning from week to week.
Practical tips for weekly consistency
Make the report fast to fill
If the weekly report takes longer than 15 to 20 minutes, it won’t stay consistent. Use templates and pre-filled comparisons for last week vs this week.
Tie actions to specific menu items
When you adjust portions or ingredients, note which dishes are affected. Otherwise the next week’s review becomes guessing.
Keep an eye on seasonal ingredient price fluctuations
In Japan, ingredient costs can shift quickly. A weekly cadence helps you protect margins before changes spread across your menu.
Recommended next read
If you want to go deeper on turning ingredient movement into menu-level decisions, review how a seasonal menu strategy protects margins.
Read: Seasonal Menu Optimization