Read, export and share a Scout report

Open the run

In Flamio Scout, click the run in Recent runs.

Read the header tiles

The tiles sum up the run: Pages visited / found, Actions taken, Site analyzed, Tokens spent and Elapsed. Notes under them say if coverage stopped early, for example at the research budget, or if parts of the site went unexercised because the run was read-only.

Jump to the report

Click View report. The report opens with a score card: the verdict (Success, Partial or Failed), the risk, a one-line summary and the count of findings per severity.

Start with the shortlist

Start here lists the top findings to fix. Click one to jump to its card. On an Explore run, Main path shows the task a visitor most likely came for and how far Scout got. On a Focused or Goal run, Your scenario shows the same for what you described.

Work through the findings

Findings lists the problems a visitor meets, worst first. Each card shows:

• the severity, and Defect (reproduced during the run) or UX (how a first-time visitor experiences the page);
• Phone when it was seen on the phone layout;
• Seen in On-Live when real visitors met the same problem — click it to open the On-Live issue;
• what is wrong, a Fix line, and Technical details for developers;
• the pages it appears on and the evidence screenshots.

With On-Live recording the site, each card also shows Real visitors on its pages: visits, the share who left there and the share who struggled. Select Real traffic above the list to put findings on the busiest pages first.

Look at the evidence

Click Expand all screenshots to open every evidence frame. Click a frame to zoom it, then step through that finding's other frames with the arrows or the left and right keys.

Read the other sections

Below the findings, when they have content:

• Technical errors — errors the site reported while Scout used it, for developers.
• Look & feel — a verdict on the design, then one note per principle it breaks, with every page it shows on. These do not stop a visitor, so they stay out of the findings and the risk.
• Cross-page structure and What works well.

Explore the map

Scroll to How it explored the site. Each page's color is its UX score: good, attention or poor. Dashed pages were seen as links but not visited. Click a page for Problems on this page.

To see exactly what Scout did, click Watch recording. Scout walks in several browsers at once, so a run can list a recording for each browser. Map pass lists how the run walked the site, step by step.

Confirm the findings

Confirm every finding you want to export. Export approved sends only confirmed findings.

Pick the destination

Click Export approved above the report and select the connected tracker from the menu.

Read the result

The dialog shows each finding as Exported, Skipped or Failed. A finding already sent is marked as already exported instead of being sent twice. Click Close.

Open the share dialog

On a completed run, click Share at the top of the run page. Share findings opens.

Pick what to share

Tick the findings the page should show. The three most severe start ticked. You can add Look & feel notes too.

Choose the summary

Leave Show the overall score, risk and summary of the audit ticked, or untick it to share the findings alone.

Create the link

Click Create link and copy the link that appears.