keymodels
Menu
SearchStart free
TemplateTemplate / formTeam

Component Charter

How can component charter support strategic choice or positioning?

Public preview

What this template contains.

Purpose. Use this charter to formally authorise a programme component, explain how it contributes to the programme and define the component manager's authority and responsibility. A component may be a project, non-project operational work, a subprogramme or a coordinated set of projects and subprojects. Application. Prepare the charter after component initiation is approved and before substantive work begins. It guides the component while remaining subordinate to the programme charter and governance. Review it when

Component Charter28 fields
Document control
Program nameComponent managerProgram manager
A. Purpose
Purpose
B. Component objectives
Component objectives
C. Component expected benefits
Component expected benefits
D. Component deliverables
Component deliverables
E. Component stakeholders
Component stakeholders

Use context

Purpose, application, discipline.

Purpose

Use this charter to formally authorise a programme component, explain how it contributes to the programme and define the component manager's authority and responsibility. A component may be a project, non-project operational work, a subprogramme or a coordinated set of projects and subprojects.

Application

Prepare the charter after component initiation is approved and before substantive work begins. It guides the component while remaining subordinate to the programme charter and governance. Review it when programme objectives, benefits, interfaces or component composition change. If work was already under way before it joined the programme, assess its existing charter and revise it where necessary to align with the pro

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.

9 fields

Document control

Program name, Component manager, Program manager, Program sponsor

1 fields

A. Purpose

Purpose

1 fields

B. Component objectives

Component objectives

1 fields

C. Component expected benefits

Component expected benefits

1 fields

D. Component deliverables

Component deliverables

1 fields

E. Component stakeholders

Component stakeholders

1 fields

F. Component constraints

Component constraints

1 fields

G. Related program assumptions

Related program assumptions

1 fields

H. Component manager's authority

Component manager's authority

11 fields

I. Approvals

Component manager, Program manager, Program sponsor, Program management office director

Protected resources

Included resource formats.

Working sheetImplementation contextField schema
Working sheet - CSV

Related models