Reliability Score
Summarize verified readiness without pretending one number is the whole product.
Summarize verified readiness without pretending one number is the whole product.
What this feature is for
Reliability Score is an evidence-backed summary of the checks and signals that support a customer or internal release conversation. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A completed audit or check history, a defined scoring scope, and a review date for the evidence shown.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Open the score, inspect the contributing signals, correct any stale or failed evidence, then share the badge only with its scope and timestamp.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
The score should link to the signals behind it and distinguish current evidence from historical context. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Do not use a high score to hide a critical unmeasured path. Add the missing check or disclose the scope in the report.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Reliability Score with Trust Page, Reports, and Full audit. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.