EXAMPLEIllustrative example · fictional restaurant «Sazón de Origen». Not your data: your result is built with YOUR restaurant's.See the assistant →
Sazón de OrigenFictional contemporary Colombian restaurant in Medellín, 2 locations, 6 years in business. Every sample result in the library comes from this same case.
Dashboards, KPIs and Scorecards

Sample result

Service Dashboard Builder for Restaurants

The owner asked this:«I want the service board for both locations. My fear: the Google score keeps dropping and I don't know what's pulling it down.»

① Block A · The service dictionary (4 of 10 indicators)

SUPUESTO: complaints are read per hundred covers using the covers each location's POS reports. If the POS counted tickets instead of diners, the figure inflates on group tables and Saturday would look worse than it is; in that case the source has to change before the target gets argued.

IndicatorFormulaSourceFrequencyOwnerTarget
Score per channelWeek's average, each channel separatelySearch profile + delivery platform + QR surveyWeeklyManagerSet by the owner
Dominant themeTheme mentions / hundred covers in the bandReviews + complaint logWeeklyManagerSet by the owner
Closed recoveryComplaints with a gesture AND written closure / totalComplaint logWeeklyShift leadSet by the owner
Return signalRepeater tables / identifiable tablesBookings + POSWeeklyManagerSet by the owner

The theme repertoire comes out of the real reviews, with a fixed name and a literal example beside it, so two people classify the same review the same way: «peak-hour delay», «cold delivery», «loud music», «portion not the usual one».

② Block B · The servicio.html file, read on a Monday

Four blocks on one screen. SCORE PER CHANNEL: search profile 4.3 🔴 and dropping 3 weeks running (4.7 → 4.5 → 4.3), delivery platform 4.6 🟢, QR survey 4.8 🟢 — the drop lives ONLY on the search profile, which is where the weekend dining-room guest reviews; the channel average would have hidden it.

THEMES: «peak-hour delay» 7 mentions 🔴 (2.4 per hundred covers), «cold delivery» 2 🟡, «loud music» 2 🟡. The dominant theme concentrates in a single Saturday band: it has a shift cause, not a method cause.

COMPLAINTS: 9 in the week, 7 with a gesture and written closure 🟡, 2 with no trace of what was done 🔴 — one of them already passed 48 hours and escalated to the owner with a name and an hour.

RETURN: 31% 🟡, stable. And the THIS WEEK'S DATA zone, marked at the foot: the manager pastes reviews and complaints in under 5 min; where data is missing, the cell says PENDING with the name of whoever brings it.

The full example has 1 more part(s): you see them inside the library, with your account.