Is It Out of Scope? — Web development
Is creating a content calendar for a new channel out of scope for a web development project?
Yes. Content strategy and scheduling have no technical component and no overlap with development work.
This request rarely lands on a dev team naturally, but can surface if the build included some content-publishing tooling and the client assumes planning what goes into it is part of the same engagement.
Is it out of scope?
Yes. Deciding what content goes where and when is strategy work, unrelated to whatever publishing tooling was built.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — The engagement covers development work — content strategy and calendar planning are excluded as a separate discipline.
Example contract wording
Example contract wording (illustrative, not legal advice)
Planning a content calendar isn't development work — that's outside this engagement. What we built is the tooling to publish into; deciding what and when is a content strategy question for someone else on your team or a specialist.
How MarginFlow flags it
MarginFlow flags content-calendar and strategy requests outside_scope on development contracts, keeping the classification consistent with how it treats other content/marketing-discipline requests on dev engagements.