Docs/Reports & Synthesis

Reports & Synthesis

Upshot's core capability: pull raw activity from your tools, interpret it with AI, and generate polished reports tailored to different audiences.

How synthesis works

Every report goes through a 5-stage pipeline:

1
Pull

Fetch latest data from all connected integrations for the selected time range.

2
Interpret

AI interpreter prompts analyze each data source — understanding what a PR, issue, or error event means in context.

3
Cluster

Related items are grouped into logical work streams (e.g., a PR + Linear issue + Sentry error = one shipped feature).

4
Score

Each cluster is scored by impact, audience relevance, and sensitivity level.

5
Generate

Output prompts produce the final report in the selected audience's voice, tone, and format.

The 4 audiences

🛠 Team

Technical updates for engineers. Includes what shipped, what broke, DORA metrics, PR highlights, and deployment details. Uses technical language — commit SHAs, error traces, metric changes.

📈 Leaders

Executive summaries for engineering managers, VPs, and C-suite. Focuses on business impact, velocity trends, team health, and strategic alignment. Abstracts away technical details into outcomes.

👥 Customers

Polished changelogs and update emails. Highlights new features, improvements, and bug fixes in customer-friendly language. Automatically filters out sensitive items (security patches, payment bugs, internal tooling).

📰 Market

Editorial blog posts for marketing. Storytelling-driven, product-narrative style. Turns shipped features into compelling content that positions your product and team.

Format options

FormatBest forDelivery
EmailLeaders, CustomersSent via connected email or copied as HTML
SlackTeamPosted to a Slack channel
Blog / ChangelogCustomers, MarketPublished to your public changelog or blog

Report scheduling

Set reports to generate automatically on a recurring schedule:

  • Weekly — every Monday morning (configurable day)
  • Biweekly — aligned to your sprint cadence
  • Monthly — end-of-month summaries

Scheduled reports go into a review queue before publishing. You'll get a notification to review, edit, and approve — or auto-publish if you trust the output.

Review & approval flow

  1. Report is generated and enters Draft status
  2. Reviewers receive a notification (email or Slack)
  3. Open the draft in Upshot to review, edit inline, or leave comments
  4. Click Approve & Publish or Regenerate with Feedback

Regenerate with feedback

Not happy with a draft? Click Regenerate and provide specific feedback — "make the tone more casual", "emphasize the performance improvement", "remove the section about internal refactoring". Upshot regenerates with your guidance incorporated.