Is It Out of Scope? — Web development
Is building a custom form beyond the template library out of scope for a web development project?
Yes. Building and wiring up a fully custom form — validation, submission handling, integrations — is more effort than configuring an existing template.
Configuring a form from an existing template is quick — fields, validation rules, and submission handling are already built. A genuinely custom form means building all of that from scratch.
Is it out of scope?
Yes. Custom validation logic, submission handling, and any new integrations it needs represent real build effort beyond configuring what already exists in the template library.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The template library and its configuration were the scoped deliverable; a form outside that library is new build work.
Example contract wording
Example contract wording (illustrative, not legal advice)
This needs custom validation and handling that none of the existing templates cover — it's a real build rather than a configuration of what's already there. I'll put together a quote for it.
How MarginFlow flags it
MarginFlow checks form requests against the template library named in the contract's deliverables and flags a fully custom build as outside_scope, distinguishing it from configuration-level requests.