Pack week
Every quarter the performance team emails the heads of service for their numbers. Repairs sends a spreadsheet. Compliance sends a different spreadsheet. Income sends a screenshot. Complaints sends a summary from their log. Finance sends the management accounts. The performance officer pastes everything into the pack template, recalculates the measures, spots that two figures do not agree, and emails everyone again.
The pack goes to the board with a week of work in it and a footnote explaining why one figure is different from last quarter's version of the same thing.
Why the pack is so much work
The data exists in systems. The work is in extraction, definitions and checking. Each service calculates its measures in its own way, often in spreadsheets that one person understands, and definitions drift between quarters.
- Each measure is produced by a different person and system.
- Definitions are written in a guidance document but applied by hand.
- Historical figures are restated when definitions change, without a clear record.
- Checks between related figures, such as voids and rent loss, are done by eye.
- Commentary is written late, after the numbers are finally agreed.
What pack week costs
Skilled staff spend days on assembly rather than analysis. The board receives numbers that are weeks old by the time they meet. Figures that change between versions reduce confidence, and questions from the board lead to more manual digging. With increasing scrutiny from the regulator and tenants, the risk of reporting something wrong matters more.
There is a governance cost as well. When a measure is calculated by one person in a spreadsheet, the board is relying on that person's formulas without knowing it. If they leave, or if an auditor asks how a figure was produced, the answer may be a file with hidden columns and a note that says do not touch.
The performance data layer we build
- Data is extracted regularly from your housing management system, repairs system, compliance system, complaints log and finance system through APIs or reporting databases.
- Each measure is defined once in code, following your written definitions, so it is calculated the same way every time and can be inspected.
- Figures are stored with history, and when a definition changes, both versions are kept and the change is recorded.
- Consistency checks run automatically, for example void numbers against rent loss, or complaint counts against the complaints log.
- The board pack and committee packs are produced from your templates, with the latest figures, trend charts and targets.
- Owners of each area get a prompt to add commentary on their measures, with the figures already in front of them.
- Live dashboards in a tool such as Power BI give managers the same numbers between board meetings.
| Pack task | Today | With the data layer |
|---|---|---|
| Collecting figures | Emails to each service | Extracted automatically |
| Calculating measures | Spreadsheets per service | Definitions applied in code |
| Checking consistency | By eye | Automatic checks with exceptions |
| History | Old packs | Stored with definition changes |
| Commentary | Written late | Prompted once figures are ready |
Which measures you report and how you define them are decisions for you and your board. We implement the definitions you set.
What pack week turns into
The numbers are ready soon after the quarter closes. The performance team spends its time on analysis and commentary. Figures are consistent across packs and quarters. When the board asks a question, the detail behind a measure is a click away rather than a week of digging.
Is this your board reporting?
- Building the board pack takes days every quarter.
- Figures arrive from services in different formats.
- Measure definitions are applied inconsistently.
- Figures change between versions of the pack.
- Board questions lead to manual investigation.