How to Export and Share a GazeRank Report

Why this matters

A stakeholder deciding whether to fund further work needs a different view than an engineer who needs to fix a specific issue. Sending the same full, detailed export to both audiences either overwhelms the executive or under-informs the implementer.

Reports also lose value quickly if they're shared without context. A raw export with no summary of what matters most forces the recipient to do the prioritization work themselves, which defeats much of the purpose of sharing a curated report in the first place.

Implementation guidance

Tailor the export and the framing to who's going to act on it.

1. 1

   Decide the audience before exporting

   A leadership summary and an engineering action list call for different levels of detail from the same underlying data.

2. 2

   Lead with the summary and priority findings

   Whatever the audience, put the most important information first rather than requiring a scroll through raw data to find it.

3. 3

   Include affected pages and suggested fixes for implementation teams

   Anyone expected to act on the report needs enough specific detail to start work without a follow-up meeting.

4. 4

   Add brief context notes when sharing externally

   A report shared with a client or external stakeholder benefits from a short explanation of what the scores mean and why they matter.

5. 5

   Set a clear next step at the end of the share

   State what you want the recipient to do with the report, whether that's approval, assignment, or a specific fix, rather than leaving it open-ended.

Validation checklist

• The export format matches the audience's role and needed level of detail.
• Priority findings are presented before raw detail, not after.
• Implementation-facing exports include affected pages and suggested fixes.
• A clear next step accompanies the shared report.