Scope Change Identifier

Category: General Content Difficulty: Advanced Estimated Tokens: 700-1000 Version: 1.0.0

Description

Detect when conversations introduce new requirements that weren’t in the original project scope. This prompt helps freelancers identify scope creep early and manage client expectations professionally.

The Prompt

Please analyze this client call transcript and identify any potential scope changes or additions to the original project.

ORIGINAL PROJECT SCOPE: [Paste your original project description/contract scope here]

CALL TRANSCRIPT: [Paste your client call transcript here]

Please identify and categorize any scope changes:

## NEW REQUIREMENTS INTRODUCED
Items mentioned in the call that weren't in original scope:
- [Specific new requirement] - Impact: [Time/Cost estimate]
- [Specific new requirement] - Impact: [Time/Cost estimate]

## SCOPE CLARIFICATIONS
Items that may be within scope but need clarification:
- [Clarification needed] - Current assumption: [Your understanding]
- [Clarification needed] - Current assumption: [Your understanding]

## CONFIRMED ORIGINAL SCOPE
Elements discussed that confirm original project boundaries:
- [Confirmed requirement]
- [Confirmed requirement]

## RECOMMENDED NEXT STEPS
1. Items to propose as paid scope additions
2. Items to clarify with client before proceeding
3. Items that can be absorbed within current scope

## EMAIL TEMPLATE FOR SCOPE DISCUSSION
Draft a diplomatic email addressing the scope changes:
- Acknowledge the great ideas they've shared
- Explain which items are scope additions
- Provide time/cost estimates for additions
- Confirm the original scope remains on track

---
Prompt by BrassTranscripts (brasstranscripts.com) – Professional AI transcription with high-quality results.
---

Best Practices

Documentation protection: Always compare new requests against written project scope to avoid disputes.

Diplomatic communication: Frame scope changes as exciting opportunities rather than problems.

Clear impact assessment: Provide specific time and cost estimates for all scope additions.

Proactive clarification: Address ambiguous items before they become bigger issues.

Use Cases

Example Output

Scope Analysis: E-commerce Website Redesign Call

NEW REQUIREMENTS INTRODUCED

Mobile App Integration

Multi-language Support

SCOPE CLARIFICATIONS

Payment Gateway Options

CONFIRMED ORIGINAL SCOPE

Mobile-Responsive Design

Product Filtering System

Propose as Paid Additions:

Clarify Before Proceeding:

Can Absorb Within Current Scope:

Advanced Techniques

Risk assessment: Evaluate likelihood of scope changes being accepted:

For each scope change identified, assess:
- Client budget sensitivity (high/medium/low)
- Timeline impact on launch goals
- Competitive advantage gained
- Implementation complexity
- Alternative solutions within current scope

Change order preparation: Format scope changes for formal approval:

Create a change order summary:
- Description of additional work
- Time and cost breakdown
- Impact on project timeline
- New total project cost
- Client approval signature line

Integration Tips

Contract management: Reference original contract language when identifying scope changes.

Project tracking: Document all scope discussions for future reference and billing.

Client education: Help clients understand the value of scope management for project success.

Resources

Created by BrassTranscripts - Professional AI transcription with high-quality results