Is It Out of Scope? — Web design
Is creating a style guide after project completion out of scope for a web design project?
Usually yes. Documenting a style guide after the fact is real authoring work, not a leftover task from the original design deliverables.
This comes up once a project is live and the client's internal team wants a reference document — colors, type, spacing rules — but a formal style guide was never part of what was quoted.
Is it out of scope?
Usually yes, unless a style guide was explicitly named as a deliverable. Reverse-engineering and documenting the system used in a finished design is its own writing and formatting effort.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — A style guide is a documentation deliverable in its own right; if it wasn't listed among the original deliverables, producing one after the fact is new work.
Example contract wording
Example contract wording (illustrative, not legal advice)
A style guide wasn't part of what we scoped for this project — I can put one together documenting the colors, type, and spacing we used, quoted as a separate deliverable.
How MarginFlow flags it
MarginFlow checks whether a style guide was named in the contract's deliverables and flags after-the-fact requests as outside_scope when it wasn't.