Is It Out of Scope? — Web development
Is reporting on a new analytics platform out of scope for a web development project?
Yes. Implementing tracking is a technical task; interpreting and reporting on the resulting data is not.
Dev teams often do own the implementation side — wiring up a tag manager, verifying events fire correctly. The line gets blurry when "can you check the tracking works" turns into "can you tell us what it means."
Is it out of scope?
Yes. Implementation is technical work; reading the resulting data and producing insight from it is an analysis discipline outside a development scope.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Development scope typically covers implementing tracking, not analyzing or reporting on the data it collects.
Example contract wording
Example contract wording (illustrative, not legal advice)
We handled getting [new platform] wired up and firing correctly — building out ongoing reports and interpreting the numbers is a different kind of work than implementation, and isn't part of this engagement.
How MarginFlow flags it
MarginFlow distinguishes implementation language ("set up," "install," "verify") from analysis language ("report on," "interpret," "insights") in incoming requests, flagging the latter outside_scope on development contracts.