Is It Out of Scope? — Web development
Is adding schema markup beyond the original quote out of scope for a web development project?
Yes, if it goes beyond the schema types listed in the quote. Implementation is dev work, but the original quote defines which types were included as deliverables.
Schema implementation is genuinely dev work, so this one's less about discipline mismatch and more about volume — the original quote typically named specific schema types (Organization, Product, FAQ), and "add more" means types that weren't on that list.
Is it out of scope?
Yes, when it's schema types beyond what the quote listed. Each type needs its own structure, testing, and validation — it's not a single toggle that covers everything at once.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote listed specific schema types as deliverables — additional types are a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
The quote covered schema markup for [types listed] — [new type(s)] weren't part of that list, and each one needs its own structure and validation. I can add it as a small scope addition.
How MarginFlow flags it
MarginFlow checks the schema types named in a request against the deliverables listed in the contract and flags a mismatch as outside_scope, since additional types represent genuine additional implementation work.