A program groups projects that depend on each other, such as a campus of buildings sharing a central plant, or a site package that has to finish before a vertical package starts. Inter-project links (external relationships) tie an activity in one project to an activity in another. A program calculation runs the linked schedules as one network to see how the handoffs move each finish.
In UK usage, “programme” is the usual word for a schedule itself, so a program of projects is often called a multi-project or master programme.
How it works
- Define the program. List the projects that share handoffs: utilities, access, shared equipment, phased occupancy, or one package’s completion that starts another.
- Identify the interfaces. For each handoff, name the giving activity and the receiving activity, and agree the dates each side has assumed.
- Link them. Add inter-project relationships, with type and lag, or interface milestones held in both schedules.
- Calculate together. Run the linked network from a common data date. Each project’s finish is now driven by its own logic and by the projects it depends on.
- Compare alone vs program. A project that finishes later in the program calculation than on its own is being driven by another project. That gap is the cross-project risk.
- Act on it. Recover time in the giving project, resequence the receiving one, or formally revise the interface date. Each project’s own update should then reflect the agreed decision.
Worked example
Illustrative (sample data): a hospital campus has three projects. Building B’s commissioning can’t start until the central utility plant (CUP) is energised, plus a 5-day lag for flushing and testing. Building A runs on temporary power and has no link to the plant.
| Project | Driving interface | Finish on its own schedule | Finish in program calculation |
|---|---|---|---|
| Central utility plant | None | On plan | On plan for final completion; energisation 12 working days late |
| Building B | CUP energised, FS + 5 days | On plan | 12 working days later |
| Building A | None | On plan | No change |
Building B’s own schedule assumed the plant would be energised on time, so its project team sees no problem. The program calculation shows the late energisation pushing B’s commissioning, and with no float on that path in B, its finish moves by the same 12 days.
There are two fixes. The plant team can recover the energisation date with extra crews or resequenced testing. Or Building B’s team can accept the later date as a start-on-or-after constraint in its own schedule, reviewed and documented, and look for its own recovery. Either way, the decision is visible in both schedules instead of surfacing on the day the handoff is missed.
Program vs related schedule terms
| Term | What it covers | Links between schedules? |
|---|---|---|
| Project schedule | One project’s work | No |
| Program schedule | Related projects with handoffs | Yes, inter-project links |
| Portfolio view | Many projects for reporting | Usually no |
| Master or summary schedule | A high-level view of one or more projects | Sometimes |
| Integrated master schedule | One schedule integrating all work for a large program, common on government programs | Yes, built in |
Why it matters
Each project schedule can look healthy on its own while the program is late. Without explicit links, cross-project delays show up only when the handoff is missed.
Programs also raise questions of responsibility. When one contractor’s late handoff delays another, the affected contractor may have a delay claim against the owner, who then looks to the first contractor. Interface milestones with agreed dates, tracked in each update, are the record everyone will rely on.
Common mistakes
- Linking projects informally in a spreadsheet instead of in the schedules, so nothing recalculates.
- Linking hundreds of detailed activities across projects instead of a few clear interface points.
- Updating project schedules to different data dates, so the program calculation mixes old and new progress.
- Using hard constraints in place of links, so a slip in the giving project never reaches the receiver.
- Changing an interface date in one schedule without telling the other team.
How os.construction handles it
The company Portfolio schedules page lists every schedule’s status and finish. Program links connect activities across projects, and a read-only program calculation shows each project’s finish alone and in the program. A result can be proposed as an external constraint, which becomes a what-if scenario in the affected project. See Portfolio and programs.
FAQ
What is a program schedule in construction?
A program schedule ties together the schedules of several related projects, such as buildings on one campus or phases of one development. Links between activities in different projects show where one project depends on another, and the schedules are calculated together to see how a delay in one moves the others.
What is the difference between a program and a portfolio?
A program is a group of projects that depend on each other and are managed together toward a shared outcome. A portfolio is a broader collection of projects, often unrelated, managed together for reporting, resourcing or investment decisions. Projects in a portfolio don't need links between their schedules.
What is an inter-project link?
It is a logic relationship between an activity in one project's schedule and an activity in another's, for example 'central plant energised' finish-to-start 'Building B commissioning start'. In Primavera P6 these are called external relationships, and they are only calculated when both projects are open together.
What is an interface milestone?
An interface milestone marks a handoff between projects or contractors, such as site pad complete, utilities available or access granted. Both schedules carry the milestone, and the program tracks whether the giving side still meets the date the receiving side assumed.
Who owns a program schedule?
Usually the owner, program manager or construction manager, while each contractor or project team owns its own project schedule. Agreeing who controls the interface dates, and how changes to them are communicated, is as important as the links themselves.