________________________________________________________________________________________________________________________
source of business truth used by the entire operation – from the senior leadership team to the venue specific insight shared with GMs.
Context is a vital part of restaurant analytics
A fundamental component of this consolidated data set is GM end of day reporting. Simple to complete, app-based GM logs ensure vital information about events that may have affected performance – such as road works, power cuts, broken dishwashers or an influx of visitors to the town / city for a new event – are automatically appended to any data analytics. This information not only ensures management queries about out of kilter performance can be swiftly answered without time consuming memory searching by GMs but also means the shift or day can be flagged as an anomaly.
Repeated anomalies, of course, become trends – with this insight highlighting, for example, ongoing problems with equipment or a shift in customer behavior that demands further consideration. For one restaurant, one venue reporting both a sales dip and extra positive customer reviews simultaneously was confusing. On the ground context provided by the GM, however, revealed the loss of local customers due to menu changes – hence the overall drop in sales. Without GM feedback, this insight would be completely invisible to head office and could lead to erroneous decision making.
GM logs also deliver essential cross venue insight – for example feedback on a promotion that may be boosting sales but also causing staff problems because it is not easy to deliver. While head office is celebrating the additional revenue, GMs are predicting a spike in staff turnover due to the challenging promotion that will have downstream financial impact. The ability to capture, identify and, hopefully, reverse this
12