Home and Ranking Reports

A self-storage dashboard for every store you run.

Open on the portfolio for the reporting month: occupancy weighted by square feet, rent income, and the work that needs someone, in order of severity. Rankings say which stores lead, which are slipping, and why.

At a glance

  • Verillum AI gives a self-storage company one dashboard for its portfolio, built from the monthly management summaries its stores already file.
  • Portfolio occupancy in Verillum AI is weighted by square feet by default and counts only the stores that reported the month.
  • When Verillum AI does not have a figure, it shows the figure as missing, never as zero.
  • Verillum AI Ranking Reports score each store against peers of its own size, and stores still in lease-up are ranked as their own group.
  • A ranking period published in Verillum AI is frozen, so the month reads exactly as it stood after later reports arrive.

The portfolio, on one screen

An org admin opens on the whole portfolio: occupancy and rent income for the reporting month, each with the number of stores behind it, and a board of stores with their close status and ranking score.

Beside it is one list, Needs your attention, ordered by severity: blocked, then overdue, then incomplete. An unsigned write-up names the oldest store and how long it has waited. An approved rate batch that has not gone out shows the dollars waiting in it.

Everyone starts where their work is

A district or area manager sees up to five stores that need them, one reason each, and lands inside a store with one tap. When nothing needs anybody, the list does not appear.

A store manager opens on the store: six months of occupancy and rent income, leasing activity, tasks and the lien steps coming due. A bookkeeper opens on the invoice queue, and an owner on their own report.

Rankings that hold up in the meeting

Stores are grouped by size, with lease-up stores apart, and scored against their own group, so a large store is never measured against a small one. A missing figure is left out and the weights adjust, and each score says how much of it was measured.

Every row opens into the metrics behind it, so "why am I seventh" has an answer before anyone asks.

Health against fixed lines

A ranking always has a winner, even when every store is slipping. The health score is measured against fixed thresholds instead: healthy at 75 and above, monitor from 60, at risk from 45, critical below that. Each weak signal is named as a driver, so leadership acts on a cause, not a number.

Revenue at risk is the monthly gap to a store's occupancy target at its own achieved rate, shown only when every input is present.

Published means frozen

Rankings recompute as reports arrive. When an org admin publishes a period, it is frozen: a manager scored on March can read March exactly as it stood after April lands, and the screen warns when the live figures have drifted from the published record.

Questions

Which occupancy figure leads?

Square-foot occupancy, by default. It is a company setting, so a company that runs on unit occupancy can lead with units instead. A ranking reads every store on one basis and says which.

What happens when a store is missing data?

It shows as missing. A store that did not report the month is left out of the portfolio figures, and each tile says how many stores it covers. In a ranking, a missing metric is left out and the other weights adjust, so a report format never costs a store its rank.

Who can see the rankings?

Org admins, district managers and area managers. A ranking is internal operations reporting and never appears in an owner report. Store managers, bookkeepers and owners do not see it.

Can a district manager rank just their district?

No, on purpose. A percentile computed inside one district is a different number. A district manager reads the whole portfolio's ranking, so every store is scored against the same population.

Who publishes a ranking period?

Only an org admin, and the database enforces it. The server recomputes the period before freezing it, so the record never depends on what a browser sent. Republishing asks first, because managers were scored on the old one.

See it against your own portfolio.

Tell us how many stores you run and who reports to whom. We stand up a workspace with your property registry already loaded.