Reports
Package the evidence a teammate, customer, or auditor needs to review.
Package the evidence a teammate, customer, or auditor needs to review.
What this feature is for
Reports turns stored checks, incidents, revenue traces, and deployment evidence into a scoped artifact. It is designed for sharing without giving away the entire workspace. 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 question the report must answer, a date range, an app scope, and a reviewer who can confirm sensitive fields are excluded.
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
Choose the evidence set, preview the report, remove irrelevant or sensitive details, export the format your recipient can use, and keep the source run in PreFlight.
- 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 report records scope, capture time, included signals, pass or fail state, and a stable reference back to the originating evidence. 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
A report that is stale or too broad can mislead. Regenerate after a material release and keep the source timestamp visible.
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 Reports with Activity, Reliability Score, and Trust Page. 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.