Every Monday morning, the same copy and paste
The sales cycle for student beds runs from autumn to September, and every week the owners, the fund or the asset manager want the numbers. Beds let by building and room type, pace compared with last year, rent achieved against budget, nominations, cancellations, pipeline. Someone exports from the booking system, pastes into last week's workbook, fixes the formulas that broke, and adds the nominations figures from another spreadsheet.
By the time the report goes out it is Tuesday, and it is already slightly wrong because bookings kept arriving.
Why the report is harder than it looks
The numbers exist. The problem is definitions and history. Is a booking with an unsigned contract let? Does a nomination count before the student signs? What is "the same week last year" when term started on a different date? Each person who builds the report answers these slightly differently, so the numbers drift from one week to the next.
- Data comes from several exports and a nominations spreadsheet.
- Definitions of let, reserved and cancelled are not written down.
- Last year's comparison depends on a snapshot someone may not have saved.
- Owners each want a slightly different layout.
- Formula errors creep in and are only found when an owner asks a question.
What the manual report costs
A day of skilled time every week is the direct cost. The larger one is decisions made on numbers that are late or inconsistent: pricing changes, marketing pushes and nomination releases timed against a report that was already out of date. And when an owner spots a figure that contradicts last week, confidence in the whole pack drops.
The lettings report we build
- Bookings are read from your booking system every night through its API or a scheduled export, and nominations from the nominations tracker or spreadsheet you keep.
- Your definitions are written down once and applied the same way every time, for example a bed counts as let when the contract is signed and the first payment made.
- A snapshot is saved every week, so pace against the same point last year is always available, aligned by weeks before term.
- The report shows beds let, reserved and available by building and room type, rent achieved against budget, cancellations and nomination status.
- Each owner's pack is produced in their preferred layout from the same numbers, as a live dashboard in Power BI or Looker Studio, a PDF, or a spreadsheet.
- Unusual movements, such as a spike in cancellations at one building, are highlighted for the team before the pack is sent.
| Report item | Built by hand | Built automatically |
|---|---|---|
| Beds let by room type | Export and pivot | Updated nightly |
| Pace against last year | Old workbook, if saved | Weekly snapshots |
| Nominations | Separate spreadsheet | Included |
| Owner layouts | Rebuilt per owner | Generated from one source |
| Checks | When an owner asks | Before the pack goes |
Budgets, targets and pricing decisions remain yours. The report shows the numbers against them.
Monday without the rebuild
The report is ready when the team arrives. Monday morning becomes a review of what the numbers mean rather than a fight to produce them. Owners get the same definitions every week, and questions can be answered by clicking into the detail. When a new building joins the portfolio, it is added to the same report rather than a new tab.
Is your weekly report like this?
- Someone spends most of a day each week building the lettings report.
- Figures change depending on who built them.
- Comparisons with last year depend on old files.
- Each owner needs a separate version.
- Errors are found by owners rather than by you.