Desktop Microsoft Project can show several client projects in one view, but only as a snapshot, not a live dashboard. Insert each client file as a subproject in one master file, and the master shows them together. ONES describes refreshing that master by exporting it again, and says a live dashboard usually needs Project Online or Power BI.
Can desktop Project show several client projects in one view?
Yes, as a snapshot. Desktop Microsoft Project can insert several client project files as subprojects in one master file, which gives one schedule view across engagements (ONES). Treat that view as a report you rebuild, not a live feed, unless your version proves otherwise in the test below.
The steps below come from the ONES guide. They were not run on a specific current desktop version, so check each one on the version your team uses before you rely on it. The ONES guide does not say which of its steps need a server, so note any step your version does not offer.
- Save each client engagement as its own project file, in a folder that only people on that engagement can change.
- Create a master file named [portfolio name] and insert each client file as a subproject.
- Open the master and check that each subproject's dates and tasks match its source file.
- When the sponsor needs a chart, export it with the feature ONES calls Visual Reports. ONES does not set out that feature's limits, so run the export on a copy first.
Avoid editing the master as if it were the source of truth. Make changes in the client files, then rebuild the master from them.
What can't a desktop master file show across client projects?
The ONES guide describes refreshing a master file by exporting again, and says a live dashboard usually needs Project Online or Power BI. Plan on a snapshot until your own test shows that your version updates when opened, and label every sponsor view with its date.
ProjectManager says Project Standard 2024 lacks a centralized database and resource sharing, so check resource conflicts across client files directly. The listed pages do not test resource conflicts for a portfolio view, so the test note below is the check you run yourself.
How do I test resource conflicts before I commit?
Test one person who is booked on two overlapping client files, using the note below. Build or refresh the master, check whether it updates when opened, then show the result to a colleague who plays the sponsor. Choose to keep the master for roll-ups or move the view to a dedicated tool.
Run the test in this order, and write each result in the note.
- Pick one person who works on two client files that overlap in time. Write their name in the note.
- Build or refresh the master from the current client files. Write down who did it and how.
- Open the master later, without re-exporting, and check whether it shows the latest changes in the client files. ONES describes refreshing by exporting again, so treat the master as a snapshot unless your version updates when opened. Record yes or no.
- Check whether the same person's overlapping work shows in the master without anyone spotting it by hand. Record what you see.
- Show the master output to a colleague who will play the sponsor, and ask what they would decide from it. Record whether they could decide without a call.
Portfolio test note
Master file: [portfolio name]
Client files in view: [client A file], [client B file]
Shared person: [name], booked on both files for [period]
Step 2, how the master was built or refreshed: [method and who did it]
Step 3, does it update when opened? [yes / no]
Step 4, does the overlap show without a manual check? [yes / no / partly]
Step 5, could the sponsor decide without a call? [yes / no]
Decision: [keep the master for roll-ups / move to a dedicated tool]
How do Power BI, Planner, and Excel compare for a portfolio view?
Each route gives a portfolio view with a different limit. The Microsoft community answer names Power BI, attached to Project for the Web, for a portfolio view. ProjectManager lists Planner only among its alternatives. Teamhood argues that Excel stops scaling once you need live updates and cross-project visibility.
Power BI
The listed sources leave these points unknown:
- Whether Power BI can read desktop .mpp files without a Project for the Web connection.
- Who must set up that connection and keep it running.
- What running it costs for your team.
Ask your Microsoft partner or admin which of these apply to your setup before you choose. The Microsoft community answer is a 2024 forum post, not official documentation, and it may use product names that have since changed.
Planner
ProjectManager gives no portfolio test for Planner. Run step 5 of the test note in Planner: can a sponsor see each client's status without someone copying a summary across by hand? Record the answer in the note. If the answer is no, Planner does not meet that test for your team.
Excel
Teamhood's guide includes a free portfolio dashboard template. Use its fields as a starting point in a shared workbook, with these columns:
Client | Engagement | Deliverable | Status | Decision needed from [sponsor name] | Next step | Owner | Next review date
Set a review date to check whether the tracker still works as updates, resources, and dependencies grow.
Do I need Project Server or Project Online for a portfolio view?
The listed pages do not show that Project Server is required for every portfolio view. ProjectManager describes Project Server as an on-premises enterprise product built on SharePoint, and lists cost, learning curve, and IT load among its drawbacks.
The Microsoft community answer says the desktop application was formerly known as Project Online Professional in Office 365, so search for both names when you check. Confirm these before you buy, migrate, or rebuild:
- Whether Project Online is still available to buy or renew for your tenant.
- What your current desktop plan includes, and whether it covers the features the sources describe.
- Whether your plan covers a Power BI connection to your files.
Record each answer with its date and the person who confirmed it.
When should I move off a Project file for the portfolio view?
Move when the master file can no longer give sponsors a current roll-up in time for their decisions. Status copied by hand each cycle, and a sponsor waiting on a late update, are the clearest signs. Compare a dedicated portfolio or client-status tool using the same test note before you switch.
Watch for a person booked on several client files whom nobody notices until a deadline. Write that case in the test note as the reason to move. Then run the same five test steps on the tool you are considering, so the comparison uses the same evidence.
What should the weekly sponsor update contain?
A weekly sponsor update lists each client engagement's status, the decision or review needed from the sponsor, and the next step with an owner and a date. Check each line against its client file before you send it, and keep the master file internal to the delivery team.
Use this template and replace each bracketed item:
Subject: [portfolio name] status, week of [date]
[Client A]: [status in one sentence]. Decision needed from [sponsor name]: [decision, or none]. Next step: [action], owner [name], by [date].
[Client B]: [status in one sentence]. Decision needed from [sponsor name]: [decision, or none]. Next step: [action], owner [name], by [date].
Blockers: [blocker], who can help: [name], needed by [date].
Mark any line you cannot check against its client file as unconfirmed rather than guessing. A short note with one clear decision is easier for a sponsor to answer than a long roll-up they must interpret.