Stakeholder reports
Stakeholder reports audience
This menu page is about reports for people who need the main point.
That can be a founder, client, manager, teammate, or anyone who should understand what changed without reading every dashboard panel.
Report contents
A useful report should be short and honest.
It should include the selected period, the main visibility change, the evidence behind it, and the next action.
| Report part | What to include |
|---|---|
| Period | The week or date range reviewed |
| Main change | Mentions, sources, competitors, or page movement |
| Evidence | Prompt answer, source pattern, or competitor gap |
| Missing data | Any integration that is not connected |
| Next action | One clear task or card |
Generation timing
Reports work best after fresh data has arrived.
For example, let visibility prompts run first. Then schedule CLEA to review the new Analytics, Sources, and Competitors data.
Review before sharing
Do not share an agent report without reading it.
CLEA should explain what the evidence proves and what it does not prove. If the report makes a claim without evidence, rewrite the prompt or inspect the dashboard again.
prompt.txtCopy prompt
Write a short team report from this week's Calendar and Analytics data. Use simple words. Include the main change, the evidence, missing data, and one next action.