How to use KitchenPulse without remembering the whole demo.
This guide explains where to start, what each page is for, and what questions to ask when KitchenPulse surfaces a signal.
Start on Home
Use the Home page as the daily operating brief. It tells you the main recommendation, why it surfaced, what to do now, and what to watch.
Check What Changed
Use What Changed when you want to understand what rose, fell, recovered, or needs attention compared with the prior run.
Use Ask SynthoPulse
Ask follow-up questions in plain language when you need a quick explanation, pre-shift talking point, or action recommendation.
What each KitchenPulse page is for.
Use this as the reference when a manager forgets where to go or what a signal means.
Home
Your daily starting point. Home summarizes the most important current recommendation and the context behind it.
- You want to know what matters before service.
- You need the primary recommendation for the day.
- You want a quick owner/GM-level explanation.
- Why did this surface?
- What should we do before service?
- What is the risk if we ignore this?
What Changed
Shows item movement between runs so you can see what improved, dropped, recovered, or needs confirmation.
- You want to know what changed since the last comparable service.
- You need to review rising items, low sellers, or recovery signals.
- You want the reason behind the Home recommendation.
- Which items need attention?
- What should we lean into today?
- Is this a one-time movement or something to watch?
Sales Dashboard
Shows captured sales performance, margin, profit, month-to-date health, and owner-level business context.
- You want revenue, profit, and margin context.
- You need an owner-level performance read.
- You want to compare the latest dinner run to prior dinner performance.
- Was the last run healthy?
- Did revenue improve without hurting margin?
- What should the owner care about here?
Events
Tracks local demand signals, in-house events, private events, holidays, and upcoming service pressure.
- There is a local event that may affect traffic.
- Your restaurant has an in-house or private event coming up.
- You want to review today’s service pressure.
- Will this event affect service?
- Should this be promoted to service pressure?
- What should we prep differently?
Staffing
Shows scheduled shifts and coverage context so managers can catch staffing gaps before service.
- You want to verify who is on today.
- You need to check FOH, BOH, Bar, or Management coverage.
- You want staffing context alongside demand pressure.
- Do we have enough coverage today?
- What department looks thin?
- Does staffing match expected demand?
Receipt Intake
Uploads vendor receipts and invoices so KitchenPulse can parse line items, stage cost signals, and route them for review.
- A vendor receipt or invoice needs to be uploaded.
- You want to review parsed line items.
- You want new vendor costs to become trackable over time.
- Did this receipt parse correctly?
- Which cost changes need review?
- Did the system create a readable item name?
Cost Center
Turns approved receipt data into cost movement, margin pressure, and vendor cost intelligence.
- You want to see which costs are rising.
- You want to spot cost relief or vendor opportunities.
- You need to review active cost signals before they affect margins.
- Which vendor items are getting more expensive?
- What cost movement should the owner review?
- Is this a pricing, vendor, or portioning issue?
A simple path for training new staff.
When someone is new to KitchenPulse, walk them through this flow. It shows the system as an operating guide, not a pile of pages.
- 1Open Home and read the primary recommendation.
- 2Open What Changed to show what moved.
- 3Open Sales Dashboard for captured revenue, profit, and margin context.
- 4Open Events and show how to add or review a local demand signal.
- 5Open Staffing to verify schedule coverage.
- 6Open Receipt Intake and explain the upload → review → cost signal workflow.
- 7Open Cost Center to show margin pressure and cost movement.
- 8Use Ask SynthoPulse for a follow-up question.
What to remember after the demo.
KitchenPulse is designed to be used in quick operating loops. Start with the recommendation, then dig into the page that explains the signal.
Where should I start each day?
Start on Home. It gives you the primary recommendation and explains the action, risk, and context. Then use What Changed if you want the item-level detail behind the recommendation.
What if a page looks empty?
An empty page usually means there is no current signal that qualifies for that section. For example, Today’s Service Pressure only shows events intentionally flagged to affect today’s service window.
What should I manually add?
Add events or local demand signals that KitchenPulse would not know automatically: school games, local festivals, downtown events, private parties, catering-heavy days, or unusual traffic patterns.
Can I trust receipt cost changes automatically?
Receipt data is review-first. Uploads and parsed lines are staged before they become active cost movement. The system is designed to keep humans in control of cost updates.
What should I ask SynthoPulse?
Ask practical operating questions: why something surfaced, what to do before service, what to watch, what to say in lineup, or what happens if the team ignores the signal.
Ask SynthoPulse what to do next.
The best questions are practical: what changed, why it matters, what to do before service, and what happens if the team ignores it.