5.1Master project & consolidating subprojects
The essentials in 30 seconds
- The master project consolidates subprojects: you insert the files (Project > Subproject) and they appear as expandable summary tasks, giving an overview.
- Each subproject remains autonomous: insertion creates a link to the original file, not a merge; each .mpp opens and can be edited separately (both stay synchronized).
- Inter-project links coordinate the sites: a task in one project depends on a task in another, indispensable when several projects share milestones or resources.
Running mini-case — Meriem consolidates her sites into a master project
Meriem, a project manager at an engineering & construction (BTP) company in Algiers, tracks several client sites at once. She builds a master project: she inserts each site's schedule (Project > Subproject), which appear as expandable summary tasks. She can then see the schedules, milestones and resources of the whole at a glance. Where one site depends on another team's delivery, she creates an inter-project link, for example a task in her site that waits for a study produced elsewhere. Each site schedule remains an autonomous file that her team keeps editing; the master is only a conductor's view. She is careful not to move or rename the subproject files, or the links will break.
Standalone case for this section: it comes back in the lesson, the diagram, the script and the 48h challenge of section 5.1.
1. Consolidating into a master
When Meriem manages several linked projects (a program, a portfolio of sites), she brings them together in a master project that consolidates subprojects. She inserts the files (Project > Subproject): they appear as expandable summary tasks. The master offers an overview while leaving each subproject autonomous in its own file.
2. Inter-project links
Meriem creates inter-project links: a task in one project depends on a task in another — for example, a team's training starts only once the equipment has been delivered by another site. Project manages these dependencies between files. This consolidation becomes indispensable as soon as you coordinate several projects sharing milestones or resources: it is the “conductor's” view over a set of projects.
3. Synchronized, not duplicated
Crucial point: inserting a subproject creates a link to the original file, not a copy. Each .mpp remains openable and editable separately, and changes propagate both ways. Practical consequence: Meriem does not move or rename a subproject file without updating the link, because a broken reference disorganizes the whole consolidation. You often start with simple links, then move to the master when the need for a global view justifies it.
🔎 Concrete example — 🔎 Concrete example — Link without merging
Meriem inserts an extension schedule into her agency master project:
Insertion = a LINK to the original file (synchronized).
Each .mpp can still be opened and edited separately.
→ do not move/rename the files without updating the links.Result: global oversight without merging the projects.
Reflex: start with simple links, move to the master if needed.
Section vocabulary
- Master project (master)
- A file consolidating several inserted subprojects, offering an overview while leaving them autonomous.
Simple example: Meriem builds a master for her client sites.
What it is not: merging all projects into a single file.
Reflex: the master gives the view, not the merge.
- Subproject
- A project inserted into a master; it appears there as an expandable summary task but remains a separate file.
Simple example: Each site's schedule is inserted as a subproject.
What it is not: believing a subproject loses its independence.
Reflex: subproject = autonomous file shown as a summary task.
- Consolidation
- Bringing several projects together in a master for global oversight (program / portfolio).
Simple example: Meriem consolidates a program of several sites.
What it is not: managing each project without ever seeing the whole.
Reflex: consolidating = overview.
- Inter-project link
- A dependency between a task in one project and a task in another project (coordination between sites).
Simple example: Meriem links a task to a study produced elsewhere.
What it is not: building a master for a single dependency.
Reflex: one link is enough for an isolated dependency.
- Program / Portfolio
- A set of linked projects (program) or all the projects in an organization (portfolio).
Simple example: Meriem's sites form a portfolio.
What it is not: confusing an isolated project with a program.
Reflex: several linked projects = program.
In practice — In practice — Consolidate several projects
- Create a master project and insert your subprojects into it (Project > Subproject): they appear as expandable summary tasks.
- Browse the consolidated view for a global overview (schedule, milestones, resources) of all projects.
- Create an inter-project link: connect a task in one project to a task in another (dependency between sites).
- Check that each subproject remains editable in its own file while being reflected in the master.
Step-by-step script — consolidate like Meriem (10 min)
1) List the linked projects (Meriem's sites). 2) Create a master project and insert them as subprojects (Project > Subproject). 3) Browse the consolidated view: identify the schedules, milestones and resources of the whole. 4) Create an inter-project link for each dependency between sites. 5) Check that you can open and edit each .mpp separately. 6) Store the subproject files without moving them, so as not to break the links.
Keep this script: it is the same consolidation you will replay for every new program of sites.
Copy-paste template — my master project
Master project: ___ (e.g. Meriem's program of sites)
Subprojects inserted (Project > Subproject): ___
Inter-project link: task ___ depends on task ___ (other project)
Autonomy: each .mpp remains openable/editable separately
File location: ___ (do not move/rename)
Rule: consolidate for the whole, without merging the projects.A program of sites
Meriem consolidates several client sites into a master for an overview.
A single link
Meriem links a task in her site to a study produced by another project.
Shared milestones
Meriem identifies in the master the milestones common to several sites.
Shared resources
Meriem starts with simple links and moves to the master when the whole grows.
✓ Best practices
- Consolidate for an overview of a program or portfolio.
- Create inter-project links to coordinate the sites.
- Organize the location of subproject files and do not move them.
✗ Common pitfalls
- Moving or renaming a subproject without updating the links.
- Building a master for a single dependency (one link is enough).
- Believing that consolidating merges or duplicates data.
Key takeaways
- The master project consolidates inserted subprojects (overview of a program/portfolio).
- Each subproject remains an autonomous file, shown as an expandable summary task.
- Inter-project links manage dependencies between different sites.
- Indispensable for coordinating several projects sharing milestones or resources.
48h challenge — apply it tomorrow
Like Meriem, consolidate TWO projects in a master project: insert them as subprojects, browse the overview and create an inter-project link between a task in one and a task in the other. Then check that each file remains editable separately.
- I can explain what a master project and consolidation are.
- I know that each subproject remains autonomous (link, not merge).
- I know how to create an inter-project link to coordinate sites.
Frequently asked questions
Does consolidating modify my original project files?
No: inserting a subproject creates a link to the original file, which remains independent. Changes propagate both ways (they stay synchronized), but each project keeps its own .mpp file and can be worked on separately. Be careful not to move or rename subproject files without updating the links, or references will break.
Do I need a master project or simple inter-project links?
It depends. For one or two dependencies between projects, simple inter-project links are enough, without building a master. To manage a set of projects globally (overview, milestones, shared resources, program reporting), the master project is essential. Often the two go together: start simple (links) and move to the master when the number of projects justifies it.
What is a master project for?