Is It Out of Scope? — Web development
Is load testing before a major launch out of scope for a web development project?
Usually yes, unless it was specifically quoted. Simulating real traffic load and tuning for it is a distinct pre-launch deliverable.
Most builds are functionally tested — pages load, forms submit — but not load-tested against a spike in concurrent traffic. Ahead of a launch expected to drive a surge, a client reasonably wants that verified, but it's a distinct exercise from functional QA.
Is it out of scope?
Yes, unless it was quoted. Setting up load-testing tooling, simulating a realistic traffic spike, and tuning based on the results is separate work from the functional testing a standard build includes.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers functional QA of the build; load testing and performance tuning under simulated traffic is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build includes functional QA, not load testing under simulated traffic — that's a separate pre-launch exercise I'd scope and quote on its own, especially given the timeline.
How MarginFlow flags it
MarginFlow flags load-testing requests outside_scope on development contracts unless the SOW explicitly listed pre-launch load testing as a deliverable.