Signal over opinion

Methodology

Every evaluation dimension in RBSI is answerable from observable, time-stamped signals. Qualitative judgement is never excluded — it is anchored to something observable.

The signal taxonomy

12 categories. 44 sub-categories. 62 signal types. 500+ sources.

Signals are the raw material of brand intelligence — typed, observable market events carrying information about a brand's commercial state or trajectory.

CodeCategoryCore question
SC-01Physical & Retail PresenceWhere is the brand physically present, and how fast is it expanding?
SC-02Financial, Funding & CorporateWhat is the brand's financial health and ownership trajectory?
SC-03Hiring & OrganisationalWhat does hiring reveal about future strategy?
SC-04Digital & Online PresenceWhat does the digital footprint reveal about commercial health and intent?
SC-05Physical Retail Strategy & ActivationHow is the brand approaching physical retail expansion?
SC-06Consumer Culture & DemandWhat do consumers aspire to and demand?
SC-07Consumer Verdict & Brand EquityWhat do consumers think the brand is worth?
SC-08Press, PR & Earned MediaWhat narrative surrounds the brand?
SC-09Legal, Compliance & RegulatoryWhat is the brand's legal standing and market readiness?
SC-10Supply Chain & WholesaleHow does the brand operationally enter and supply markets?
SC-11Innovation & Forward TrajectoryWhere is the brand strategically heading?
SC-12Cultural Relevance & SeasonalityHow aligned is the brand with local culture and timing?

Get the full document

Download the RBSI framework.

The complete methodology, scoring architecture, and governance model in a single reference document.

The signal event model

Every signal is a typed event, not a static attribute.

Signal type
Classification within the taxonomy — e.g. Trademark filing.
Timestamp
Date and time of detection.
Source
The originating data provider.
Source reliability
Provider reliability score, 0–100.
Freshness
Days elapsed since the event occurred.
Confidence
System confidence in the interpretation, 0–100%.
Evidence count
Number of corroborating data points.
Visibility type
Quiet, semi-public, or public.
Intent strength
Low, medium, high, or very high.
Signal earliness score
How far in advance of market activity this signal type typically appears.

The confidence envelope

No score without its confidence.

Every output — and every underlying reading that feeds it — carries a confidence envelope: confidence score, evidence count, source reliability, freshness index, and volatility flag. A reading at 91% confidence is a fundamentally different signal from the same reading at 54% confidence.

What the framework does not do

Boundaries, stated plainly.

It does not make leasing decisions

Leasing systems that consume RBSI outputs apply their own site-fit logic on top — footfall counts, void analysis, lease economics. The framework evaluates brands; site decisions are downstream.

It does not value companies

RBSI outputs are relative index readings, not a DCF model, a transaction multiple, or an audited valuation. They inform valuation thinking — they do not replace it.

It does not predict consumer behaviour

It reads signals of consumer activity and translates them into intelligence about equity and demand. It does not model individual purchase decisions.

It does not replace expert judgement

It structures and evidences analytical judgement. The framework does not produce conclusions on its own.

Versioning

A living standard, reviewed on a fixed cycle.

Annual review
Formally reviewed once per year, incorporating validated prior-year outcomes, expert practitioner input, and market development.
Major versions (1.0, 2.0)
Structural changes to pillar architecture, scoring dimensions, or foundational principles.
Minor versions (1.1, 1.2)
Signal taxonomy, source methodology, or weighting-parameter updates.
Patch versions (1.1.1)
Corrections to definitions or examples.
Backward compatibility
Historical scores are never retroactively revised — the version under which they were produced is always recorded.
Public change log
Every version change is documented publicly: what changed, why, and what evidence or expert input prompted it.