Read your first report

Before you start

The first report turns completed live-audit evidence into prioritized issues, screenshots, confidence labels and next actions. Read it before starting fix workflows, ticket exports, monitoring or public sharing. Use this page after the live audit reaches Completed. If the report is still being generated, stay on the report or scan page until the product shows the report is ready.

• Open the private report when the scan finishes.

Read the report summary

Follow the path `Dashboard → Shortcut paths → Get the first useful report → Reports → Report evidence and next action → Private report`.

1. Open `/dashboard` and choose Get the first useful report, or open `/reports` after the live audit reaches Completed. Result: the Reports page shows Report evidence and next action and lists the newest private report for the project with status, issue count and scan context.
2. Choose the newest report for the project. Result: the report opens with the risk score, scanned page count, severity counts and available report actions.
3. Read the summary before changing anything. Result: you understand whether the scan found high-priority issues, evidence gaps or publication blockers.
4. Open the highest-severity issue first. Result: the issue detail shows page URL, evidence text, screenshot or artifact references, severity and confidence labels.
5. Check that the evidence matches the public page behavior you expect. Result: you know whether to start an automated fix task, export a tracker ticket, schedule monitoring or keep the report private.
6. Use public sharing, PDF or export actions only after evidence is complete and the report delivery gate is ready. Result: incomplete evidence does not leave the private workspace.

Review issue evidence

Read the issue evidence as the record of what the scanner saw, not as a generic checklist. The page URL, screenshot, HTML or console/network detail, severity and confidence label explain why the issue exists and what automated next actions are safe. If the report says evidence is pending, wait for the product state to update. Do not treat an incomplete report as final delivery, and do not publish or export findings that still lack the required evidence.

Continue from report evidence

For deeper interpretation, continue to [Understand report evidence](/docs/reports/report-evidence). If eligible findings should become remediation work, continue to [Fix tasks](/docs/remediation/fix-tasks).

Blocked states

• Report not ready means the scan finished but report generation or evidence processing has not completed. Wait or refresh from the report list.
• Report evidence pending means some artifacts are still being attached. Use the available summary but avoid public sharing until evidence is complete.
• Publication blocked means the report has not passed sharing gates. Keep it private and resolve the gate shown in the report.
• Fix action unavailable means the issue lacks plan eligibility, credits, safe access or supported automation. Use ticket-only export or stop.
• A completed scan is required first means the project is still in setup, scope, authorization, billing or evidence collection and should continue from Shortest path to first useful report.