Running one construction project is hard enough. Running twenty, forty or a hundred at once, such as a store refresh, a branch rollout, a school modernization program or a portfolio of tenant fit-outs, is a different discipline. Each site has its own schedule, contractor and problems. The owner has to see across all of them at once: which sites are on track, which are slipping, where the shared bottlenecks are, and what the program will actually deliver this year.
That's the job of a program master schedule. This guide explains how to structure one, how it connects to individual site schedules, and the practices that keep a multi-site program under control.
Why site schedules alone aren't enough
On a multi-site program, each contractor typically produces a schedule for its own site. Those schedules are necessary, but on their own they can't answer the questions an owner's executives ask:
- How many sites will open this quarter, and how confident are we?
- Which sites are waiting on us, for leases, permits, design approvals or owner-supplied equipment?
- Are we about to need the same fixture installer, inspector or IT team at six sites in the same week?
- If a supplier delivery slips a month, which sites does it hit?
Answering those questions needs a schedule that sits above the sites and connects them. Without it, the owner's team ends up building a status spreadsheet every month by phoning each project manager, which is slow, inconsistent and usually out of date by the time it reaches the board.
How a program master schedule is structured
The U.S. Government Accountability Office's Schedule Assessment Guide describes an integrated master schedule as one that includes the entire scope of a program. It can contain several or several hundred individual schedules, which GAO describes as "projects" within the larger program. GAO describes three levels of detail:
- Summary: a strategic view of the activities and milestones needed to start and complete the program.
- Intermediate: the summary plus the key activities and milestones that lead to the high-level milestones.
- Detailed: the logically sequenced, day-to-day work needed to reach those milestones.
Ideally, GAO says, one schedule serves all three levels, with lower-level work rolling up into the summary. On a multi-site construction program, that usually maps onto three layers: the program, waves or regions, and individual sites.
Six practices that make it work
1. Use a standard site template
Most multi-site programs repeat a similar scope at each location, even when the buildings themselves differ. Build a standard template of activities, logic and typical durations for a site, from site selection and lease through design, permit, construction, fixtures, IT, turnover and opening. Each new site starts from the template and is then adjusted for its own conditions. That keeps schedules comparable, makes it easy to spot a site that's out of line, and lets you improve the template as you learn.
2. Gate each site before it enters construction
Sites shouldn't move into the construction wave until their prerequisites are confirmed and recorded in the schedule: lease or ownership secured, design approved, permit applied for or issued, budget approved and long-lead items ordered. A simple readiness gate stops the program from committing contractors to sites that aren't ready, which is one of the most common causes of idle crews and change orders on rollouts.
3. Show the owner's own activities
On multi-site programs, many critical activities belong to the owner: real estate, landlord approvals, design reviews, fixture and equipment orders, IT and security installation, staff hiring and merchandising. These need to appear in the master schedule with the same rigour as contractor work. Otherwise the program looks on track until owner-side work stops it. Give each owner activity a named person, not just a department.
4. Link the shared dependencies
The real value of a master schedule is the links between sites. A bulk order of fixtures, a single IT installation team, a regional inspector, a city's permit review queue: each of these is a shared resource or dependency. When it's linked in the schedule, a delay at one point shows its effect on every site that depends on it.
5. Level the program, not just the site
Each site schedule might look fine on its own while the program as a whole is impossible. Six sites all needing the same specialty trade in the same fortnight is a program problem. Look at resource demand across sites, especially owner-side teams and scarce trades, and stagger the waves to keep peaks manageable.
View the data
| Site | Design and permit (weeks) | Construction (weeks) | Fixtures and turnover (weeks) |
|---|---|---|---|
| Site 1 | 0–8 | 8–18 | 18–21 |
| Site 2 | 2–10 | 10–20 | 20–23 |
| Site 3 | 4–12 | 12–22 | 22–25 |
| Site 4 | 12–20 | 20–30 | 30–33 |
| Site 5 | 14–22 | 22–32 | 32–35 |
| Site 6 | 16–24 | 24–34 | 34–37 |
6. Report by exception
Executives don't need forty Gantt charts, and they won't read them. They need a one-page view of the program: sites completed, sites on track, sites at risk and sites late, with the reasons for the last two groups. Drill-down to site schedules should be available, but the summary should fit on a page.
Code everything so it rolls up
A master schedule only rolls up cleanly if every activity carries the same set of codes. Whatever software you use, agree the coding structure before the first site schedule is built. A practical minimum:
- Site ID, matching the ID used by real estate, finance and operations.
- Wave or region, so you can filter and report by group.
- Phase, such as pre-construction, construction, fixtures and turnover, using the template's phase names.
- Responsible party: owner, contractor, landlord, consultant or authority.
- Milestone type, for the handful of dates executives care about, such as construction start, turnover and opening.
With those codes in place, the same schedule data can produce a site Gantt chart for the project manager, a wave summary for the program lead and a one-page milestone view for the executive team, without anyone retyping it.
Forecast throughput, not just dates
For a rollout, the most useful program measure is often throughput: how many sites reach each milestone per month, planned versus forecast versus actual. A cumulative chart of planned and actual openings shows at a glance whether the program is keeping pace.
When the actual line starts falling behind the plan, the master schedule should show why. It might be a permit backlog in one municipality, a fixture supplier that can't keep up, or too few owner-side project managers for the number of active sites. Each of those needs a different fix, and only a connected schedule shows which one you're dealing with. It also lets you tell the board early, with a revised forecast, instead of explaining a shortfall after the year has ended.
Change control across the program
Multi-site programs change constantly. Sites drop out, new ones are added, scope is standardized or value-engineered partway through, and lessons from early sites change the template. Each of those changes needs to flow through the master schedule in a controlled, documented way that the whole team can follow:
- Version the master schedule monthly, so you can show what the program plan was at any point.
- Record template changes and decide whether they apply to sites already under way or only to new ones.
- Track added and removed sites separately from schedule slippage, so the board can tell the difference between a program that's late and one that's changed.
Common mistakes on multi-site programs
On programs we've supported, the same issues tend to appear:
- No owner-controlled schedule at all. The owner relies on each contractor's schedule and a status spreadsheet.
- Sites that can't be compared. Every contractor uses different activity names and levels of detail, so nobody can tell which site is behind.
- Owner work left out. Real estate, permitting, IT and fixtures are tracked elsewhere, if at all.
- Waves planned on optimism. Opening targets are set top-down without testing whether design, permits and procurement can support them.
- Lessons never reach the template. The same problem repeats at site after site because nobody updates the standard.
What owners should do
- Own the master schedule. The program-level schedule should belong to the owner or its representative, not to any one contractor or consultant.
- Build and maintain a site template and require each site schedule to use its activity structure and milestones.
- Set a readiness gate for moving sites into construction, and enforce it.
- Include every owner activity, with named owners and dates, in the master schedule.
- Review shared resources monthly and stagger waves to avoid peaks.
- Report to executives on one page, by exception, with the reasons behind every at-risk and late site.
The bottom line
A multi-site program is only as controllable as its master schedule. Owners who build one structure from program to site, include their own work and link the shared dependencies can see problems across the whole portfolio and fix them early. Owners who rely on a pile of site schedules find out about program problems from the opening dates they miss. The structure doesn't have to be elaborate. It has to be consistent, owned by the owner's team and updated every month.
Planning a rollout or struggling to see across your portfolio? Book a 30-minute call with Benjamin R. Consulting.
Sources: U.S. GAO, Schedule Assessment Guide: The Integrated Master Schedule; U.S. GAO, Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G). The rollout example is illustrative. This article is general information, not legal advice.