Is It Out of Scope? — Web development
Is migrating SEO tracking after a site redesign out of scope for a web development project?
Depends. If this team's own redesign broke tracking that was previously working, that's a defect to fix under warranty. If it's a full re-implementation of tracking that was never live before, that's new scope.
This is one of the more genuinely ambiguous requests in the redesign cluster: if the dev team's own rebuild is what broke tracking that used to work, fixing it looks a lot like a defect. If the client is asking for tracking to be migrated or newly configured as part of the redesign, that's a fresh deliverable.
Is it out of scope?
Depends. Restoring tracking that broke because of this engagement's own changes is a warranty fix. Building out new or migrated tracking that wasn't part of the original build is new scope.
Clause typically implicated
Clause typically implicated
Warranty clause→ — Covers fixing tracking broken by this engagement's own redesign, distinct from new tracking setup — see also exclusions-clause for tracking work outside the original build.
Example contract wording
Example contract wording (illustrative, not legal advice)
If the redesign is what knocked out tracking that was live before, we'll get that restored under warranty at no extra cost. If you're looking for a broader tracking migration or new setup beyond what was there before, that's additional scope I can quote separately.
How MarginFlow flags it
MarginFlow checks whether the request describes something that was previously working (routes it toward defect/warranty language) versus something newly requested (routes it toward outside_scope), flagging the ambiguity for manual review when the request doesn't make the distinction clear.