Is It Out of Scope? — Web development
Is fixing issues caused by the client's own edits out of scope for a web development project?
Yes. Breakage from a client editing code or config directly isn't a defect covered by warranty.
This shows up when a client with some technical access — a plugin they installed, a config value they changed, a snippet they pasted in — breaks something, and it lands as a bug report rather than what it actually is.
Is it out of scope?
Yes. A bug traced to the client's own post-delivery code or config change isn't a defect in the delivered build — the warranty covers issues in what was actually shipped, not changes made after handoff.
Clause typically implicated
Clause typically implicated
Client responsibilities clause→ — Places responsibility for the outcome of the client's own post-delivery changes to code or configuration on the client.
Example contract wording
Example contract wording (illustrative, not legal advice)
Checking the history, this traces back to a config change made after delivery, not the original build — that falls outside warranty, but I can fix it as billed work.
How MarginFlow flags it
MarginFlow flags fix requests outside_scope on development contracts when deploy or edit history shows the client's own change caused the issue, keeping it separate from genuine warranty defects.