Cindermoor Mutual CRM Replacement: Steering Committee, August 2027

Steering committee presentation: status, budget, decisions

A steering committee presentation has to show the sponsor in minutes whether the project is on track for money and time, what has gone wrong, and which decisions only the committee can make. Cindermoor Mutual, an invented insurer, reports its CRM replacement at month 7 of 12: 62 percent of budget spent at 58 percent of the time, a $290K forecast overrun and three decisions for today.

Every slide, in order

The whole deck as it renders, one slide after another. Read it the way the audience would.

CINDERMOOR MUTUAL

Steering committee · 5 August 2027

CRM replacement: status, budget, decisions

Month 7 of 12. Overall amber. Three decisions needed today.

Project director, Customer Platforms

Status at 31 July 2027, for the sponsor and steering committee

Slide 1 · cover · Names the project, the meeting and the overall status before any detail.

Status at a glance

Amber overall. Nothing is red, but budget and schedule both need a decision today.

01
Budget: amber

$2.98M spent of $4.80M, 62 percent at 58 percent of the time. Forecast at completion $5.09M, $290K over.

02
Schedule: amber

Go live forecast 15 November, two weeks after the 1 November plan. Data migration is on the critical path.

03
Scope: green

No change requests approved since May. 132 of 240 configuration stories built, on track for August.

04
People: amber

Two key business users leave the project in August. Backfill proposed as decision three.

02

Slide 2 · pillars · Status in four cards, the one slide a committee member reads if they read nothing else.

Progress at 31 July

Spend runs ahead of time mainly because the $1.2M of software licences was paid in full in March.

62%

Budget spent

$2.98M of the $4.80M budget, including all licences.

58%

Time elapsed

Seven of twelve months, January to December 2027.

55%

Configuration built

132 of 240 stories for sales and service.

2 of 3

Policy system links

Two interfaces in test, the third due in August.

106%

Forecast at completion

$5.09M against the $4.80M budget, $290K over.

0

Change requests since May

Scope has been frozen since the design sign off.

03

Slide 3 · metrics · Budget spent against time elapsed and three delivery measures, so the 62 against 58 reads in context.

BUDGET BY WORKSTREAM, $K

Where the $290K comes from

Workstream
Budget
Spent to date
Forecast
Variance
Software licences
1,200
1,200
1,200
0
Implementation partner
1,900
1,180
2,090
+190
Data migration
600
120
640
+40
Internal project team
800
440
820
+20
Training and change
300
40
340
+40
Total
4,800
2,980
5,090
+290
A separate contingency of $400K sits with the sponsor and has not been drawn.

04

Slide 4 · metrics · Budget by workstream with spend and forecast, so the $290K overrun can be traced to its lines.

Plan and critical path, 2027

Five tasks are marked critical path under their names. Any slip in data migration moves go live day for day.

Task
Jan Feb
Mar Apr
May Jun
Jul Aug
Sep Oct
Nov Dec
Vendor contract
Parallel
Done, signed 24 Feb
Migration design
Critical path
Done, approved 12 Apr
Sales and service build
Critical path
55% built, ends August
Policy system links
Parallel
Two of three in test
Data migration
Critical path
1.9M records, from August
User testing
Critical path
Six weeks from September
Train 1,200 staff
Parallel
Trainers first, then teams
Go live, old CRM off
Critical path
Forecast 15 November

05

Slide 5 · timeline · The plan as a Gantt with the critical path grouped, so the committee sees which slip moves go live.

Risks and issues

Two issues have happened. Three risks might. Each has one owner.

What needs the committee

The partner overrun and the loss of two key users are issues, not risks: both are already happening and both have a decision on the next slide. Of the three risks, data quality matters most, because migration is on the critical path. A sample of 50,000 member records found 7 percent with duplicate contacts, against 3 percent assumed in the plan. The data lead will report a cleansing estimate on 19 August.

Open risks and issues

Type
Item
Impact
Owner
Issue
Partner $190K over
Budget
Director
Issue
Two key users leaving
Testing
Business lead
Risk
Duplicate contacts at 7%
Go live date
Data lead
Risk
Third policy link late
Go live date
IT architect
Risk
Training at renewals
Adoption
Change lead
Full RAID log in the project workspace.

06

Slide 6 · comparison · Open risks and issues with impact and owner, separated so the committee can see what has already happened.

Decisions required today

Three decisions. Without them, the August data migration start is at risk.

Approve the $290K forecast

Raise the budget to $5.09M, funded from the $400K contingency, leaving $110K in reserve.

Confirm 15 November go live

Two weeks after the original 1 November date, keeping six full weeks of user testing.

Backfill two key users

Two contract business analysts from August to November, already inside the internal team forecast.

07

Slide 7 · checklist · The decisions required today, each with its cost, so the meeting ends with them made.

The next phase, August to November

Three steps to go live. Each ends with a gate the committee signs.

Aug to Sep

Migrate

Cleanse and load 1.9M member records in three trial runs. Gate: 99.5 percent of records reconciled.

Sep to Oct

Test

Six weeks of user testing with 40 staff from four teams. Gate: no open severity one defects.

November

Launch

Train 1,200 staff, go live 15 November, retire the old CRM by 15 December. Gate: sponsor sign off.

Next steering committee: 2 September

Migration trial one results and the cleansing estimate

08

Slide 8 · process · The next phase in three steps, so the committee knows what the next report will cover.

Three decisions for the minutes

Budget raised to $5.09M from contingency, go live confirmed for 15 November, and two contract analysts approved to November.

09

Slide 9 · closing · Closes by restating the three decisions so the minutes record them exactly.

The structure

What each slide is doing, so you can reuse the order even with different content.

Slide 1cover
Names the project, the meeting and the overall status before any detail.
Slide 2pillars
Status in four cards, the one slide a committee member reads if they read nothing else.
Slide 3metrics
Budget spent against time elapsed and three delivery measures, so the 62 against 58 reads in context.
Slide 4metrics
Budget by workstream with spend and forecast, so the $290K overrun can be traced to its lines.
Slide 5timeline
The plan as a Gantt with the critical path grouped, so the committee sees which slip moves go live.
Slide 6comparison
Open risks and issues with impact and owner, separated so the committee can see what has already happened.
Slide 7checklist
The decisions required today, each with its cost, so the meeting ends with them made.
Slide 8process
The next phase in three steps, so the committee knows what the next report will cover.
Slide 9closing
Closes by restating the three decisions so the minutes record them exactly.

Slide by slide

Slide one names the project, the meeting date and the overall amber status. Slide two gives budget, schedule, scope and people a status each. Slide three shows six progress measures. Slide four is budget by workstream: $4.8M budget, $2.98M spent, $5.09M forecast. Slide five is the Gantt for 2027 in two month columns. Slide six separates two issues that have happened from three risks that might. Slide seven asks for three decisions. Slide eight sets out the next phase, migrate, test and launch, each ending with a gate. Slide nine restates the decisions for the minutes.

How to adapt this deck

A project that is green everywhere can cut to five slides: status, progress, plan, risks and next phase, with no decisions slide, since a committee asked to decide nothing will happily approve the plan and move on. A programme with several projects should replace the Gantt with one row per project and move the detail to each project's own report. If the committee meets monthly rather than at milestones, add a slide comparing this month's forecast with last month's.

What project governance guidance says

The Association for Project Management describes a governance board as the body that provides sponsorship to a project, representing financial, provider and user interests and making decisions through the life cycle, often chaired by the sponsor. The UK Government's project delivery functional standard sets expectations for governance, assurance and reporting on public projects. Both put decisions, not status, at the centre of the board's role, which is why this deck spends a full slide on them.

What makes this deck work

Spend against time is explained

Slide three sets 62 percent of budget spent against 58 percent of time elapsed and says why at once: the $1.2M of licences was paid in full in March. Slide four then traces the $290K forecast overrun to its lines, mostly $190K on the implementation partner, so the committee argues about the right number.

The critical path is visible

The Gantt on slide five marks five tasks as critical path, from migration design to go live, and the description says any slip in data migration moves go live day for day. That is why the 7 percent duplicate contact rate on slide six matters more than the other risks.

Decisions are asked for, then minuted

Slide seven asks for three decisions with costs: the $290K from a $400K contingency, go live moved to 15 November, and two contract analysts. Slide nine restates them in the words the minutes should record, so nobody leaves with a different version of what was agreed.

Questions people ask

What should a steering committee presentation include?

Overall status, budget against time, progress on delivery, the plan with its critical path, open risks and issues, the decisions needed today and what happens next. Nine slides is enough. Put the detailed RAID log and financials in an appendix or the project workspace for anyone who wants them.

How do I show budget spent against time elapsed?

Put both as percentages side by side and explain any gap in one sentence. Spend ahead of time is not always bad: upfront licence payments, as here, push spend early. Follow with a forecast at completion so the committee sees where the project will land, not only where it is.

Should risks and issues sit in one table for a steering committee?

One table works if a type column separates them. A risk might happen; an issue already has. A partner billing over budget is an issue, while possible data quality problems are a risk. Listing issues first helps the committee act on them now and then decide which risks to fund.

How do I show the critical path without dependency arrows?

Label each critical path task in the Gantt, for example with a group under the task name, and say in the description which slip moves the end date. Committees rarely need the full network; they need to know which few tasks set the go live date.

How do I get a steering committee to make decisions?

Ask for each decision explicitly, with its cost, its owner and what happens if it is not made. Send the deck a few days ahead so members arrive with views. End the meeting by reading the decisions back for the minutes, so agreement is recorded rather than assumed.

Can I export the Gantt slide into a PowerPoint for the board pack?

Yes. In an editable PPTX export, the Gantt artwork stays a picture but its labels become native text boxes, so task names and dates can still be edited in PowerPoint. Tables become native PowerPoint tables. PowerPoint exports are paid features; a PDF export costs about 1 credit per 10 slides.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other presentation examples

Want the steps in the builder? Read Add charts, maps and diagrams to slides, then Export a presentation to PowerPoint or PDF. For everything this generator can do, see the presentation maker.

Sources

Written and checked by the OneCraft team. Last checked .