Most restaurants track numbers. Few restaurants act on them the same way twice. The RAA framework closes that gap by forcing every KPI, every week, through the same three-part loop: Result, Analysis, Action.
What does RAA stand for in a restaurant?
RAA stands for Result, Analysis and Action, the three-part weekly loop a restaurant runs against every number on its KPI sheet.
Result is simply the number and how it compares to target. For example, food cost was 34.2%, which is 2.2 points above the 32% target. That sentence alone is not useful on its own, but it is the starting point.
Analysis is the root cause behind that number, not a description of the week. In the food cost example, the analysis might read: the waste log shows 18 lbs of proteins discarded on Wednesday, and the receiving log shows a $400 price increase from the primary supplier. That sentence tells a manager exactly where to look.
Action is the specific change, the named owner, and the deadline. Something like: the chef re-pars Wednesday proteins by Tuesday end of day, and the owner calls the distributor by Friday to renegotiate price. No vague intentions, no open-ended follow-up.
Why must the Result come from a controller and not a manager?
Because the person being measured has an incentive to distort the measurement, so the number has to come from someone with no stake in how it looks.
A manager reporting their own food cost or labor cost number is grading their own test. RAA removes that conflict by requiring the Result to come from an independent source, such as a controller pulling directly from POS and payroll records rather than from a manager's self-report.
This single structural change is what separates RAA from a normal KPI meeting. The loop only works if the first step, Result, is trustworthy. Everything downstream, the Analysis and the Action, is only as good as the number it starts from.
What is the difference between analysis and description?
Description restates what happened in general terms, while analysis names the specific, measurable cause behind the number.
"It was a busy week" is description. It explains nothing and leads to no action. "Tuesday and Wednesday exceeded forecast by 22%, but labor was not cut mid-shift, resulting in a 3.1% labor overage" is analysis. It names the exact days, the exact gap, and the exact decision that caused the overage.
The same test applies to Action steps. "Be more careful with portioning" is not an action because nobody can be held to it. "Chef weighs the top five proteins at every shift start using a digital scale, logged in the waste tracker" is an action, because it can be checked the next day.
Results are not typical and will vary with your business, your market, your team and how much of the work you actually do. Client figures on this site come from recorded interviews and are dated. Nothing here is a guarantee of revenue, profit or growth.
How do Green, Yellow and Red trigger zones work?
Trigger zones pre-define the response to a number before it goes bad, so the team reacts automatically instead of deciding under pressure.
- Green, at or below target: acknowledge the result and move on.
- Yellow, 1 to 2 points above target: the KPI owner writes a one-page analysis and presents it at the Weekly Sync.
- Red, 3 or more points above target: an owner audit meeting is held within 48 hours.
Waiting until a number looks bad to decide what to do means time has already been lost. Pre-defined zones remove that lag entirely.
What happens when a restaurant actually runs RAA every week?
One Founders Board member used RAA with an independent controller to turn prime cost swings of 62-68% into a stable 59%, adding $54,000 in pure profit in year one.
The shift was not a new recipe or a new vendor. It was the structure itself: a trustworthy Result, honest Analysis, and specific Action, repeated weekly until the pattern stabilized.
How does RAA fit into a restaurant's broader KPI system?
RAA is the weekly engine that runs against every target on the KPI sheet, including food cost at 32% and labor cost at 29%, turning each target into a tracked loop instead of a one-time goal.
A target without a loop is just a number on a wall. Food cost target of 32% and labor cost target of 29% only matter if someone checks the actual result every week, explains the gap with real analysis, and assigns a specific action with a deadline. That is what RAA does for every line on the sheet, not just the headline metrics.
Restaurants that build this discipline into every KPI, not just the ones that are currently a problem, are the ones that catch drift early. Pizza Pizzazz installed KPIs on every line of its profit and loss statement within 90 days, which is the same instinct RAA is built on: measure everything, not just what is already on fire. The Pizza Pizzazz case study covers how that played out.
What does it take to put RAA to work in a real restaurant?
It takes an independent data source for the Result, a habit of writing root-cause Analysis instead of description, and an Action with a named owner and deadline, run on a fixed weekly schedule.
None of the three steps is complicated on its own. The discipline is in doing all three, every week, on every metric, without exception. That consistency is what the Scaling Engine OS licenses to Founders Board members, built from the same structure used across the restaurant groups the coaching team has worked with.
Owners who want to see whether this kind of structure fits their business can review the case studies or apply directly.
