PROJECT MANAGEMENT
Weekly upstream-team reliability scorecard from blocker history
Every week aggregates which teams caused the most dependency slips and how many downstream days they cost.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull slipped dependencies for periodClickUp
- LogicAttribute slips + sum days per team
- ActionPublish scorecard to ConfluenceConfluence
- OutputHeads-up to top offenders' leadsSlack
What it does
This workflow turns blocker history into accountability. Once a week it pulls every dependency that slipped, attributes each to the upstream team that owned it, and tallies the total downstream days lost per team. It publishes a ranked reliability scorecard to Confluence and quietly flags the leads of the worst offenders.
When to use it
Use it when the same teams keep blocking others and you need data, not anecdote, to drive the conversation. It gives delivery leads a recurring, fair scorecard for retro discussions.
How it works
- 1A weekly schedule starts the run.
- 2The flow queries ClickUp for dependencies that slipped in the period.
- 3Each slip is attributed to its upstream team and its downstream day-cost is summed.
- 4Teams are ranked by total days caused and slip count.
- 5The scorecard is written to a Confluence page, and the leads of the top offenders get a private Slack heads-up.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
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.