Generate, review, and share reports

Open the journey analysis and select Start autopilot. UX Robot first collects the connected GA4 and Search Console reports for the saved evidence period. Starting and saving this evidence does not use an analysis unit.

Before starting, confirm:

• the organisation profile, goals, constraints, and stakeholders are current;
• the journey brief describes the visitor, the task, what success means, and a safe stopping point;
• the correct GA4 property is connected, and Search Console if you use it;
• whether this website has Microsoft Clarity heatmaps and, if it does, which project contains them;
• if This journey requires sign-in is on, the engineer has signed in to the website in that same browser profile; and
• the billing owner will have one available analysis unit when final report generation begins.

1. Select Start autopilot. The evidence checkpoint asks whether heatmaps are available. Answer yes to add Microsoft Clarity collection to this journey, or no to continue without it. The page then shows a generic progress stage while server evidence is collected and the journey test is planned. During a long task, Still working, elapsed time, and the last saved activity time continue to update even when the evidence percentage cannot move.
2. When Desktop step ready appears, select Open desktop handoff. If this computer is not connected yet, open Settings → Desktop connections, give the computer a recognisable name, and select Connect a desktop. Copy the connection instruction into Codex or Claude once. If the computer is already connected, do not create another credential.
3. Copy the run instruction into the connected desktop AI. A connection is reusable, but the run instruction identifies one analysis and run, so copy a fresh run instruction for every new journey or chat. The desktop AI completes the journey on the website, performs safe interaction and usability checks, and saves a checkpoint after each coherent chunk. When heatmaps were selected, it also gathers the relevant Microsoft Clarity evidence. It captures screenshots for each meaningful journey stage, useful patterns, and interface failures; it does not capture Clarity or analytics dashboards.
4. If the computer closes or the session stops, open the same handoff and copy the instruction again. The desktop agent resumes from the saved checkpoint instead of repeating completed work.
5. After the evidence set is complete, UX Robot automatically reserves one available unit and starts the powerful server-side report model. The desktop model gathers and records evidence; it does not write the final report.
6. The unit is consumed only after a valid structured report is stored. If generation fails, the reservation is released, the collected evidence remains safe, and Retry report preparation becomes available.

You do not need to keep the UX Robot page open. Server collection and report generation continue in the background. The desktop AI needs to remain available while it carries out the journey and, when selected, the behaviour-evidence step. UX Robot emails both the person who started the run and the organisation owner when report generation finishes, with a link straight to the report. When the same person is both, only one email is sent. If generation fails, that email explains what went wrong and confirms that no analysis unit was used.

A journey report that recommends visible changes adds one more desktop step after the report is written. The analysis page shows Make the after pictures. Open the same handoff and copy the run instruction, or select Skip after pictures. The draft report can be read in the meantime, and approval waits until the step is finished or skipped. See Journey analyses for the full journey method.

When processing completes, select Read report to open the dedicated reading view. Start with the 30-second assessment, then the evidence-informed journey map, the stages, and the priorities. Each priority says what to change, where, why, and how you will know it worked, and is labelled Measured or Observed only so you can see which ones your evidence backs.

Every analysis row, analysis page, journey report, and stakeholder summary shows Created and Last run. These timestamps use the timezone saved in the organisation profile and include its current timezone abbreviation. Last run means when the latest full autopilot run started. An analysis that has never run says Not run yet.

The Performance chapter keeps real-user Chrome UX Report results separate from simulated Lighthouse diagnostics and shows unavailable or failed checks instead of hiding them. Readiness says whether the evidence can support a decision; it measures evidence completeness, not whether visitors succeed.

Every organisation is paired with a dedicated UX Robot engineer who can learn its goals, website, evidence history, and previous decisions. If you do not have an internal UX team, the engineer can help explain findings, prioritise work, run workshops, review proposed changes, and check whether completed work improved the experience. If you already have a UX, product, design, or digital team, the engineer can add focused capacity where it is most useful.

The report speaks to the website owner in plain, constructive language. Each explanation should stand on its own without requiring you to understand how UX Robot collected the evidence. Strengths show what to build on, findings explain the opportunity they create, and recommendations give an achievable next step without hype or unsupported promises.

Screenshots show the exact tested viewport with the affected control outlined. The highlight comes from the element bounds recorded in the same browser state, not from a later AI guess, and UX Robot keeps the untouched source image separately. Screens containing personal, authentication, payment, confidential, or signed-in third-party information are not captured; the agent must save that exception explicitly, and the report identifies the page area in words.

• Trace important claims back to GA4, Search Console, Clarity, browser observations, or known context.
• Check that each source keeps its proper role: search demand, on-site behaviour, and interaction evidence are related without claiming that one caused the other.
• Check that a priority labelled Measured really cites a measure, and that the figures describe the journey’s pages.
• Check that missing evidence is identified as a limitation instead of being replaced with assumptions.
• 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.
• Open each highlighted location and confirm that the outline identifies the issue described by the finding.
• Check that priority and effort are practical for the organisation.

If the draft is not ready, correct the brief 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, 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 brief and evidence cannot be edited, and the report cannot be rerun. Create a follow-up analysis when the journey should be tested again. Approval also starts writing the stakeholder summary.

Download PDF and Copy for AI are available on every finalised report. They are also available on a completed draft that can be approved: marked ready, with finding-specific screenshots, and a readiness score strictly greater than 60%. A score of exactly 60% does not qualify.

• Download PDF creates a print-ready report using UX Robot’s monochrome editorial layout and embedded PDF typography. The document is prominently labelled Draft or Finalised, and a finalised export always uses the approved, locked snapshot.
• Copy for AI copies the complete structured report together with instructions for the receiving AI. Paste it into the AI tool your organisation permits.

The copied prompt tells the AI to work only from the supplied report, keep each source in its role, avoid outside knowledge, start from the 30-second assessment and the journey map, keep the What, Where, Why and Measure handoff, and never present a draft as approved. You can follow it with a narrower request, such as drafting a meeting brief, creating implementation tickets, or extracting acceptance criteria and success measures. The same evidence rules still apply.

Stakeholder delivery is available after the journey report is approved. Approval starts writing a shorter summary of the approved report for decision-makers.

1. Open the approved analysis. The Stakeholders section shows when the summary is ready; if it failed, select Retry stakeholder report.
2. Select Review stakeholder summary and check it 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 emails, review the recipient count, and confirm Send emails.

The summary keeps the journey report’s evidence basis: it says plainly whether each problem is measured in your evidence or observed in the browser only, and it shows representative screenshots from the journey’s stages. For a page tested before launch, it explains that the figures describe the comparable live page and presents the launch baseline as the target to beat.

Each selected stakeholder receives an editorial email with the report brief, confidence, up to three priority issues, up to three recommended actions, and 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.