Is It Out of Scope? — Web development
Is supporting an additional browser or device beyond the agreed matrix out of scope for a web development project?
Yes, past the agreed matrix. Extra compatibility testing and fixes for a new target take real QA time.
The build was tested and priced against a defined matrix — the major current browsers and common device sizes. A request to also fully support something outside that, like an older browser version, is a real additional QA and fix commitment.
Is it out of scope?
Yes. Testing against and fixing issues for a browser or device outside the agreed matrix is additional QA and engineering time beyond what the build's price covered.
Clause typically implicated
Clause typically implicated
Out-of-scope clause→ — Native compatibility work, but testing and fixing for a target outside the agreed matrix exceeds the QA scope the build was priced against.
Example contract wording
Example contract wording (illustrative, not legal advice)
The build was tested against the agreed matrix — supporting [the new target] fully would mean additional QA and fixes, which I'd scope and quote separately.
How MarginFlow flags it
MarginFlow flags requests to support a browser or device outside the agreed matrix outside_scope on development contracts.