Roll Up Microsoft Project Plans Into One Sponsor Report

To roll up several Microsoft Project plans into one sponsor report, give every plan the same small set of status fields, keep risks and issues in one shared list outside the schedule, and build the report from those two sources. Desktop Project can roll milestones onto a single program view. Risks, issues and overall status need a shared list or a reporting layer that you set up yourself.

Which Microsoft Project route carries risks and issues across projects?

Only a reporting layer built on shared project data carries risks and issues across projects automatically. A Microsoft Project schedule holds tasks and dates, so risks and issues need their own shared list. A desktop program view handles milestones well. Excel and PowerPoint templates carry anything, but someone fills them in by hand every cycle.

Microsoft's Power BI app for Project Web App combined milestones, risks and issues across projects. That route depends on Project Online, which had a scheduled retirement date that has now passed (see the next section).

Microsoft also explains how to use Power BI Desktop to connect with your project data, and it introduced the original Project Online content pack for Power BI on its Project blog. Read both against your current licence before you build anything on them.

What does the Project Online retirement change?

The Project Online retirement means any roll-up that reads Project Online data, including the Power BI portfolio reports, may need a new source. Velosio reported that Project Online was scheduled to retire on September 30, 2026. That date has passed, so confirm with your administrator what your tenant can still reach.

Ten Forums covered the same scheduled date. According to Velosio, Microsoft points users to Planner Premium, Project Server Subscription Edition or Dynamics 365 Project Operations. Ask your Microsoft partner or administrator these questions:

1. Where are each project's status, risks and issues stored now?
2. Can our existing Power BI reports read that store, or do they need rebuilding?
3. Was our risk and issue history exported, or can it still be recovered?
4. Who can see which projects, and can we limit that by client?

If the answers are unclear, run the next cycle from a shared list and a template while you decide. Sponsors still get their report on time.

How do I set up each plan so it rolls up cleanly?

A plan rolls up cleanly when every project reports the same fields, uses the same names and follows the same rules for status colours. Settle those fields and rules once with your project leads, before the next reporting cycle, and the roll-up becomes copying rather than interpreting.

1. Agree the fields. Scrumbuiss suggests one row per project with Health, Trend, Milestone, Variance, Top risk, Blocker, Decision needed and Next action. Add an Issue field if your sponsors separate issues from risks.
2. Write the colour rules in words. For example: "Green: next milestone on its baseline date and no open decision past its due date. Amber: milestone at risk or a decision overdue. Red: milestone missed or an issue the team cannot resolve without the sponsor." Agree the wording with leads so two projects in the same state get the same colour.
3. Choose the status dimensions. Analysistabs rates RAG across six dimensions: overall health, schedule, budget, scope, resources and risk. For a small engagement, overall health plus schedule and risk may be enough.
4. Put risks and issues in one shared list. Use a SharePoint list, a shared workbook or your reporting tool, with columns for [Project], [Client], [Type: risk or issue], [Description], [Owner], [Rating], [Due date] and [Sponsor action needed]. Leave the task schedule for tasks.
5. Baseline every plan. Milestone variance only means something once a baseline is set.
6. Set a cut-off. Leads update their plans and the shared list by [day and time] before the report goes out.

How do I build the milestone view in desktop Project?

Build the milestone view in desktop Project by putting each client's plans into one program file, copying the Gantt Chart view, turning on rolled-up bars and styling milestones by status. MPUG's guide describes a view that shows every project in a program with milestone status, and notes Project's standard views do not give executives a quick summary.

The program file holds each client's plans together, so the milestone view can show them side by side. MPUG's guide starts from a program that already exists, so create that file first.

1. Insert each client plan into a [Client] program file.
2. Copy the Gantt Chart view to a new view named [Sponsor milestones].
3. Open Format, then Layout, and check "Always roll up Gantt bars", as MPUG describes.
4. Open Format, then Bar Styles, and create a style for each milestone state: complete, on track, delayed and not baselined. MPUG uses green for on or ahead of schedule, red for delayed and black for not baselined.
5. Check the order of the bar styles. MPUG warns that the order decides which bars draw on top, so a later style can hide an earlier one.
6. Add milestone names and dates as bar labels, then print or export the view for the report.

MPUG's steps use an older menu layout and name no Project version. In newer versions, look for the Layout and Bar Styles dialogs under the Format tab.

This view covers milestones only. Take status, risks and issues from your shared list.

What should the sponsor report look like?

The sponsor report should open with a short summary and one line per project, put red and amber projects first and end with the decisions you need. Analysistabs notes that the executive summary is often the only part senior readers see, so make the first page carry the whole message.

Copy this layout:

[Client name] portfolio report, [reporting period]

Summary
[One or two sentences: overall position, biggest change since last report, decisions needed.]

Projects (red and amber first)
| Project | Health | Trend | Next milestone and date | Variance | Top risk | Open issue | Decision needed | Next action and owner |
| [Project] | [R/A/G] | [Better/Same/Worse] | [Milestone, date] | [Days or note] | [Risk] | [Issue] | [Decision, by date] | [Action, owner] |

Decisions requested
1. [Decision], needed by [date], because [consequence of waiting]. Recommended option: [option].

Milestones
[Rolled-up milestone view from Project]

Appendix: one page per project
[Status by dimension, full risk and issue list, milestone table]

Follow Scrumbuiss's review rules: sort red and amber projects first, show the trend next to the colour and keep requested decisions visible. For steering meetings, Techno-PM points out that a PowerPoint format lets you combine several project status reports into one presentation.

How do I keep one client's data out of another sponsor's report?

Keep one client's data out of another sponsor's report by building a separate report for each client from a filtered source, never by hiding rows in a shared one. A consultancy's internal portfolio view can hold every engagement. What a client sponsor receives should only ever contain that client's projects.

• Add a [Client] column to every plan, the risk and issue list and the report source, and filter on it.
• Build one program file in desktop Project per client rather than one for the whole firm.
• In Power BI or Excel, save a separate report or file per client. Do not send a shared file with filters a recipient could clear.
• Before sending, check that every project name, risk and issue in the file belongs to that client.
• Share by named recipient, and remove old access when a sponsor changes.

How much manual work does each cycle take, and how do I reduce it?

The manual work in each reporting cycle depends on where project data lives. With a template, someone copies every field from every project. With a shared list and a reporting layer, the work moves to leads keeping their own data current, and you review the result before sending. Shared fields and a fixed cut-off reduce the retyping.

Use this checklist each cycle:

1. Leads update plans and the shared list by the cut-off.
2. Refresh the milestone view and the report source.
3. Check that each colour matches the agreed rules, and challenge any that do not.
4. Write the summary and the decisions requested yourself.
5. Run the client separation check, then send.
6. Record each sponsor's decision against the project and assign the next action.

When is a lighter alternative better?

A lighter alternative makes sense when the reporting layer costs more upkeep than the report is worth, or when what you need from sponsors is decisions rather than a dashboard. For a small engagement, a shared list, a template and a short decisions section sent to each client sponsor may be enough.

If you would rather start from the Microsoft Project plans you already keep than build a reporting layer, an import can save retyping. Unblockd's onboarding includes a setup guide, a first-ask composer that suggests asks from the project's plan and previews the email, templates, plan import (paste, Microsoft Project, Rocketlane), tool imports.

When a decision cannot wait for the next report, send it on its own with wording like this:

Subject: Decision needed on [project] by [date]

[Sponsor name], we need your decision on [question] by [date].
Options: [option A] or [option B]. We recommend [option] because [reason].
If we wait past [date], [consequence].
Reply with your choice and we will confirm the next step.

Whichever route you pick, your next step is the same: agree the shared fields and colour rules with your leads before the next sponsor meeting.