PromptSharp › Prompt Library › Consulting & Strategy › Scope guard: a risk register that catches creep before it eats the margin
Scope guard: a risk register that catches creep before it eats the margin
The engagement is drifting and the budget is tightening. Build a risk register and a scope guard that surfaces creep early.
The prompt — copy and run it
You are an engagement manager building a risk register and scope-control read. Produce: A) RISK REGISTER — the top risks to this engagement from what I described, each with likelihood, impact, an owner, and a specific mitigation — sorted by likelihood × impact. B) SCOPE DRIFT — the 2-3 places where delivered work is expanding past the SOW, and the exact conversation to have with the client about each. C) BURN CHECK — planned vs actual effort at this point, the projected overrun if the trend holds, and the lever with the most margin impact. D) STATUS LINE — a three-sentence honest status I could send the client today (green/yellow/red, why, next step). Inputs: [ENGAGEMENT SCOPE / SOW] · [WHAT'S ACTUALLY HAPPENING] · [BUDGET + BURN] · [TIMELINE + MILESTONES] Rules: Do not invent budget figures or downplay risk — rate honestly from what I gave you and mark unknowns. Keep confidential client and financial data out of consumer AI tools. This flags the risks; the client conversation and the call stay yours. Verify anything uncertain against the source before relying on it.
Why this prompt works
Engagements lose money to scope creep that nobody names until it's too late; a likelihood×impact-sorted register plus an explicit scope-drift scan and burn projection turns quiet drift into a specific client conversation with a mitigation attached — and the honest-status rule prevents the yellow-that-should-be-red reflex.
Want the daily version?
The PromptSharp Consulting Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
The engagement is drifting and the budget is tightening. Build a risk register and a scope guard that surfaces creep early.
Why does this prompt work?
Engagements lose money to scope creep that nobody names until it's too late; a likelihood×impact-sorted register plus an explicit scope-drift scan and burn projection turns quiet drift into a specific client conversation with a mitigation attached — and the honest-status rule prevents the yellow-that-should-be-red reflex.
What mistake does this prompt help you avoid?
{'code': 'PF02', 'note': "Unnamed scope creep — a sorted risk register plus scope-drift and burn checks surface margin erosion while it's still fixable."}
Related Consulting & Strategy prompts
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 becom…
Issue tree builder: from vague client ask to testable hypotheses
New engagement, vague problem statement. Build the issue tree and the week-one analysis plan before the team burns days boiling th…
All Consulting & Strategy free prompts
The PromptSharp Consulting Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting