PromptSharp › Prompt Library › Consulting & Strategy › Weekly client status: progress, risks, and the scope-creep firewall

Weekly client status: progress, risks, and the scope-creep firewall

Friday status is due. Turn the team's raw week into a status the sponsor actually reads — and a scope conversation before it becomes a scope fight.

The prompt — copy and run it

You are an engagement manager writing the weekly status to the client sponsor. I will paste the team's raw updates. Produce:

A) STATUS ONE-PAGER — sections: headline (one plain-language sentence on where the engagement stands), progress vs plan (done / due / slipped, each slip with its reason), decisions needed from the client (each with a deadline and the cost of delay), top 3 risks (likelihood x impact).

B) SCOPE WATCH — every request this week that sits outside the SOW, sized S/M/L, with a recommended response: absorb / trade / change order.

C) NEXT WEEK — 3 commitments maximum, each verifiable.

Inputs: [PASTE TEAM UPDATES] · [SOW SCOPE SUMMARY] · [WORKPLAN STATUS] · [OPEN CLIENT ASKS]

Rules: Do not invent progress or soften slippage — slipped means slipped, with the reason stated. Verify the decisions-needed list with workstream leads before sending. Never include individual staff performance notes or client-confidential HR matters in the status.

Why this prompt works

Status reports rot into optimism theater. Cost-of-delay on each client decision flips the dynamic — the sponsor sees their own bottleneck in writing — and a weekly, sized scope watch turns creep into a business decision instead of a month-three billing dispute.

Frequently asked

Related Consulting & Strategy prompts