The portfolio view. It serves today's snapshot when it is fresh and recomputes on demand when it is missing or more than three hours old, so the roster is never stale but never recomputes everything on every page load.
Also called: all accounts health · who needs a hand · portfolio view · risk roster
- 1Today's snapshots are loaded in one query for every account.
- 2Snapshots older than three hours are treated as stale and recomputed with bounded concurrency — four accounts at a time — so a hundred tenants stays sane.
- 3Rows carry score, risk, alerts, 7 and 30-day sessions, active days, last active, milestones done of total and the 30-day metrics.
- 4A summary tallies each risk band and total high-severity alerts.
The freshness window and the concurrency bound are both deliberate: recomputing every account on every open would not survive scale, and serving a stale snapshot would make the roster untrustworthy. Demo accounts are excluded entirely — 'every retention number this module computes… is a claim about a paying customer's behaviour. A seeded demo would score however the seeder happened to shape it, and would then sit in the roster and skew the averages beside real accounts.'
- Reviewing account health meant opening each account individually.
- Recomputing everything on demand did not scale.
- Seeded demo data contaminated portfolio averages.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →