# Cloudbeds Trend Reporting Workflow

## Objective

Build a repeatable occupancy reporting system that:
- captures the newest Cloudbeds occupied-room report
- archives daily XLSX files in a consistent location
- parses daily occupied-room counts
- compares latest versus previous day
- builds rolling daily / weekly / monthly / quarterly summaries
- emails a report every morning at 7:55 AM America/Chicago

## Reporting cadence

### Daily
- latest report freshness
- today vs yesterday occupied-room total change
- notable property movers if historical data exists

### Weekly
- rolling 7-day occupied-room trend
- strongest and weakest properties over the last 7 days
- variability / consistency notes

### Monthly
- rolling 30-day trend
- property contribution patterns
- directional notes

### Quarterly
- rolling 90-day view
- broad portfolio movement
- concentration and scale notes

## Required storage convention

Store parsed daily reports under:
- `reports/cloudbeds/raw/occupied-room-count-YYYY-MM-DD.xlsx`

Store parsed JSON snapshots under:
- `reports/cloudbeds/parsed/occupied-room-count-YYYY-MM-DD.json`

Store generated trend briefs under:
- `reports/cloudbeds/output/`

## Daily pipeline

1. identify latest Cloudbeds occupancy email
2. extract latest link
3. obtain latest XLSX (directly or via local saved file flow)
4. archive today’s XLSX with standard filename
5. parse to structured JSON
6. compare with historical parsed snapshots
7. generate report body
8. send to Bill with CC to Bob

## Important operational note

Trend reporting is only as good as file capture consistency.

If the daily XLSX is not captured reliably, the system should:
- still send a daily report
- clearly mark trend confidence as partial
- use the latest available historical snapshots

## Best future upgrade

Make the XLSX download fully automatic so the reporting chain no longer depends on manual saves from LibreOffice or Downloads.