Separate the work from the observation.
A published article, a recorded mention and a change in visibility are different things. We keep them distinct so a report can explain what was done and what was observed without implying that every movement has a single cause.
Start with a simple record of the work: what was created, where it was published and which question or audience need it was intended to serve. That gives the rest of the report a useful reference point.
Keep the context with the evidence.
For a search or AI observation, record the query, platform and observation date, together with a source URL or screenshot where available. For a relevant mention, preserve the surrounding conversation. A count without context is difficult to interpret and even harder to act on.
Describe observations with the limits of the record in view. A single observation is a snapshot. A repeated observation may deserve more attention, but the report should still explain how it was collected.
Make room for what is missing.
A report is more valuable when it shows gaps as well as examples of presence. Which important questions still lack a useful answer? Which explanations need an expert review? Where does the product remain difficult to understand?
These are working questions for the next cycle. They connect measurement with editorial judgment and keep the discussion focused on improving the body of work.
End with a decision.
Choose a small set of next priorities and explain why they belong next. Refresh an answer that needs more detail. Build the walkthrough that sales keeps requesting. Investigate a source that appears repeatedly in category research.
The report has done its job when the team can see the evidence, understand its limits and agree on the next useful move.
A note on our approach, from the Nakama team.
