PROJECT MANAGEMENT
Cross-team velocity rollup with Teams risk briefing
Twice a sprint it rolls up velocity and burn-down across multiple ClickUp team spaces into an Airtable tracker, ranks teams by spillover risk.
How it runs
The automated pipeline, trigger to output.
- TriggerTwice-per-sprint schedule
- ActionPull sprint lists and estimates from each ClickUp spaceClickUp
- LogicCompute per-team completed, remaining, and projected finish
- ActionUpsert team snapshots into Airtable trackerAirtable
- LogicScore and rank teams by spillover risk
- OutputPost ranked risk briefing to Microsoft TeamsMicrosoft Teams
What it does
It aggregates sprint progress across several ClickUp spaces, records each team's committed, completed, and projected-remaining work in an Airtable rollup, scores every team's spillover risk, and posts a ranked briefing so program leads see which teams need attention first.
When to use it
Use it when one program manager oversees several squads and needs a single comparative view of who's on track and who's about to spill. It replaces chasing each team individually with one prioritized risk list.
How it works
- 1A twice-per-sprint schedule starts the run.
- 2It pulls each configured ClickUp space's sprint list, statuses, and estimates.
- 3It computes per-team completed vs. remaining work and a projected finish based on recent throughput.
- 4It upserts each team's snapshot into the Airtable velocity tracker for trend history.
- 5A scoring step ranks teams from highest to lowest spillover risk.
- 6It posts the ranked risk briefing to the program Microsoft Teams channel.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Log every dependency slip to a Notion register and email the affected leads
On any Asana dependency slip, appends a structured row to a Notion blocker register and emails the leads of the downstream teams so there is both an auditable record and a direct…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.