Claim denial tracker
Claim denials tracked end to end: authorization issued → denied item (with reason and amount) → appeal → outcome (recovered or lost). Every step is dated, and the money in dispute never disappears from view — the panel shows how much is open, under appeal, recovered, and lost. Register insurance pl…
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Reassess
The list shows
VerticalTemplateDemo tenantMain screenExposureAcademy pathReadiness
Form fields
Nome
Descrição
Endereço de destino
Dhcadastro
Ativo
Ícone
Ordem
Visivelmenu
Visivelmenulateral
Visivelmenutecnico
Visivelconfiguracao
Permiteatalho
Grupoatalho
Ordematalho
Tabela
Grupomenu
Destinomenu
Perguntadono
Sinonimos
Eixossecundarios
+ 2 more fields
Start here
A matriz "zero não"
By vertical, the four checks that keep it standing: does it have a seeding template? does it have a demo tenant? does the main screen open? is it recording exposure? Everything read from the actual state of the system, nothing declared by hand. Read-only screen — nothing is changed here.
What this screen is
The "zero no" scoreboard for the platform's 5 verticals (PSA/software house, field services, retail/rental, health/clinic and light industry). For each one, the minimum checks that keep it standing: does it have a seeding template? does it have a demo tenant? does the main screen open? is it recording exposure? A vertical only counts as ready when it passes all applicable checks. Read-only/aggregation — nothing is changed here.
How to
Os estados da coluna Exposição
"n/a" = exposure is not within the scope of workstream B in that vertical (it does not count against it). "pending (workstream A)" = the exposure foundation is not yet integrated at runtime. Green = actually recording. Red = should be recording and is not.
Reassess
Re-queries the actual state now. Since the reading comes from configuration and not from a document, turning on a key or seeding a demo changes the scoreboard on its own — Re-evaluate only forces the re-reading right away.
Rules
PRONTO é zero "não" — um único não derruba
A vertical is only ready when it passes ALL applicable checks. The screen does not average: 3 yes and 1 no is "1 no", in red. It is deliberate — a half-ready vertical sold as ready is the partner discovering the gap in front of the customer.
Frequently asked questions
Para que o placar serve na prática
It is a vertical's go-live gate and the same matrix that the partner Enablement Kit checks in its checklist: a partner only becomes qualified in a vertical that has zero "no". If the cycle's goal is to open a new line of business, this is the screen that says what is missing.
Which question this screen answers
Is each of the platform's verticals standing — with template, demo, screen and exposure? For the 5 verticals (PSA/software house, field services, retail/rental, health/clinic and light industry), the scoreboard answers the minimum checks: does it have a seeding template? does it have a demo tenant? does the main screen open? is it recording exposure? READY is zero "no" — a single no brings the vertical down. It is reading and aggregation: nothing is changed here; Re-evaluate only redoes the measurement.
Was this article helpful?
In the same module: Inteligência da rede2
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.