How Often Should Hospitality Forecasts Be Refreshed?

Hospitality forecasts should be refreshed at three speeds. Update the short-term forecast every day as actual takings and wages land, review the next one to two weeks each week before rosters and orders are locked, and reforecast the month and full year each month after the close. Refresh straight away when something material changes, such as a venue closure, a major event or a price change.

Why refresh frequency matters#

A forecast that is only updated at budget time stops being useful within weeks. Trading in Australian clubs and pubs moves with school holidays, public holidays, weather, sporting finals and local events. If the forecast does not move with it, managers roster against a number they know is wrong, and finance reports a variance to budget that everyone already expected.

Refreshing too often without good data has its own cost. If the forecast changes every time someone edits a spreadsheet, nobody trusts it. The right cadence depends on how quickly actuals arrive and what decision the forecast supports.

A cadence that matches the decisions#

Horizon	Refresh	Decision it supports	Who owns it
Today and tomorrow	Daily, from live trading	Floor staffing, sending staff home, cash orders	Venue manager
Next 1 to 2 weeks	Weekly, before rosters close	Rosters, stock orders, function staffing	Venue manager with finance
Rest of the month	Weekly	Month-end expectations, wages against revenue	Financial controller
Full year	Monthly, after the close	Budget variance, cash flow, board reporting	Financial controller and owners

Same-day hospitality forecasting is the fastest layer. As the POS records trade during the day, the forecast for the rest of the day should adjust. A quiet lunch on a wet Wednesday is a signal to adjust the evening roster, and the manager needs that signal before the evening shift starts.

The weekly review is where most labour cost is decided. Rosters for the next week or two are built from this forecast, so refresh it before the roster deadline, not after.

The monthly reforecast keeps the year honest. After each month closes and the reconciled actuals are in, update the remaining months. Boards get a current view of where the year will land instead of a comparison with a budget set months ago.

Triggers for an immediate refresh#

Some changes justify a refresh outside the normal cycle:

• A venue closes for renovation, or reopens
• A new venue joins the group
• A large function is booked or cancelled
• Prices change across the menu or bar
• Opening hours change
• A regulatory change affects gaming hours or venue trading

Record the reason each time you refresh outside the cycle. Later, when someone asks why the forecast moved, the answer is written down.

What makes frequent refreshes possible#

Daily or weekly refreshes only work if the actuals arrive without manual work. If the forecast waits for an administrator to finish the takings spreadsheet, it can only ever be as current as that spreadsheet. The forecast also needs wages, not just revenue, because the decision most forecasts support is how many staff to roster.

This is where connected data matters. When POS, gaming, workforce and cash-handling data feed one record, the forecast can compare itself with actuals every day. wirely.ai's reporting and forecasting update describes longer forecasting windows, tracking actuals against budget, and showing labour against revenue in the same view. wirely.ai connects the systems venues already use, so actual takings and wages reach the forecast without exports.

The parent guide on live hospitality group performance compared with month-end reporting covers why waiting for month-end slows decisions. To decide where the forecast should sit on screen and what to show next to it, see what a hospitality venue performance dashboard should show. For the full picture, read the complete guide to connected hospitality financial operations.

Variations for different operators#

Single venues. A single pub can often combine the weekly review and the rolling month into one weekly session with the manager and the bookkeeper.

Multi-venue groups. Use the same refresh calendar at every venue so the group forecast is assembled from forecasts of the same age. A group total built from one venue updated yesterday and another updated three weeks ago is unreliable.

Clubs with boards. Align the monthly reforecast with the board pack so directors see the reforecast alongside the month's actuals. Financial controllers can then explain the variance once instead of twice.

Seasonal venues. Venues with a strong summer or winter season should refresh weekly through the peak, when small changes in trade have the biggest effect on the year.

Frequently asked questions#

Is a monthly forecast refresh enough for a hospitality venue?#

Monthly is enough for the full-year view and board reporting. It is too slow for rosters and ordering, which need a weekly review of the next one to two weeks and a daily check against live trade.

Should forecasts include wages as well as revenue?#

Yes. Most forecast-driven decisions in a venue are about labour. Forecasting revenue without wages tells a manager how busy the venue will be but not whether the roster fits.

What data do I need to refresh a forecast daily?#

Actual takings by department, wages worked, and the same period last year for comparison. If these arrive automatically from connected systems, a daily refresh takes minutes.

Who should own the forecast?#

Venue managers own the short-term forecast because they act on it. The financial controller owns the monthly reforecast and the group roll-up.

Build a forecast your managers will use#

If your forecast only changes at budget time, book a demo. Bring your current budget template and roster process, and we will show how live actuals and wages could keep the forecast current at every venue.