Freelancers often use "scope creep" as a catch-all for any project expansion, but there's an important distinction between scope creep and feature creep.
Scope creep
Scope creep is the expansion of project requirements beyond what was originally agreed upon. It's client-driven: the client requests additional work, revisions, or deliverables that weren't in the original agreement.
Example: You agreed to design a logo, and the client asks you to also design business cards and a letterhead.
Feature creep
Feature creep is when the complexity or sophistication of individual deliverables increases beyond what was planned. It can be client-driven or self-driven.
Example: You agreed to build a contact form, and the client (or you) decides it should also include file uploads, conditional logic, and a CRM integration.
Why the distinction matters
Scope creep is best handled with change orders — new deliverables at new prices. Feature creep is best handled with specific deliverable definitions upfront. Both are prevented by a detailed scope of work that defines not just what you'll deliver but the complexity of each item.
Tools like ScopePilot help with both: each deliverable has a description field where you can define its boundaries, and revision tracking catches the iterations that signal feature creep.