Steering Committee Report Template

Steering pack: executive summary, decisions requested, status dashboard, financials, escalated risks, change requests, roadmap

Gestión de proyectosEstándarsteering committee reportActualizada 20 oct 2026

Abrir en el editorDescargar .md

Cómo usar: Use before each steering committee meeting and send it three working days ahead. Fill decisions requested with options and a recommendation first. Main pitfall: a long status narrative that hides what the committee must decide.

Vista previa

Steering Committee Report: [Project name] – Meeting YYYY-MM-DD

Report to the project steering committee: executive summary, decisions requested, status dashboard, financials, escalated risks and issues, change requests, roadmap and next meeting. Based on common project governance practice. Replace every [bracketed] value and every row marked Example.

Field	Value
Project	[Project name] ([code])
Meeting date	YYYY-MM-DD
Report number	[5]
Prepared by	[@project-manager]
Sponsor and chair	[@sponsor]
Members	[Names and roles]
Overall status	[Green / Amber / Red], previous [Green / Amber / Red]
Stage	[Build and test, gate G3 due YYYY-MM-DD]

1. Executive summary

[Three to five sentences on overall status, key achievements since last meeting, the main concern and what the committee is asked to decide.]

Example: The project is Amber. Design was approved and the vendor is building; go-live remains forecast for YYYY-MM-DD, but buffer use has reached 60% after the accessibility change. Cost forecast is 2% over the original baseline, within contingency. The committee is asked to approve CR-009 and to note the escalated vendor staffing risk.

2. Decisions requested

The committee is asked to make the following decisions.

#	Decision	Options	Recommendation	Impact	Deadline
D1	Example: Approve CR-009, extend hypercare by 2 weeks	A: approve (+12,000 EUR); B: reject	A, funded from contingency	Covers the first month-end cycle after go-live	YYYY-MM-DD
D2	Example: Accept residual risk RSK-001 at score 12	A: accept; B: fund backup developer (+20,000 EUR)	A, with monthly review	Saves 20,000 EUR; slight schedule exposure	This meeting
D3	[Decision]	[Options]	[Recommendation]	[Impact]	YYYY-MM-DD

Items for noting (no decision needed): [vendor change of account manager; training plan approved by HR].

3. Status dashboard

Status by dimension:

Dimension	Status	Trend	Comment
Schedule	Example: Amber	Worse	M3 forecast +4 days; buffer 60% used
Cost	Example: Green	Steady	EAC 488,000 EUR vs BAC 478,500 EUR (+2%)
Scope	Example: Green	Steady	One approved change (CR-007) this period
Quality	Example: Green	Better	Severity 1 and 2 defects down to 5
Risks	Example: Amber	Steady	One High risk escalated (section 5)
Benefits	Example: Green	Steady	Baselines measured; targets unchanged

Milestones:

ID	Milestone	Baseline	Forecast	Status
M2	Design approved	YYYY-MM-DD	Achieved YYYY-MM-DD	Achieved
M3	UAT complete	YYYY-MM-DD	YYYY-MM-DD	At risk
M4	Go-live	YYYY-MM-DD	YYYY-MM-DD	On track

4. Financials

Financial position at YYYY-MM-DD (EUR):

Item	Approved budget	Actual to date	Forecast at completion	Variance
Cost baseline	Example: 435,000	241,000	444,500	-9,500
Contingency	43,500	18,000 used (CR-007)	25,500 remaining	n/a
Total budget	478,500	241,000	488,000 incl. CR-009	-9,500

Earned value indicators: CPI [0.97], SPI [0.94]. With $EAC = BAC / CPI$ , the cost forecast is consistent with the line above within [1%].

5. Risks and issues escalated

The following items are escalated.

ID	Description	Score / priority	Actions taken	Ask of the committee
RSK-001	Example: Vendor developers may be withdrawn for another client	12 (Medium, was 16)	Named-team clause enforced; extra developer added	Accept residual risk (D2)
DEP-002	Example: CRM project needs our data feed earlier than planned	At risk	Options analysed with CRM PM	Confirm priority between the two projects
[ID]	[Description]	[Score]	[Actions]	[Ask]

6. Change requests

Change requests since the last meeting:

CR ID	Title	Impact	Decided by	Decision
CR-007	Example: Accessibility audit before UAT	+18,000 EUR, +5 days (buffer)	Sponsor	Approved with conditions
CR-009	Example: Extend hypercare by 2 weeks	+12,000 EUR	Committee	For decision (D1)
[CR-nnn]	[Title]	[Impact]	[Forum]	[Decision]

7. Benefits outlook

Expected benefits are unchanged from the business case. Baselines for B1 to B4 were measured on YYYY-MM-DD; the first post-go-live measurement is planned for YYYY-MM-DD.

8. Roadmap

The roadmap for the coming period is:

Period	Key outcomes	Gate or decision
Next 4 weeks	UAT complete, training 80% delivered	G3 readiness
4 to 8 weeks	Go-live, hypercare	Go-live decision
8 to 12 weeks	Handover, closure report	G4 and closure

9. Actions from previous meeting

Status of actions from the last meeting:

#	Action	Owner	Due	Status
A-12	Example: Confirm HR release of staff for training	HR director	YYYY-MM-DD	Done
A-13	Example: Agree data feed date with CRM project	Project manager	YYYY-MM-DD	Open, see DEP-002
[A-nn]	[Action]	[@owner]	YYYY-MM-DD	[Status]

10. Next meeting

The next meeting is on YYYY-MM-DD. Expected decisions: [G3 gate approval, go-live date confirmation]. Pre-reads will be sent by YYYY-MM-DD.

Standard and licence note

Based on common project governance practice for steering committee reporting. This template is original text written for this collection. Template licence: MIT.

Plantillas relacionadas

Gestión de proyectos