How checks work
Flowpane examines the public governance resources of your Site and shows their observed status, findings and score where evidence is available.
The check pipeline
Start a check, review the outcome and open each artefact to understand its findings. Confirm the observation time before using a result in a client review. A sitemap scan examines declared URLs; a Deep Scan provides additional crawl evidence.
Check outcomes
| Status | Meaning |
|---|---|
| Present | The resource was obtained and assessed; findings may still need attention |
| Missing | The expected resource was not found |
| Blocked | A firewall or challenge prevented access |
| Error | The check could not produce a usable current result |
Missing and inaccessible resources are different outcomes. An unavailable score is not a clean bill of health. Review the explanation, correct access problems and check again.
Proposed drafts remain separate from public observations. Publish reviewed changes through your authorised process and run another check.
Checks, crawls and connection
A governance check assesses the supported public artefacts. A sitemap scan reads declared URL inventory; a Deep Scan adds bounded page and link observations. A supported CMS connection adds the capabilities shown for that installation, but is not required to interpret a public-file finding and does not authorise managed changes.
Review run-level completion and individual resource outcomes separately. A completed run can contain Missing or Blocked artefacts. Use the glossary and troubleshooting when labels appear to conflict.