Guides /

GitHub Blockers and Risks for Sponsor Meetings

Set up GitHub rules for blockers and risks, save them as views, and build a short sponsor list with owner, age, customer impact, and decision needed.

By The Unblockd teamPublished

To surface blockers and risks from GitHub for a sponsor meeting, write each term as a rule the team can check, save each rule as a filtered view, and open those views before the meeting. The output is one short list with an owner, an age, the customer affected, and the decision the sponsor needs to make. A saved view shows the state at the moment someone opens it, so the list is only as current as the last time the views were opened.

What counts as a blocker or risk in GitHub?

In GitHub, a blocker is an issue or pull request that cannot move until someone outside the delivery team acts. A risk is open work tied to a customer date that will slip unless something changes. Write both as rules built on labels, status values, and age, so anyone who applies a rule gets the same list.

Start from the table below. Replace each bracketed part with the label names and status values your team already uses.

Type Rule to write Example trigger
Blocker Item carries the [blocked label], or its status reads [blocked value] Work waits on a decision from [sponsor or team name]
Risk Open item tied to [go-live date] with no status change in [N days] Pull request has no review after [N days]
Customer-owned Item waits on the customer, with no reply in [N days] Customer has not confirmed [input needed]

Test each rule against the items from your last sponsor meeting. If a rule catches work nobody would raise with a sponsor, tighten it. If it misses an item the sponsor cared about, loosen it and test again.

How do you pull the list before each sponsor meeting?

The team pulls the GitHub list by saving each rule as a filtered view and opening those views on a fixed schedule before every sponsor meeting. Write the rules first, since a filter is only as good as the rule behind it. The steps below work in any tracker the team already uses.

  1. Write the rules on one page the team can read. Include the label names, the status values, and the day threshold for each rule.
  2. For each rule, save a filter that matches it. If the tracker cannot save filters, bookmark each filtered list and name the bookmark after its rule.
  3. Book a recurring hold for the afternoon before each sponsor meeting, titled "Sponsor list review". Open every saved view during that hold.
  4. Compare the results with the list from the last meeting. Note what is new, what has closed, and what has aged. The change is usually what the sponsor needs to hear.
  5. Remove duplicates, fill in missing owners, and drop items that fail their rule.

Common mistake: trusting a count you have not checked. Compare each total with the number the tool shows before the list goes on a slide.

How do you show age and customer impact?

Age is the number of days since an item last changed status, counted on the review day. Customer impact is one sentence naming the customer, the date at risk, and the effect if nothing changes. Use the same method for every row so the sponsor can compare items from one meeting to the next.

For age:

  • Use the date of the last status change, not the date of the last comment.
  • Count on the review day, the same way for every row.
  • Flag any row over the [N days] threshold in its rule.

For customer impact, name the customer the way the sponsor already does, not by an internal project code. Name the date the work affects. Then describe the effect in plain terms, such as a moved rollout or a workaround the customer must use.

An item opened long ago that moved last week is not stuck. Date its age from the last status change, so the sponsor sees the item as it stands now.

Common mistake: copying the engineering cause into the impact field. The sponsor needs the effect on the customer. The cause can stay in the item link.

What should each sponsor line contain?

Each sponsor line gives the decision needed first, then the item, owner, age, and customer impact. A line without a decision is only information, so write the decision first. Add a recommendation and the team's next step for the case where the sponsor approves.

Decision needed: [approve option A or option B] by [date]
Item: [issue or pull request title], [link]
Owner: [name], [team]
Age: [N days] since the last status change
Customer impact: [customer] goes live on [date]. If this is not decided by [date], [specific effect].
Recommendation: [one sentence]
If approved: [team action] by [date]

The brackets stand in for facts from your own tracker, because no real figures are supplied here. This row shows the same form filled in with placeholders only:

Decision needed: choose whether [customer name] goes live with [module A] only, or waits for [module B], by [date].
Item: [title of the pull request], [link]
Owner: [name], [team]
Age: [N] days since the last status change
Customer impact: [customer name] goes live on [date]. If this is not decided by [date], [effect the customer will feel].

Read the decision line on its own. If it tells the sponsor what to choose and by when, the line works.

What does the lead check before the list goes out?

Before the list goes to the sponsor, the lead checks each row against its rule, removes engineering-only items, and confirms that every decision is one the sponsor can make. Each owner confirms their item and its status. The tracker link stays as backup, not as the main content.

  1. Check each row against its rule, and remove any row that does not match.
  2. Move items with no sponsor decision to the team's own list.
  3. Confirm each owner's name and status with that person before sending.
  4. Send one decision per request. A link to the tracker is not a decision.
  5. After the meeting, record the decision beside the item, with the next step and its date.

Ask one question before you send: if the sponsor reads only the decision line, can they act on it? If not, rewrite that line.

Mistakes to avoid: sending the whole backlog, dating age from the open date, leaving the decision blank, and copying issue titles without confirming the owner still holds the item.

Can a sponsor answer the decision by email?

A sponsor can answer by email when each request asks for one clear choice with a deadline. The sponsor does not need to open the tracker to reply. Keep the message short, name the date, and say what the team does after the answer.

Subject: Decision needed by [date]: [customer name] [module]

[Sponsor name], the team needs one decision on [item]. Option A: [option A]. Option B: [option B]. If we have your answer by [date], we will [team action]. If not, [specific effect]. Reply with A or B.

Send a separate email for each decision, so each reply stays attached to one item.

What can run automatically, and what decision is left?

The team can set up written rules, saved filters, and a review hold now, without a new tool. Sending the list to a sponsor on a schedule needs a connected tool or a script, and a GitHub proposal for a scheduled report was closed as not planned. Decide which path the team will follow before the next sponsor meeting.

Path one is to keep it by hand. The lead opens the saved views during the review hold and checks each total against the tool's count. This takes time before each meeting, but it needs nothing installed or hosted.

Path two is to ask for a connected tool. Before you ask, test its rules against the items from your last sponsor meeting. Ask whether it can apply your blocked label, status values, and day thresholds, and whether it shows the owner, age, and customer for each item. Get those answers in writing before you rely on it.

Some tools send alerts about engineering activity. Gitmore's public page describes alerts for stale pull requests, agent pull requests waiting on a human, and merges with no reviewer. Those signals describe engineering health, so pass one to the sponsor only when it threatens a customer date.

A recipe that pulls GitHub security alerts into a sheet on a timer notes that GitHub caps alert responses at 100 per page, and that skipping pagination can show only the first page while looking complete. That recipe covers security findings, not delivery blockers, and it involves writing an Apps Script fetch loop. Use it as a warning about counts, not as a setup to copy.

Next step: before the next sponsor meeting, choose path one for that meeting, or ask the tool owner about path two, and write the choice in the team's notes with its date.

Questions people ask

How often should I refresh the GitHub list?

Open the saved views before each sponsor meeting, and check them again only when a new blocker is raised. Date each version of the list so the sponsor knows which one they are reading. A list that predates the last meeting should not go out.

Should I mark blockers with labels or project fields?

Use whichever field the team keeps current. Labels are simple to filter on, and a status field gives a clearer picture when people update it. Pick one for blockers so the rule does not depend on two places that can disagree.

Can I automate this with a script or a scheduled workflow?

Some teams do, but that is a build project for engineering rather than a sponsor-meeting task. A [recipe that pulls GitHub security alerts into a sheet on a timer](https://aitoolrecipes.com/recipes/github-security-report-google-sheets-dashboard) shows the pattern, but it covers security findings rather than delivery blockers. Saved views and a review hold are enough to start.

What if people do not label work consistently?

Agree on one blocked label and one named owner before relying on the list. Let the review catch items missing either one. Fix the habit where the work is recorded, not only in the sponsor list.

The Unblockd team

Unblockd helps teams deliver projects faster by getting stuck work in front of the sponsor who can clear it: an AI agent drafts the ask from the project's evidence, the team checks and sends it, and the sponsor answers without signing up.

Get the sponsor ask checklist

One screen to check before you send an ask: the decision, the options, the date, and what waits on it. Then one email a week with new guides.