Boundary Setting

Pushing Back on Scope Creep Email Template

Address expanding project requirements that go beyond the agreed scope.

When to use this template

The project requirements keep expanding beyond the original scope and I need to push back.

Example subject line

Project Atlas — New Feature Requests Beyond Original Scope, Change Request Needed

Tips for writing this email

  • Reference the original project brief, statement of work, or agreed-upon requirements document by name and date.
  • List the specific new requests that fall outside the original scope so the additions are clearly visible.
  • Propose a formal change request process — additional scope should come with an adjusted timeline or budget.
  • Frame the pushback around protecting project quality rather than refusing to do more work.

What to avoid

  • Do not silently absorb extra work and then miss the original deadline — raise the issue early.
  • Avoid saying "that is not in the scope" without explaining what the impact of adding it would be.
  • Do not send the email to the whole team — address scope concerns directly with the project owner or stakeholder.
  • Avoid being adversarial — position yourself as a partner who wants the project to succeed within realistic constraints.

Ready to write your boundary setting email?

Use our AI generator to create a personalized version of this template tailored to your specific situation.

Generate This Email

Frequently Asked Questions

How do I push back on scope creep without sounding difficult?

Frame it as protecting project quality and timeline. Say something like "To deliver X by the deadline, we need to formally assess the impact of adding Y" rather than simply refusing.

What is the difference between scope creep and a legitimate change request?

Scope creep happens when new requirements are added informally without adjusting the budget or timeline. A legitimate change request goes through a formal process with documented impact on cost, resources, and delivery date.

Should I track scope changes in writing?

Absolutely. Document every addition to the original scope with the date it was requested, who requested it, and the estimated impact. This paper trail protects you if deadlines are missed due to unplanned additions.

Other Boundary Setting Templates