SpyderBot Documentation
Report progress and recommend the next investment
Leadership or a client wants to know what changed, what the team accomplished, and where to invest next. A useful update connects evidence to a decision without asking the reader to interpret every dashboard.
Your outcome: a concise report with measured findings, implementation status, material limitations, and a specific recommendation for resources or next work.
1. Name the decision the report should support
Choose the audience and request before selecting charts. Examples include approving an integration-content update, continuing a monitoring program, or investigating a new competitive threat.
State the Context and period. If you cover several markets or product lines, give each its own scoped findings. Do not average unrelated Contexts into a new overall score.
| Available evidence | Appropriate report |
|---|---|
| Only a first valid observation | Baseline, priorities, and measurement plan |
| Comparable observations over time | Progress and changes within that scope |
| Implemented work with later evidence still pending | Delivery status and the next outcome checkpoint |
| Material scope change | Separate earlier and later scopes, explaining the transition |
2. Select the findings that change the decision
Start with Brand Insights summaries, Observatory Intelligence Brief, relevant benchmark comparisons, or AI Traffic findings and outcomes. Use the source most relevant to the decision rather than collecting a metric from every product.
For each finding, write the conclusion in plain language, include its scope, and retain the evidence reference. Open the supporting detail when the finding determines a meaningful investment or needs qualification.
"Integration portrayal improved in the monitored small-business questions" is useful. "Our AI score improved" is incomplete without the metric, eligible scope, and comparison conditions.
3. Separate work delivered from outcomes observed
Use the existing task record and relevant verification evidence. Report three layers when applicable:
| Layer | What belongs here |
|---|---|
| Implementation | The content, configuration, or process change actually completed |
| Observed AI or website behavior | Comparable portrayal, recommendation, citation, access, or referral observations |
| Business outcome | Configured human goals, qualified outcomes, or revenue with its measurement limits |
Do not fill a missing layer with a proxy. A passed audit does not stand in for an AI recommendation, and a recommendation does not stand in for a sale.
Where multiple activities occurred at once, describe progress observed after the work rather than assigning all change to one task. If there is no suitable baseline, report the current state without inventing a trend.
4. Write a decision-ready update
Illustrative update for leadership. This is a reporting template, not an automatic SpyderBot export.
Decision requested
Approve a bounded update of the related setup guide and continue monitoring the integration use case.
Scope
The selected small-business Context, monitored systems and question panel, and the comparison periods shown in the linked observations.
What we learned
Later comparable answers describe the corrected integration capability accurately. Recommendation behavior has not shown a supported improvement in the same scope.
What we delivered
The integration page was updated and its facts approved by the product owner. Publication and accessibility were checked.
Business outcome
No supported conversion conclusion yet. Report available human referral evidence separately with its source and coverage.
Recommendation
Align the setup guide with the verified capability, then investigate the remaining selection criteria before funding a broader content rollout.
Owner, resource request, and checkpoint
Name the content and product owners, state the actual effort or budget requested, and set the next review against eligible observations.
Replace every example statement with your measured evidence. Keep the full supporting report available for readers who need detail; the executive update should make sense on its own.
5. Address the questions a decision-maker will ask
Check the draft against four questions:
- What is different or newly known?
- How strong and relevant is the evidence?
- What should we do, and what resources or owner does it require?
- What observation would cause us to change that decision?
If the answer is "we do not know yet," name the uncertainty and the work needed to resolve it. If evidence supports no additional investment, say so. Do not construct an ROI figure without a suitable cost and attribution basis.
6. Share the appropriate view
Use available export or sharing controls under the workspace's access permissions. Confirm the actual public/private state and audience before sharing. A screenshot should retain the metric label, period, and scope needed to interpret it.
You are done when the recipient can identify the requested decision, the evidence supporting it, the owner, and the next checkpoint. The value of the report is the decision it enables, not the number of charts it contains.