Is It Out of Scope? — Web development
Is creating a custom 404 page beyond the template out of scope for a web development project?
Yes, past implementing the standard template. Custom logic (dynamic suggestions, search, tracking) is separate build work.
Implementing a static 404 page is a small, expected part of most builds. It becomes a real build item when the client wants it to do something — surface a search box, suggest related pages dynamically, or log the broken URL for review.
Is it out of scope?
Yes, past implementing a static styled template. Dynamic behavior — content suggestions, search, structured broken-link logging — is logic that wasn't part of a standard error-page build.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The quote covers implementing a static template error page; dynamic 404 logic is a new, unquoted deliverable.
Example contract wording
Example contract wording (illustrative, not legal advice)
Implementing the standard 404 template is included, but adding dynamic suggestions or search on that page is separate logic — I'd scope and quote that as its own item.
How MarginFlow flags it
MarginFlow flags dynamic-404-logic requests outside_scope on development contracts, distinguishing them from implementing a static template page.