Status updates

sprintrr can read a project's recent activity — tasks completed, milestones shifted, comments, blockers — and draft a structured update you'd send to stakeholders. It's the fastest way to keep people informed without writing the update from scratch every week.

What you get

Every status update has six fixed sections:

• TL;DR — one or two sentences an executive will read first.
• Shipped — what landed in the period.
• In progress — what's underway right now.
• Blockers & risks — what's off-track or stuck.
• Next — what's planned for the next period.
• Asks — explicit decisions or resources needed from the reader.

The AI only writes from evidence in your project. If a section has no supporting evidence, it stays empty rather than padded with fluff.

Generating an update

1. Open a project and switch to the Updates tab.
2. Pick the period it covers: This week (Monday to today — the default on Thursdays and Fridays), or the last 7, 14 or 30 days. Otherwise it starts on the last 7 days, or on the default you set in Settings → Status updates.
3. Pick Quality or Speed — Quality is more nuanced, Speed is roughly 2× faster. The current models are named in AI generation.
4. Click Draft update. After a few seconds you'll see the draft in the window, ready to edit. It costs 1 AI Update.

You can edit every section inline before publishing — add bullets, remove what the AI got wrong, tweak the TL;DR.

Publishing

Publishing marks the update as final and (optionally) sends it out. Under Send to, tick where it goes:

• Slack — posts to a channel you choose, using Block Kit so it renders cleanly on mobile and desktop. Connect your workspace in Settings → Status updates first — Send to Slack walks through the permissions and private channels.
• Email — sends transactional emails via the same delivery infrastructure sprintrr uses for account emails. Type the recipient addresses comma-separated.

The button names what will happen — Send to #launches + 2 emails, Email 2 people — and every send waits 8 seconds behind Undo send before anything leaves sprintrr. With nothing ticked it reads Mark as final: the update is saved as published, and you can share it with the export options below.

Viewing and exporting past updates

Every update you've generated stays in the Updates tab. Click any row to re-open it in full.

• Drafts open ready to edit, distribute, or publish — same controls as right after generation.
• Published updates open read-only, so you can't accidentally change something that's already gone out. They're still fully exportable.

Three export options are available on any opened update:

• Copy as Markdown — drops the update onto your clipboard as Markdown, ready to paste into a doc, a wiki, or a Slack message.
• Copy for email — copies a formatted version that keeps its bold headers and bullet lists when you paste into Outlook, Gmail, or any rich email composer. (A plain-text version comes along automatically for editors that don't accept formatting.)
• Download PDF — opens your browser's print dialog; choose Save as PDF to get a clean, selectable-text document you can attach or archive.

Scheduled weekly drafts

In Settings → Status updates, turn on Scheduled drafts and pick a day + hour in your timezone. Every cycle, sprintrr drafts an update for the most recently updated project you own — never auto-published. It waits in that project's Updates tab for you to review and publish on your own time.

Portfolio updates

For users juggling multiple projects, the portfolio update rolls up a narrative across N projects in one go. Portfolio runs count as 5 from your monthly AI Updates allowance (vs 1 for a single-project update) — the AI cost scales with the number of projects involved.

AI Updates allowance per plan

Status updates draw from your AI Updates allowance — a monthly allowance separate from your AI Credits, shown in the sidebar AI usage panel.

Allocations reset on the 1st of each month. Delivery to Slack or email does not decrement the bucket — only generation does.

Which allowance a run uses depends on the project: in a paid team's project where you hold a seat, the team's 500; anywhere else (your personal projects, a free team, a team where you have no seat), your own plan's. An update is counted when generation starts and given back if it fails; if the allowance can't be checked for a moment, nothing is generated and you're asked to try again. See Teams.

Bring Your Own Key = unlimited

If you connect your own AI key in Settings → Your AI keys, status updates run on your key instead of sprintrr's allowance. There's no monthly cap and sprintrr's cost is zero. This is the recommended path for power users.

Trust & data

• The generator only sees data inside your sprintrr workspace — tasks, milestones, comments, activity events. No external sources are pulled in.
• BYOK calls go directly to the provider you chose (Anthropic, OpenAI, or Gemini) using your key. sprintrr stores neither the prompts nor the responses on those keys.
• Every published update is logged in the activity feed with honest attribution: whether it ran on sprintrr credits or your own key, and which model.

Roadmap

• Per-section confidence signals + "show me where this came from" link to the source events.
• Reading receipts on email + Slack to surface unacknowledged updates.
• Risks detected inline, linked to the risk register.