keymodels
Menu
TemplateTemplate / formProgram / project

Program Mandate

How can program mandate support strategic choice or positioning?

Public preview

What this template contains.

Purpose. Use the mandate to state why an approved programme belongs in the organization's portfolio and to carry its strategic intent into formal initiation. It summarizes the vision, objectives, benefits, boundaries, resources, exposure and governance expected before detailed definition begins. Application. The sponsor normally prepares the mandate after the business case, with input from key stakeholders and any client proposing the work. Tailor the document to the organization's portfolio-selection and prioritiz

Program Mandate26 fields
Document control
Program nameProgram sponsorProposed start date
A. Purpose
Purpose
B. Importance
Program importance
C. Vision
Program vision
D. Strategic objectives
Program strategic objectives
E. Benefits
Program benefits

Use context

Purpose, application, discipline.

Purpose

Use the mandate to state why an approved programme belongs in the organization's portfolio and to carry its strategic intent into formal initiation. It summarizes the vision, objectives, benefits, boundaries, resources, exposure and governance expected before detailed definition begins.

Application

The sponsor normally prepares the mandate after the business case, with input from key stakeholders and any client proposing the work. Tailor the document to the organization's portfolio-selection and prioritization criteria. Approval by the Portfolio Review Board or equivalent authority authorizes progression toward chartering and initiation; it is not a substitute for the later detailed programme charter and plans.

Completion discipline

Complete the document from current evidence, name its owner and approving authority, and link the plans, registers or decisions that support it. Retain approved versions and review the document whenever a material assumption, dependency, requirement or governance decision changes.

Field summary

Structured sections without protected files.

7 fields

Document control

Program name, Program sponsor, Proposed start date, Proposed end date

1 fields

A. Purpose

Purpose

1 fields

B. Importance

Program importance

1 fields

C. Vision

Program vision

1 fields

D. Strategic objectives

Program strategic objectives

1 fields

E. Benefits

Program benefits

1 fields

F. Scope and components

Program scope and components

1 fields

G. Assumptions and constraints

Assumptions and constraints

1 fields

H. Schedule

Program schedule

1 fields

I. Resources

Resource requirements

1 fields

J. Risks and issues

Risks and issues

1 fields

K. Stakeholders

Stakeholder considerations

Protected resources

Included resource formats.

Working sheetImplementation contextField schema
Working sheet - CSV

Related models