Which resource should I use next?

Use the linked primary resource for the actual artifact or decision framework. This article addresses the narrower task: audit a web feature request.

Web Design Scope Creep: Trace the Extra Feature Before You Quote

Illustrative case — not a customer result

Illustrative case: a brochure-site client asks for member login after approving static pages. Login introduces account states, error handling, data storage, and access testing. An extra page estimate would miss the actual dependency chain. First compare the feature with the approved functional requirements; if login was included, it is not new scope.

Apply the decision

List account states and data dependencies
Identify integration, accessibility, and testing work
Offer a separate phase if launch should remain unchanged

Boundary and limitations

Do not estimate only the visible screen or describe an already promised feature as an addition.

Message for this situation

Free editable sample

No purchase or email required.

Member login adds account states, access rules, and testing beyond the approved static pages. I can scope that separately or schedule it after the initial launch.

Decision record to complete

Free editable sample

No purchase or email required.

Feature: [complete for this project]
requirements reference: [complete for this project]
affected screens: [complete for this project]
data dependency: [complete for this project]
test plan: [complete for this project]
fee: [complete for this project]
launch impact: [complete for this project]

Frequently asked questions

Which resource should I use next?: Use the linked primary resource for the actual artifact or decision framework. This article addresses the narrower task: audit a web feature request.
What should I avoid assuming?: Do not estimate only the visible screen or describe an already promised feature as an addition.

Continue with the next decision

Role-specific solution

Feature Requests Outside Scope for Web Developers

Web developers should describe the added feature’s build, integration, testing, and schedule impact rather than treating it as a quick code change.

Next step

Stop Scope Creep

Diagnose the request before you change the project.

Free editable artifact

Freelance Change Order Form Template

A freelance change-order form records the original agreement, requested difference, added and removed work, price adjustment, revised milestones, dependencies, and authorized approval. Give each change an identifier so the client can approve a specific version.