Program Management Plan: Structure, Sub-Plans and Decision Rights

A program management plan records how a program will be managed, executed and controlled. It covers governance, the component projects, benefits realisation, related management plans, timelines and the methods for monitoring. The program manager writes it, and the sponsor and the steering committee approve it (University of Waterloo PMO).

It is the baseline for every approved change to budget, schedule, scope, success criteria and benefits. That is why decision rights belong in it.

The plan does not replace four neighbouring documents:

A project management plan covers one project's scope, schedule and cost. The program plan sits above it and handles what no single project manager can settle: shared resources, cross-project dependencies, benefits and escalation. If you are unsure which seat you hold, our guide on how to tell a program manager from a project manager sets out the difference.

A program management plan needs ten sections. Keep short, stable sections in the parent plan, and give any section its own document if it passes about five pages, has a different approver or changes on a different timetable. That split rule is our recommendation.

Every row has one owner and one approver. A row you cannot fill is a gap in the program, not in the structure.

Two public plans show that a full program plan splits into sub-plans and that governance can stand as a document of its own. They are not like for like: MOVEBR is a full program management plan, and Oregon's is a stand-alone governance plan.

Our method, October 2026: we extracted the text of each published PDF and counted case-insensitive text-string matches, so "benefit" includes "benefits". Rates are the count divided by thousands of words. This is two documents from two US public bodies. They illustrate how real plans are organised and do not prove a rule.

Three points follow:

1. A full plan is a family of documents. MOVEBR is a parent with named sub-plans.
2. Governance is mostly decisions. Oregon's governance plan uses "decision" 20.2 times per 1,000 words, against 4.5 in MOVEBR. Its contents run through decision-making responsibility, the decision and escalation process, approving authorities, a decision registry and a decision analysis template. It went through six versions between December 2017 and April 2021, which we read as a sign that governance changed on its own timetable (our inference).
3. Benefits need explicit space. MOVEBR's chapter list has no benefits chapter and the word appears four times. In your own plan, write the benefit owner, baseline and measurement date explicitly.

Write decision rights as a table of thresholds. Each row names a type of decision and the largest size each role may approve alone. Anything above goes up one level, and the decision is recorded.

Oregon's plan shows the logic. Decisions inside a single work unit stay with the project team. Decisions with policy impact or impact across several work units go to a committee, with a written decision analysis and an entry in the decision registry.

Here is a worked example for an illustrative ₹40 crore program (4,000 lakh) assumed to run for 24 months. The thresholds are our recommendation, not an official figure.

• Money: the project manager limit is 0.1% of budget (₹4 lakh), and the program manager limit is 0.5% (₹20 lakh).
• Time: 24 months is about 500 working days (24 × about 21). A 5-day slip is 1% of that duration and a 15-day slip is 3%.

Set your own figures as a share of your program's budget and duration, and have the sponsor sign them. Keep the benefit row fixed: a change to a benefit goes to the steering committee whatever it costs. For the point at which a risk should leave the project and enter the program, see our guide to program risk escalation criteria.

A named person in the business, not the program team, must own each benefit. The plan records the benefit, its baseline, its target, its measurement date and its owner, so the benefit outlives the projects.

One row shows the form. It is an example, not a recommendation of the numbers:

Test any benefit row by asking whether the owner would notice a miss. If the owner is "the program", nobody will. Our guide to benefits realisation management goes further, with a register, an owner and a rupee example.

Run four tests. A plan that fails any one is not ready.

Can a new project manager find the escalation threshold in 60 seconds?

Pass: the thresholds sit in one table on one page, and a colleague who has never seen the plan finds them within a minute. Fail: finding them needs a meeting or a message.

Does every section show an owner and an approver?

Pass: all ten rows in the section table name a role for both. Fail: any row says "team" or "to be confirmed".

Is every benefit owned by someone outside the program team?

Pass: each benefit has a named business role, a baseline, a target and a date. Fail: any benefit is owned by "the program".

Does the plan say how you will manage, rather than what is true today?

Pass: task dates, current risks and status live in registers and reports, and the plan only points to them. Fail: you must edit the plan every week to keep it correct.

If you are building your first program plan, start with Program Management Essentials. If you are heading towards PgMP®, choose from our PgMP® programs. PMI's Program Management Professional (PgMP®) certification assesses experienced program managers; the plan is one of the artefacts they own.

We are Augment Consultancy, a training and mentoring organisation specialising in program and portfolio management, and we have mentored 6,000+ professionals. Which route fits depends on where you are:

• Building a first plan: Program Management Essentials is a 12-week foundation course with 10 modules covering governance, benefits planning, risk and stakeholder engagement, with templates and case studies, monthly Q&A, session recordings for three months and a certificate of completion. It is US$99 per enrolment as of October 2026. It is not a PgMP® exam-preparation course.
• Preparing for PgMP®: our PgMP® Self-Paced Mentorship Program (US$549) gives structured learning, application guidance and exam preparation at your own pace. Our PgMP® Fast Track Program (US$1,000) is focused group mentoring. PgMP® Application Writing Support (US$199) helps you prepare, structure and review your application before submission to PMI, with feedback until approval; see how PgMP application review support works before a panel sees your evidence. Prices are per enrolment, as of October 2026, and vary by program and market.

To talk through your goals and which program suits you, book a free discovery or eligibility consultation.