Scheduled Digests

A recurring sprint status update, delivered to Slack, Microsoft Teams or email — so nobody has to open the app to know how the cycle is going.

Plan: Business and above

What you can do

  • Schedule a digest per project, daily or weekly.
  • Pick the hour it sends (0–23) and the timezone it's measured in.
  • Deliver to a Slack channel, Microsoft Teams, or a list of email recipients.
  • Add an optional AI narrative — two or three sentences summarising progress and naming the biggest risk.
  • Send now to test it, without waiting for the schedule.
  • Enable or disable a schedule without deleting it.

Getting started

Find it

Digests live in the Command Center, not in their own sidebar item.

  1. Click Command Center in the workspace sidebar.
  2. Open the Digests tab.

📷 Screenshot: The Command Center with the Digests tab active, listing scheduled digests.

Create a digest

  1. Click New digest.
  2. Name it (defaults to Sprint digest).
  3. Pick the Project.
  4. Pick the Frequency — Daily or Weekly.
  5. Set the Send hour (0–23) and the Timezone. 9 in Europe/London means 9am UK time, year-round.
  6. Choose the Destination:
    • Slack — type the channel name (for example, project-updates).
    • Microsoft Teams — posts to the workspace's connected Teams channel(s). No extra field.
    • Email — enter comma-separated recipients (lead@acme.com, pm@acme.com).
  7. Tick Add AI narrative if you want the written summary.
  8. Tick Enabled.
  9. Click Create digest.

📷 Screenshot: The New scheduled digest modal — project, frequency, send hour, timezone, destination and the AI narrative checkbox.

Test it

Click Send now on the digest row. It builds and delivers the digest immediately, and tells you if delivery failed and why. Do this before trusting a schedule.

What's in a digest

The digest reports on the project's current cycle — the one running today. If no cycle is running, it falls back to the most recent one; if the project has no cycles at all, the digest has nothing to report and won't send.

It contains:

  • Progress — items done out of total, as a count and a percentage.
  • Incomplete, Added after start (scope creep), and Overdue counts.
  • Needs attention — named items, not just numbers: what's overdue, what's high or urgent and still open, and what got added after the cycle started.
  • AI narrative (if enabled) — a short, plain-text note leading with overall progress, calling out the most important risk by name, and ending with a suggested next action.

The AI narrative is grounded in the numbers above and instructed not to invent items. It needs an AI provider configured on your instance — without one, the digest still sends, just without the narrative.

Managing digests

Each row shows the digest's name, its project, its schedule, its destination, and the outcome of its last run. From the row you can:

  • Send now — deliver immediately.
  • Edit (pencil) — change anything, including turning it off with the Enabled checkbox.
  • Delete (trash) — remove it entirely.

Prerequisites

  • Slack — the workspace must have Slack connected, and the channel must exist. See Integrations.
  • Microsoft Teams — the workspace must have a Teams channel connected. See Teams. Teams digests go to the connected channel(s); you cannot choose a different one per digest.
  • Email — SMTP must be configured on the instance (admin panel → Email).

If the destination isn't set up, Send now will tell you so rather than failing silently.

Tips

  • Weekly digests hit hardest the morning of your sprint review. Daily digests suit teams that need standup context in-channel.
  • Set the timezone to the team's timezone, not the server's. The send hour is interpreted in the timezone you pick, and it stays correct across daylight saving.
  • Use Send now after every edit. It's the only way to be certain the channel name or recipient list is right.
  • The AI narrative is what people actually read. The counts are what they skim past.

Limits & good to know

  • Daily or weekly only. No hourly, no monthly, no "weekdays only", no specific day-of-week for weekly digests — the weekly cadence just fires roughly every seven days from its last run.
  • Hour precision, not minute. You pick an hour; the digest sends somewhere within it. The scheduler wakes every few minutes.
  • One project per digest. No workspace-wide roll-up. Want four projects? Create four digests.
  • Cycle-based only. A project with no cycles produces no digest. The content is always cycle stats — you can't change what it reports.
  • Teams destination isn't channel-specific. It goes to the workspace's connected Teams webhook(s), so if you've connected several channels, several get it.
  • If the service is restarted around a digest's send hour, that run can be missed. The next one goes out normally.