Reporting to the Steering Committee: The Project Is Behind Schedule

Good morning. Thanks for making time for this.

Morning. Let's get straight to it, shall we?

Of course. Overall, we've made solid progress this month.

Good. So, are we still on track for go-live?

Well... that's the difficult part.

I'm afraid our status has moved from green to amber.

Amber? Last month you said everything was fine!

The supplier delivered the migration tool three weeks late.

And unfortunately, that task sits on the critical path.

So how much slippage are we talking about?

Um, around four weeks, if we do nothing.

Four weeks? Ugh, the board won't accept that.

Why wasn't this escalated earlier?

That's fair. I should have flagged it sooner.

We honestly believed the supplier could catch up.

Hmm. And where are we on the budget?

Don't worry, the budget variance is under two percent.

Okay, I've prepared two options for a mitigation plan.

First, we bring in two extra developers,

paid for from the contingency budget.

And the second option?

We go live on time with a reduced scope,

and deliver the reporting module a month later.

Right. Which one would you recommend?

The first one. It protects both the scope and the date.

But it uses most of our contingency, doesn't it?

It does, but the risk of further delays is low.

The dependency on the supplier has now been resolved.

Fine. I'll approve the extra resources, on one condition.

I want a weekly report until we're back to green.

Absolutely. You'll have it every Friday morning.

And next time, escalate early. No surprises.

Understood. Thank you — that's a real relief!

Good. Let's get the change request signed off today.