Snapshots and data freshness

Liftrr summarises each period (typically a calendar month) into a stage-score snapshot stored in liftrr_stage_score_snapshots. The dashboard and trend panels read from these snapshots, not from source data.

Why snapshots

• Historical numbers stay stable even when source data is revised after the fact.
• Snapshots are fast to read; the dashboard loads instantly.
• Snapshots record which mapping version was used, so versioned trends are honest.

Open vs closed periods

• The current period is open: its snapshot may be recomputed as new data arrives.
• Closed periods are immutable. Their snapshots are the source of truth for trends.

Freshness label

The dashboard displays an "as of …" label derived from the newest snapshot. If the newest snapshot is older than 35 days, the pilot readiness data-freshness check fails and the operator must investigate.

Recalculating snapshots

SaaS admins can trigger a recalculation from /saas-admin/snapshots/recalculate. Use this after a mapping change or after a large data backfill. Recalculation respects period locks.