Is It Out of Scope? — Web design
Is fixing bugs found after sign-off out of scope for a web design project?
It depends on what the "bug" actually is. A genuine defect in what was delivered — something that doesn't match the approved design or doesn't work as built — is typically covered by warranty. A new issue introduced by later changes, or a request framed as a bug that's really a new feature, is not.
The client approved the design and it launched. Weeks later they report something "broken" — a hover state that doesn't match the mockup, a section that misbehaves on a specific browser, a spacing issue that wasn't there in the approved comps. Whether that's covered work or a new billable request turns entirely on what actually changed: a real defect in the delivered build is different from something that only looks like a defect.
Is it out of scope?
It depends. If the issue is a genuine discrepancy between what was approved and what was delivered — the build doesn't match the signed-off design — that's typically covered under warranty and should be fixed at no charge within the warranty period. If it's a new issue that emerged after sign-off (a browser update, the client's own edits, a third-party plugin conflict) or is really a new preference dressed up as a bug report, that's a separate, billable request.
Clause typically implicated
Clause typically implicated
Warranty clause→ — Sets the window and conditions under which defects in the delivered work are fixed at no charge — the line between a covered defect and a new request usually runs through this clause.
Example contract wording
Example contract wording (illustrative, not legal advice)
Happy to take a look. If this turns out to be a mismatch between the approved design and what was delivered, it's covered under our [X]-day warranty at no charge. If it's something that changed after launch — a browser update, a plugin, an edit on your end — I'll flag what I find and quote the fix separately.
How MarginFlow flags it
This is a case where MarginFlow's confidence score matters as much as the classification itself — the model weighs the request against the warranty terms and revision history in the thread, and when it genuinely can't tell whether something is a covered defect or a new issue, it says so with a lower confidence score and an explanation that names the ambiguity, rather than forcing a confident yes/no it can't actually back up.