Objective
PMI Live Forecast Accuracy helps you review forecast values from selected snapshots alongside the comparison data shown in the report. It supports a practical question: how close was an earlier expectation to the outcome, and where should the forecasting process improve?
Use the view to investigate patterns across dates and departments. A single unusual day should prompt investigation rather than a conclusion about the reliability of every forecast.
Set the review context
Select the property or organizational unit, reporting period and snapshot date. The reporting period identifies the dates being reviewed; the snapshot identifies the forecast position used for the comparison.
Historical dates and future dates need different interpretation. An actual result is an outcome. A future Live Forecast remains an expectation. Check the column heading before describing a difference as forecast error.
Choose what to display
The legacy interface provides Revenue and Labour modes. Available measures include revenue, room nights or other applicable units, guest nights and ARR for revenue analysis, and hours and productivity for labour analysis.
Use View Options to choose data content and the measures required for the review. Options in the interface include Budget or Target, Forecast, Last Year, Live Forecast and Actual/Live Forecast, with availability depending on the view. Snapshot comparisons can use a Days before setting. Show dates adds date detail; MAD and MAPE can be displayed where applicable.
MAD expresses the size of deviations in the relevant measure’s units; MAPE expresses deviations as a percentage. Interpret them with the scope and underlying observations in mind. Low-volume or zero-actual periods need particular care.
Run a useful review
- Choose a completed period with sufficiently complete actual data.
- Select one department or a clearly defined group and one measure.
- Set the forecast snapshot or comparison horizon you intend to assess.
- Review the summary, then show dates to find where differences concentrate.
- Check import completeness and unusual operating events before attributing the difference to forecasting decisions.
- Agree a practical action, such as a regular review of event assumptions or earlier investigation of missing data.
Example
At Demo Hotel A, the team reviews room revenue for a completed week using an earlier forecast snapshot. Most days are close to the outcome, but one event date differs substantially. The team checks the booking changes and actual imports for that date before deciding how to improve the next review.
Common checks
If the result seems inconsistent, confirm the snapshot, period, department, measure and comparison content. Avoid comparing an earlier forecast for one report with today’s Live Forecast in another. When escalating a question, include these selections and the affected dates; share customer details only through the approved support channel.