CircleCI delivery scorecard for every project in your org
See how every project in your CircleCI org is really doing on one screen, then drill into the workflow and job that is slowing your team down.
CircleCI
Google SheetsEngineeringOperationsResearch & MonitoringBuild me an app that our engineering lead opens on Monday mornings and during planning, to see how every project in our CircleCI organization is actually performing instead of checking one project at a time in the CircleCI UI. It is a browse and drill surface, not a report: I open it, sort, filter, and click into whatever looks wrong.
The landing view is a sortable table of every project in the org, built from a single call to the CircleCI operation Get org summary metrics for the selected window. One row per project, with columns for success rate, throughput (number of runs), median duration, p95 duration, and credits consumed. Where the response carries trend data, show a small week over week arrow beside success rate, duration, and credits, green when the metric improved and red when it got worse, with the percentage change on hover, so regressions are obvious at a glance. Let me sort by any column, and default the sort to worst success rate first so the problem projects sit at the top. Format durations as human readable (4m 12s, not 252000), success rate as a percentage, and credits with thousands separators.
Put two controls at the top of the page that apply to every view: a branch filter that defaults to the default branch (main), and a window switcher for the last 7, 30, or 90 days. Changing either refetches whatever view I am on. Keep my selections when I drill into a project or workflow and come back out.
Clicking a project row opens that project's detail view. Use Get project summary metrics and trends for the project level headline numbers with their trends, and Get summary metrics for a project's workflows for a table of that project's workflows carrying the same columns as the landing table: success rate, runs, median duration, p95 duration, and credits. Same sorting behaviour, same branch and window filters.
Clicking a workflow opens the workflow detail view, which shows two panels side by side. The first uses Get summary metrics for a workflow's jobs to list that workflow's jobs, so I can see which jobs are slowest and which fail the most, with a toggle to rank the list by p95 duration or by failure rate. The second uses Get recent runs of a workflow to show the most recent runs newest first, with status, duration, credits, branch, and when each ran, and failed runs visually distinct from successful ones.
Every failed run in that recent runs list gets a Rerun button that calls Rerun a workflow for that run, rerunning from the failed job. Ask me to confirm first, show the result inline, and refresh the runs list afterwards so I can see the new run appear.
Add an Export to Sheet button on the landing view that appends the current project table, exactly as filtered and sorted, to a Google Sheet using Append Values. Let me pick the spreadsheet and tab and remember them for next time. Include the branch, the window, and the export date on every appended row so numbers pulled in different weeks stay comparable once they are in our leadership deck. Confirm how many rows were appended when it finishes.
Important nuance to bake in: these CircleCI insights only cover the last 90 days and refresh once a day, so the newest runs may not be reflected yet. State that in plain language in a persistent spot next to the window switcher, and never present the numbers as real time. If a project has no runs in the selected window, show it as no data rather than as a zero percent success rate, and if a project or workflow returns nothing at all for the chosen branch, say so plainly instead of rendering an empty table.
What does this prompt do?
- Opens on a sortable table of every project in your CircleCI organization: how often builds pass, how many ran, how long they take, and the credits they used.
- Puts week over week arrows on every number, so a project that just got slower or flakier stands out at a glance instead of hiding in an average.
- Lets you click a project to see its workflows, then click a workflow to see its slowest and most failure prone jobs next to its most recent runs.
- Reruns a failed build in one click, and sends the current table to a Google Sheet so the numbers land in your leadership deck without retyping.
What do I need to use this?
- A CircleCI login with access to the organization you want to review
- A Google account, if you want to send the table to a spreadsheet
- The branch your team ships from, usually main
How can I customize it?
- Switch the window between the last 7, 30, or 90 days depending on whether you are doing a Monday check-in or planning a quarter.
- Point the branch filter at your default branch or at any other branch your team releases from.
- Change which column the table sorts by, and which spreadsheet and tab the export lands in.
FAQs
How fresh are these numbers?
Can I look further back than 90 days?
Do I have to add each project one at a time?
Can I restart a failed build from here?
What if my team does not ship from main?
Related templates
Stop buying stale lists. Reps run a saved search, work the results like an inbox, and only the accounts they approve ever reach your CRM.
Drag creators through Sourced to Wrapped on a board grouped by campaign, with audience stats on every card and a one-click brief for each creator.
Pick a repricing rule, send an assistant out to check competitor pages, then approve the new prices that clear your margin floor.
See the projected bounce rate for any outbound send before it goes out, and keep the launch button locked until the list is clean enough to be safe.
Pick any date range and see what each device in your home actually cost to run, not just how many kilowatt-hours it used.
Search three months of global coverage on your topic, rank the outlets actually writing about it, and draft a tailored pitch for each one.
Stop checking CircleCI one project at a time.
Open one screen that ranks every project by how well it is really building, and drill straight into the workflow that needs attention.