Generate, review, and share reports

Open the dated analysis and review its context and evidence. The run button remains unavailable while the report is approved, another run is active, or no GA4 reports have been collected.

Before selecting Run analysis, confirm:

• the organisation profile, goals, constraints, and stakeholders are current;
• the analysis period is correct and its context explains changes, issues, and seasonality;
• GA4 reports exist for the saved period, and Search Console reports are present where relevant;
• heatmaps, sitemaps, and additional evidence have useful dates, sources, and notes;
• important pages have heatmap evidence when page-level interaction or visual-friction findings are needed; and
• the billing owner has at least one available analysis unit.

1. Select Run analysis.
2. UX Robot reserves one available unit before dispatching the report-generation request.
3. The page shows Queued or Processing and refreshes while the provider response is checked.
4. The unit is consumed only after a valid structured report is stored. If the run fails, the reservation is released and the balance is not reduced.

When processing completes, review the generated report from beginning to end. Check the executive summary, evidence interpretation, strengths, friction, opportunities, recommendations, confidence, priorities, and any comparison with the previous report.

• Trace important claims back to GA4, Search Console, heatmaps, uploaded evidence, goals, or known context.
• Check that page-level interaction and visual-friction findings are supported by heatmap CSVs, screenshots, or recording observations.
• Check that missing heatmap evidence is identified as a limitation instead of being replaced with assumptions about public pages.
• Check that the date range and comparisons are described correctly.
• Look for unsupported certainty, invented facts, misleading causation, or a recommendation that conflicts with a recorded constraint.
• Confirm that personal or sensitive information has not been unnecessarily reproduced.
• Check that priority and effort are practical for the organisation.

If the draft is not ready, correct the organisation or analysis context and run it again only when a new full generation is justified. AI can make mistakes; human review remains required.

Select Approve and save report when the current result is the version the organisation should retain as its historical record.

1. Confirm the analysis name, period, readiness information, and generated report.
2. Select Approve report and read the permanent-lock warning.
3. Select Approve and save report to create the approved snapshot.

Approval is permanent for that analysis. The analysis becomes locked: its setup and evidence cannot be edited, and the report cannot be rerun. Create a follow-up analysis when new evidence or a later period should be assessed.

Stakeholder delivery is available after the full report is approved.

1. Open the approved analysis and select Generate stakeholder report.
2. Open Stakeholder report and review the shorter summary for clarity, accuracy, and appropriate language.
3. Return to the organisation’s Stakeholders section and confirm each intended recipient has a correct email and is marked to receive reports.
4. Select Send stakeholder report, review the recipient count, and confirm Send emails.

Each selected stakeholder receives private links to the stakeholder summary and full approved report. Recipients should not forward those links outside the authorised audience. Sending is queued, so delivery may not be instantaneous.