Is It Out of Scope? — Web development
Is adding social media templates out of scope for a web development project?
Yes. Social media templates are static design assets, not something a development engagement produces — outside the scope regardless of whether the request is routed to the dev team for convenience.
On engagements where there's no separate active design resource, requests for design assets that have nothing to do with the build — like social media post templates — sometimes land with the development team simply because they're the point of contact, not because it's development work.
Is it out of scope?
Yes. Social media templates are static graphic design assets, unrelated to building or maintaining a website. This is outside a development engagement's scope regardless of who the request is addressed to.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — The engagement covers development work — static design assets like social templates are excluded as a different discipline.
Example contract wording
Example contract wording (illustrative, not legal advice)
Social media templates are a design asset outside our development scope — that's not something we produce under this engagement. Happy to point you toward a designer, and if there's ever a technical piece involved (like a template system in a tool you're using), that part could fall under development.
How MarginFlow flags it
MarginFlow flags static design asset requests like this outside_scope on development contracts by default, since they never appear in a dev SOW's deliverables under any framing — the explanation notes the discipline mismatch plainly so it's an easy redirect for the account manager.