Spot creeping scope hidden in routine feedback

Catch micro-requests, revisions, and feature creep disguised as normal comments. Use this before actioning revision rounds to protect billable hours.

You getIncluded Revisions, scope Creep Detected and suggested Boundary Script

Prompt

Prompt
Act as a contract project manager and QA lead. Review the client feedback or revision notes provided below and separate contractual revisions from scope creep.

Rules:
- Distinguish between fixing agreed deliverables (in scope) and functional expansion or new design directions (out of scope).
- Point out disguised phrases like 'while you are in there' or 'simple tweak'.
- Provide a specific justification for why each flagged item constitutes new scope.

Output format:
1. Included Revisions (table: Item, Original Spec Reference, Action Required)
2. Scope Creep Detected (table: Client Request, Why It Is Out of Scope, Recommended Billing Action)
3. Suggested Boundary Script (short phrase to reply to the client)

My project specification notes and the client feedback are below:

Example output

Example for: feedback on a fixed-bid B2B contact form and thank-you page

1. Included Revisions
ItemOriginal Spec ReferenceAction Required
Fix mobile layout clipping on submit buttonSection 2.1: Responsive UI complianceAdjust CSS padding and line-height on viewports below 480px.
Correct typo in headline paragraphSection 1.4: Approved copy deckUpdate copy string to match approved final draft.
2. Scope Creep Detected
Client RequestWhy It Is Out of ScopeRecommended Billing Action
'Can we also route leads to two different sales reps based on company size?'The agreement specifies a single standard notification email; conditional logic requires new backend script and validation rules.Quote as a standalone feature add-on (approx. 4 hours).
'Let us embed an interactive calendar picker instead of the plain date field.'Specification agreed on native HTML date input; custom calendar component requires external library integration and QA.Inform client that calendar replacement requires a separate mini-estimate.
3. Suggested Boundary Script

'We have completed the responsive styling fixes and headline correction. The lead routing rules and interactive calendar widget are outside our current build spec, so I have scoped those separately below if you would like to proceed with those additions.'

Written by AI from this prompt. Your results will vary.

Paste your contract deliverable list followed by the client's revision comments into Claude, ChatGPT, or Gemini. If you bill hourly, follow up by asking the model to estimate total developer hours for the out-of-scope items.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Project Management
Project Management

Diplomatic pushback against scope creep

Draft a polite, professional response that acknowledges an out-of-scope request, explains project tradeoffs, and offers clear paths forward.

Project Management

Audit a RACI chart for split accountability

Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.