Is It Out of Scope? — Web design
Is adding a second environment (staging/QA) out of scope for a web design project?
Yes. Environment setup is infrastructure work, not a design deliverable.
This usually comes from a client's internal IT or ops contact rather than the design stakeholder — a request to "also stand up a staging copy" once they realize changes are landing straight on production.
Is it out of scope?
Yes. Provisioning a second environment is server and deployment infrastructure work, not layout, visual, or brand design — it doesn't fit a design deliverable list at all.
Clause typically implicated
Clause typically implicated
Exclusions clause→ — Environment and infrastructure setup is technical work excluded from a design engagement's scope.
Example contract wording
Example contract wording (illustrative, not legal advice)
Setting up a staging environment is infrastructure work outside design scope — that's something your developer or hosting provider would handle.
How MarginFlow flags it
MarginFlow flags staging/QA environment requests outside_scope on design contracts, since they're infrastructure asks with no design-deliverable overlap.