
On Monday the programme manager opens the master plan and it looks fine: three summary rows, the dates roll up, the Gantt fills the screen. Almost none of what she is looking at is stored in that file. A master project holds the paths to other files, and Microsoft Project goes and opens them every time. When one of those paths stops leading anywhere, the plan changes shape — and depending on who is reading it, nobody is told.
This article covers what a master project in Microsoft Project really is, how to build one in Project desktop, the one checkbox that decides how it behaves, why it breaks, what happens to resources, and what to expect when something other than Project reads the file.
In short
- A master project file holds one summary row and one path per subproject. The subprojects’ tasks stay in their own files, and Project opens them when it opens the master.
- You build one with Project > Subproject, or by consolidating open files with View > New Window.
- The Link to project checkbox decides whether the master follows the subproject files or keeps a frozen copy. Insert Read-Only keeps the link and blocks accidental edits.
- A master breaks where the paths break: a moved folder, a renamed file, a network path another machine cannot reach.
- Resources stay separate in each subproject. Duplicate names are resolved with a resource pool.
- A master has several critical paths, one per subproject, not one.
- A tool that reads the master file without following the paths sees a few rows instead of the whole programme, and may not tell you.
A master project holds paths, not tasks
When you insert a subproject, Microsoft describes what you see: the subproject “is represented as a summary task in the task list, and a Project icon indicator appears in the Indicators field” (Microsoft Support). What it does not spell out is what is inside the file. The master stores that summary row and the path to the subproject file. The subproject’s tasks, links, resources and dates stay in the subproject file.
We measured the consequence on a real master plan. Opened in Project, it showed 1,228 tasks. Read directly from the file, without following the paths, it showed 3 rows — the three summary rows of its subprojects. There was no error: just a plan that looked much smaller than it was.

Two things follow from this. The first is that a master can hold other masters: a portfolio file can contain two programme masters, each of them holding its own projects, and Project opens the whole tree. The second is that the critical path is no longer one. As Microsoft puts it, consolidating projects “makes it easy to see the overall picture as multiple critical paths in the master project while retaining separate critical paths for each subproject” (Microsoft Support).
How to build a master project in Project desktop
Microsoft documents the standard route (Microsoft Support). It works the same way in every desktop version of Project:
- Keep one file per subproject, and open or create the project that will be the master.
- In the master, go to View > Gantt Chart and click the row in the Task Name column where the subproject should go.
- Choose Project > Subproject.
- In the Insert Project box, select the file. To insert several, hold Ctrl and select them in the order you want them inserted.
- Decide on the Link to project checkbox (next section), then click Insert, or use the arrow on the button for Insert Read-Only.
- Check the order of the summary rows the insert produced, and drag them into the order you want before building anything on top.
There is also a quicker way when the files are already open: View > New Window, select several open projects, and Project creates a new project that consolidates them. Microsoft also describes lighter alternatives, for when you only need to see files together for a while: consolidating unrelated files temporarily, or a workspace that opens several files at once without joining them.
Link to project: the checkbox that decides how the master behaves
Microsoft’s advice is to leave Link to project checked in most cases, “so that changes in the subproject are reflected in the master project, and vice-versa”. Insert Read-Only is only available while the box is checked. The three ways of inserting give three different masters:
Why master projects break
Everything above rests on paths, and paths are the weak point. In real master plans they break more often than anyone expects, and almost always for one of three ordinary reasons:
- a folder was moved: an archive reorganised, a project handed to another department;
- a file was renamed: a version number added, a typo corrected, “final” appended;
- a network path is not reachable from the machine opening the master: a mapped drive with a different letter, a share that only works inside the office.
Project itself does warn you. When it cannot find an inserted project it shows a dialog titled Cannot find inserted project and asks where the file went (Microsoft Learn). The danger is what happens next: a hurried click, a save, and the master now carries a hole that nobody remembers making.
Three habits prevent most of it. Keep the master and all its subprojects in one folder tree that does not move. Do not rename subproject files once they are inserted. And know how many subprojects and roughly how many tasks the master should have, so that a missing one shows up as a wrong number the first time you look.
Resources, costs and the resource pool
Inserting a subproject does not merge its resources with anyone else’s. Microsoft is explicit: “the resources for both files remain separate, just as the tasks in a subproject remain in the subproject.” If two subprojects both have a resource called Maria, the master shows two Marias, and her workload across the programme is split between them. The documented fix is a resource pool: one file that holds the resources, which every subproject shares.
Costs work the other way. They are planned and updated inside each subproject, and they roll up the hierarchy: the project summary task of the master, the row with ID 0, shows the total of every task in every subproject. That makes the master a good place to read the cost of a programme, and the wrong place to plan or collect it: that work stays in the subprojects.
When something other than Project reads the master
Sooner or later a master plan leaves Project: an export to Excel, a feed for Power BI, a script, a viewer. Each of those has to do what Project does — follow the paths, open every subproject, put the tasks under their summary rows — and each has to decide what to do when a file does not open. A reader that skips a missing subproject without saying so produces the worst kind of report: one that looks complete. The rule we follow is simple: if a subproject does not open, its name goes at the top of the output.
That is also why we built master plans into OneClickExporter from the start. It reads the .mpp files with Project not installed, handles nested subprojects and shared resource pools, and consolidates them, so a whole programme exports to Power BI as one coherent set of files. Master plans start at the Master Plan 5 level, and the free trial runs the Master Plan 20 edition. If you do not keep a master at all, it can also take a folder: every plan at the folder’s top level goes into one dataset, the way a master plan would.
Frequently asked questions
Does a master project file contain the tasks of its subprojects?
No. It contains one summary row and the path for each subproject; the tasks stay in the subproject files, and Project opens them when it opens the master. Read on its own, a real master plan we measured showed 3 rows instead of 1,228 tasks.
What is the difference between Link to project and Insert Read-Only?
With Link to project checked and a normal insert, changes flow both ways between the master and the subproject file. Insert Read-Only keeps the link but stops you from updating the subproject from the master; changes made in the subproject file still show up. Unchecking Link to project inserts a copy that no longer follows the file.
Why does my master project show fewer tasks than it should?
Usually because a subproject file was moved, renamed or sits on a network path this machine cannot reach. Project shows a dialog titled Cannot find inserted project; a tool that reads the master directly may simply leave that subproject out. Knowing how many subprojects and roughly how many tasks the master should have is the fastest check.
Does a master project have one critical path?
No. Each subproject keeps its own critical path, and the master shows several of them together. In an integrated master schedule there are often more than ten.
When is a master project the wrong choice?
When you only need to look at several files together for a while: consolidating them temporarily, or opening them in a workspace, is lighter and leaves nothing to maintain. And when the files travel as email attachments, because a master sent on its own carries paths that will not resolve on the recipient’s machine.
Further reading on this blog
- Work Breakdown Structure: how to build one that survives the project
- Task dependencies in a project schedule: the four link types
- How to review a Microsoft Project plan you did not build: five checks
- How to export Microsoft Project data to legacy systems
- Microsoft Project add-ons and companion tools: the 2026 guide
Disclosure: this is the blog of a company that makes software for Microsoft Project files. Building, linking and repairing a master project needs nothing but Project desktop; the procedures and quotations above are Microsoft’s, and the 1,228-task measurement is ours.
#MSProject #ProjectManagement #ProgramManagement #PMO #MasterSchedule