> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/use-cases/hospitality-groups-multi-venue/group-level-consolidated-reporting.md).

# Group-Level Consolidated Reporting

This use case explains how to build group level consolidated reporting across multiple venues for hospitality groups in Model Reef.

You will:

* Aggregate venue level P\&Ls into regional and group views.
* Combine venue results with any central or head office costs.
* Build dashboards and packs for group management and investors.
* Use scenarios to test portfolio and strategy changes.

Model Reef is not a statutory consolidation system. It is a planning and management reporting environment built on driver based venue models.

## When to use this pattern

Use this pattern when:

* You operate multiple venues, sites or brands.
* You want consistent group level reporting across the portfolio.
* You need to integrate site level plans, central costs and funding.
* You want scenario based group views for decisions and stakeholder communication.

It sits on top of:

* Venue Level Forecasting Pack
* Promotions and Margin Sensitivity
* Staff Rostering and Labour Planning
* Build a Consolidated Forecast Model

## Architecture overview

Group level reporting uses:

1. Branch hierarchy
   * Venue branches for each site.
   * Regional branches aggregating venues.
   * Group branches for corporate and head office.
2. Category alignment
   * Shared Revenue, COGS, Staff and Opex categories.
   * Common KPIs and ratio definitions.
3. Consolidated reports and dashboards
   * Group P\&L, Balance Sheet, Cashflow and Cash Waterfall.
   * Regional and brand segment views.
   * KPI dashboards for margins, staffing and cash.
4. Scenario overlays
   * Alternative portfolios, pricing strategies and labour models.
   * Expansion, refurbishment or closure plans.

{% stepper %}
{% step %}

### Confirm branch and category structures

Ensure that:

* Each venue is a branch with a consistent template of variables.
* Regions, brands or concepts have parent branches as appropriate.
* Head office functions have their own branches for central costs.
* All branches share common category structures for P\&L lines.

This enables Model Reef to roll venue results up to regions and then to the group while keeping consistent report layouts.
{% endstep %}

{% step %}

### Build core group P\&L, balance sheet and cashflow views

Use the reporting system to build:

* Group P\&L that aggregates all venues and head office.
* Regional P\&Ls by filtering reports to regional branches.
* Brand or concept P\&Ls where relevant.
* Group Cashflow and Cash Waterfall reflecting all venues, capex and funding.

Check that:

* Revenue and cost categories line up for meaningful comparisons.
* Head office costs are visible and separated from venue level costs.
* One off items such as refurbishments or closures are clearly flagged.

This provides a core set of group reports that all stakeholders can use.
{% endstep %}

{% step %}

### Create dashboards for group and segment KPIs

Build dashboards for:

* Revenue and EBITDA by region, brand and group.
* Gross margin, labour cost and rent cost percentages.
* Capex and refurbishment spend.
* Cash balance, headroom and key funding metrics.

For each dashboard:

* Use filters for region, brand and venue type.
* Allow users to switch scenarios.
* Provide drill down from group metrics to regional and venue level views.

This turns the multi venue model into a management cockpit for the group.
{% endstep %}

{% step %}

### Integrate central and shared costs

Add central cost branches for:

* Group management and administration.
* Marketing and brand support.
* Shared services such as HR, IT and finance.
* Property and lease management where centralised.

Decide how you want to present these in group reports:

* As central cost lines separate from venue performance.
* Allocated back to venues or regions using drivers such as sales, seats or staff count.
* Both, via alternative reporting views.

Implement allocation using driver based formulas so that allocations scale with portfolio changes in scenarios.
{% endstep %}

{% step %}

### Use scenarios for portfolio and strategy decisions

Clone the base model into scenario models to explore:

* Opening new venues in specific regions.
* Closing or refurbishing underperforming sites.
* Changing pricing, promotions or operating hours.
* Adjusting labour models or staffing targets.
* Changing rent structures or property strategies.

In each scenario, adjust:

* Venue level revenue and cost drivers.
* Central cost levels and allocation rules.
* Capex plans and funding assumptions.

Compare scenarios using:

* Group level EBITDA and margin profiles.
* Cash and funding requirements.
* Portfolio composition and performance by region and brand.
* Valuation metrics if you use the valuation engine for group level analysis.
  {% endstep %}
  {% endstepper %}

## Check your work

* Group level results reconcile with recent management accounts when historic drivers are applied.
* Segment views match internally recognised brand, region and venue groupings.
* Central costs are treated transparently and consistently.
* Scenario outputs support real decisions, not just additional complexity.

## Troubleshooting

<details>

<summary>Consolidated numbers differ from accounting reports</summary>

Reconcile starting balances, ensure all venues and central costs are represented, and confirm that any non trading items from statutory accounts are treated appropriately in the planning model.

</details>

<details>

<summary>Segment reports are hard to interpret</summary>

Simplify category structures, ensure naming is consistent, and create a small set of standard views for regular use.

</details>

<details>

<summary>Model performance slows with many venues</summary>

Use representative venue cohorts for long range planning and reserve detailed per venue forecasts for near term horizons.

</details>

## Related guides

* [Build a Board Reporting Pack](/how-tos/dashboards-and-reporting/build-a-board-reporting-pack.md)
* [Build a Consolidated Forecast Model](/how-tos/core-modelling/build-a-consolidated-forecast-model.md)
* [Notes & Comments](/help/permissions-and-collaboration/notes-and-comments.md)
* [Entering Schedules](/syntax/how-input-fields-work/entering-schedules.md)