Read your fleet's health on FleetHQ
Before you begin
You need access to the Fleet Success scorecard to see the score band, and View FleetHQ to see the insights workspace. These are separate, so you may have one without the other. FleetHQ must be enabled for your organization.
This scenario needs your fleet to have at least one published finding. If the workspace says "No insights right now — your fleet is on baseline", read through the steps anyway — but you won't be able to perform steps 6 to 9 until FleetHQ publishes something.
What you will accomplish
You'll read the score band and understand what its coverage labels mean, then follow a weak pillar to the finding FleetHQ ranked first.
Steps
Open Home. The page is titled FleetHQ.
Read the Fleet success score, and note its Updated on date. That date is the last successful FleetHQ run for your organization — not the moment you loaded the page.
Choose the scorecard period you want to review.
Read each of the four pillar scores: Stakeholder Satisfaction, Intentional Culture, Resource Efficiency, and Risk Management.
Read the reporting label beneath each pillar — either Not reporting or a count in the form {reporting} of {possible} reporting. Treat it as part of the score, not as a separate warning beside it.
Find a pillar row carrying an insight-count chip, and select the chip. FleetHQ moves you to that pillar's highest-priority visible finding.
In Insights and recommendations, compare the findings you can see — their severity, metric name, pillar, age, and action progress.
Select a finding. Its recommended plan appears beside the list.
Select View metric, where the link is offered. The Fleet Success metric behind the finding opens and is highlighted, so you can see the number the finding is talking about.
What you just did
You read the two halves of the page and connected them. They are not the same thing: the score band summarizes the Fleet Success metrics you record, and the workspace holds the findings FleetHQ published after evaluating those metrics. A low score is not automatically a finding, and an empty findings list does not mean every pillar is healthy. The coverage label in step 5 is the part most people misread. Missing metrics count as zero in a pillar score, so a pillar reporting three of eight metrics is not showing you a partial picture of a bad result — the missing five are already inside the number. One warning worth carrying: if the workspace shows a load error rather than an empty state, that is not an all-clear, and you have not seen your findings.
Next steps
Check the evidence behind an insight — look at what FleetHQ actually measured before you act on it.
Review fleet health and prioritize an insight — the full task, including the queued-findings behaviour and the empty states.
What FleetHQ is — why the scorecard and the findings share one page.