Product tour

One estate, three screens, no screenshots

Every panel below is rendered by the code that renders the product, on the estate you can open in the next click. Harbourline Retail is a fictional retailer with 100 Power BI reports — synthetic from top to bottom, regenerated every day, read-only to everyone.

Today it holds 50 healthy, 16 at risk, 21 underused, 5 orphaned, and 8 it declines to judge at all. 42 of the 100 need a decision this week.

1 · The board

The list is ordered by what to do, not by what happened

Reports that need a decision come first, in the engine's own severity order. Everything else is below them, including the reports we cannot judge yet — which is a section, not a footnote.

Needs action (42)

StatusReportOwnerBreaches
At riskReplenishment Exceptionshenrik.dahl@harbourline.exampleRefresh failures Freshness
UnderusedCopy of Group P&L (do not use)Usage Ownership
OrphanedCost Centre Drilldown (legacy)Ownership

…and 39 more.

Watching (58)

StatusReportOwnerWhy not judged
Insufficient dataGateway Healthviktor.novak@harbourline.exampleNo refresh outcome has ever reached us for this one. The expectation stands; the verdict waits. It is not stale, and it is not fine.

Real rows from the demo estate, in the product's own markup. The live board writes the engine's own sentence of evidence in the last column and links every row to the report behind it.

2 · The evidence

Every verdict names the contract version that produced it

A health state you cannot interrogate is a number to argue about. Open a report and you get the expectation it was held to, rule by rule, the finding against each one, and the history of every state it has been in.

Replenishment Exceptions At risk

RuleExpectationFinding
Refresh failuresNo more than 2 consecutive refresh failuresBreached
FreshnessA successful refresh within 24hBreached
LatencyNo expectation declared
UsageAt least 5 unique viewers in the last 30 daysMet
OwnershipAn accountable owner mappedMet

The workspace default contract of the demo estate, worded exactly as the contract screen words it — because it is the same code. Editing it appends a version; nothing is ever corrected in place, and a report judged under an older version says so.

3 · The digest

The weekly email is the product for most people

One message per week per person, scoped to the workspaces their account holds: what needs action, what changed state since last week, and what we still cannot judge. Every row links straight to the report it is about.

The counts are complete even when the list is trimmed — a digest that under-reports to stay short would be the same lie as a false green.

The first digest is a baseline, not an alarm: it says what your estate looks like now, so the second one can say what moved. There is no inbox ceremony to set up and nothing to acknowledge.

It renders on the same design as the board, in HTML and in plain text, with no images and no tracking pixel — several of the clients this lands in would strip them anyway, and we would rather not know when you opened it.

4 · What we cannot see

A new workspace warms up in stages, and says which one it is in

Inventory and ownership land in the first scan, within minutes. Refresh outcomes follow. Usage is last, because a viewer minimum over a window we have not watched from the beginning would be a guess — so until we have watched a full window, nothing in that workspace is called underused. Ever.

Warming up

A stage still arriving is shown as arriving, with the date it will be complete where the date is knowable.

Not available

Where a feed tells us it cannot collect — a Tableau site without Admin Insights, say — the stage reads Degraded and stops promising that waiting will fix it.

Rejected input

Malformed telemetry is quarantined and counted on the board, never silently dropped. You can see how much of it there is.

Click the estate yourself

Same board, same verdicts, nothing you can break. When you are ready, the connect walkthrough for your own workspace is one page.