Method · 16 of 18
Every number on this console, defined
Written to be read by somebody who will be asked to defend it to an analyst on a results call. If a figure cannot be explained in a sentence, it should not be on the screen.
Total definitions
20
Every figure shown anywhere on this console
Measured
11
▲ 55%share of all definitions
Modelled
8
▲ 40%share of all definitions
Assumed
1
▲ 5%share of all definitions
Composition of the console
Measured, modelled or assumed
20
Definitions
Where the inputs come from
A definition can draw on more than one source — a modelled figure is still typically anchored to at least one measured input.
Metric definitions
Searchable glossary — every figure on the console, defined
| What it counts | |||
|---|---|---|---|
| 100 basis points | One per cent of operational beds. At 133,600 beds that is 1,336 beds. | Measured | |
| Competitive pressure | Times a competing operator was named in a conversation, weighted by the share of those conversations not won. | Modelled | |
| Contact role verification | Whether the person on the call appears on a public filing as a director, designated partner or authorised signatory. | Measured | |
| Enquiry | One inbound expression of interest, from any channel, de-duplicated on contact and family within 30 days. | Measured | |
| Entity resolution | The family named on the call matched to a CIN or LLPIN on the statutory register, with the match confidence recorded. | Measured | |
| Expansion score | A 0 to 100 composite of headcount signal, stated bed need and same-building capacity. | Modelled | |
| Forward occupancy | Modelled occupancy at 30 and 90 days, decomposed into five components. | Modelled | |
| Growth centre | A centre open 24 months or less. Reported separately from mature centres everywhere on this console. | Measured | |
| Live requirement | A stated bed count, a stated micro-market and a stated move-in window, all three captured in the same conversation. | Measured | |
| Portfolio occupancy | Occupied beds divided by operational beds, across all centres including those opened this quarter. | Measured | |
| Reached | A two-way conversation took place. Not a dial, not a ring-out, not a voicemail, not a delivered message. | Measured | |
| Renewal gap | Accounts carrying a healthy rating on file whose stated intent on the call was contraction or exit. | Modelled |
Collection
- Inventory and CRM. Read directly. Read-only until you switch writing on.
- Conversations. Every call and message recorded, transcribed and scored. Retained per your policy, not ours.
- Channel feeds. Site, app, portals, referrer submissions, walk-ins, the enquiry line.
- Trigger sources. Public filings and announcements, licensed property data. Never scraped personal data.
Processing
- Extraction. Requirement fields pulled from the transcript, then written as structured data, never as free text.
- Clustering. Topics formed from what patients actually said, not matched against a fixed keyword list.
- Scoring. Per conversation, in the language it happened in. Kannada and Hindi scored natively, alongside English.
- Thresholds. Nothing reported below 30 conversations for a centre in a window. The sample cannot carry the claim.
Known limits of this build
- 16 of 31 Bengaluru centres loaded
- Micro-market map is schematic, not geographic
- Realisation per bed is assumed, not disclosed
- Voice-verified intent is not yet back-tested against outcomes
- Confidence band on the 90 day forecast is itself an estimate
How to read the class tags
Measured — counted from a system of record
11 of 20Reproducible without this console. If your CRM or inventory system disagrees with this figure, the system of record wins.
Modelled — derived by a stated, fixed rule
8 of 20Built from measured inputs through a published formula. The rule does not change silently between releases.
Assumed — an input we do not have
1 of 20A value chosen in the absence of disclosure, flagged here and carried through to the assumption ledger for scrutiny.
Standing statement
Read-only on day one
Read-only on day one. Nothing is written back to your systems until you switch it on.
The layer proves itself against live data before it changes anything. This is on the console rather than in a contract because a contract does not travel into a meeting, and because a commitment written into the interface is harder to quietly relax than one written into a slide.