Scope baseline
Approved sitemap, page/template count, component list, content owner, integrations, migration inventory, exclusions, and platform accounts.
Scope-first planning tool
Web Design Contract Template & Scope Planner
Turn project facts into a reviewable planning draft covering deliverables, dependencies, revisions, acceptance, hosting, access, copyright, handoff, and payment evidence.
Build the project record
Use operational facts, not passwords, API keys, customer records, tax IDs, or confidential production data. The output is a planning draft for discussion and legal review, not a promise that any clause is enforceable.
Describe outputs that can be inspected. Avoid broad phrases such as "complete website" without a page, template, or feature list.
Do not treat labels as outcomes. Calling someone an independent contractor, naming a work "made for hire," or selecting an accessibility target does not by itself establish legal status, copyright ownership, or compliance.
Contract Preview
Fill in the form above to generate your contract...
Use the planner in four passes
- Inventory inspectable deliverables, exclusions, platforms, integrations, client assets, and account ownership.
- Define review rounds, feedback windows, change approval, acceptance tests, milestone evidence, and launch authority.
- Separate custom work from pre-existing tools and third-party materials; record licenses, renewals, source files, and transfer limits.
- Generate the planning draft, verify every placeholder with the other party, then obtain legal, privacy, security, accessibility, and tax review where applicable.
Evidence to collect before signature
Review baseline
Named approver, feedback format, included rounds, review windows, change estimate approval, acceptance tests, and issue-severity rules.
Handoff baseline
Repository, source files, licenses, domain and hosting control, deployment record, backups, access revocation, documentation, and support boundary.
Do not leave these as vague boilerplate
| Topic | Weak wording | Evidence-based replacement |
|---|---|---|
| Scope | "Build a complete website" | Pages, templates, reusable components, content, data migration, integrations, devices, tests, exclusions, and account owner. |
| Revision | "Reasonable revisions" | Number of rounds, consolidated approver feedback, response window, what counts as a correction versus new scope, and written pricing approval. |
| Acceptance | "Approved when delivered" | Staging URL, test checklist, review period, severity definitions, rejection notice, correction cycle, and written acceptance record. |
| Ownership | "All rights automatically transfer" | Identify custom deliverables, pre-existing tools, open-source and licensed assets, transfer or license timing, source files, portfolio use, and lawyer review. |
| Launch | "Designer guarantees uptime and compliance" | Name hosting owner, launch approver, backup and rollback steps, third-party dependencies, accessibility target, security test scope, and continuing maintenance owner. |
Web design contract review boundaries
This planner produces an operational record, not legal advice or a signed-ready agreement. Contract language depends on the parties, location, worker relationship, privacy and security obligations, accessibility requirements, project risk, insurance, dispute choices, and the licenses attached to software, themes, fonts, media, plugins, and open-source components.
Copyright treatment deserves specific review. The U.S. Copyright Office explains that specially commissioned work does not become a work made for hire merely because a contract uses that label; statutory categories and a signed written agreement matter. A project may instead use a written assignment or license, but the parties should have counsel confirm the intended ownership and the treatment of pre-existing and third-party materials.
Security access should also be written and testable. The FTC advises businesses to specify vendor security expectations, limit access to need-to-know purposes and time periods, verify compliance, and address data handling and deletion. For a website project, translate those principles into named accounts, MFA, least privilege, staging and production separation, backup/rollback responsibilities, incident contacts, and prompt access revocation.
Accessibility should be planned as a scoped production activity rather than a blanket guarantee. W3C WAI recommends defining goals, scope, responsibilities, standards, review work, and ongoing monitoring. Record what will be designed, implemented, tested, documented, and maintained, then obtain qualified advice on legal requirements for the relevant organization and jurisdiction.
U.S. Copyright Office - Works Made for Hire (Circular 30)Review statutory requirements before using work-made-for-hire or ownership language.
Federal Trade Commission - Cybersecurity for Small BusinessReview vendor security, access control, data handling, monitoring, and breach-response guidance.
W3C Web Accessibility Initiative - PlanUse an explicit accessibility objective, scope, responsibility, review, and monitoring plan.
Source review: July 19, 2026. Re-check current law, standards, product terms, and project facts before use.
Web design contract planning questions
Who should own the domain and hosting accounts?
Record the actual account owner, billing owner, access level, launch approver, backup process, and handoff procedure. Client-owned accounts often simplify continuity, but the right structure depends on the engagement.
What is the difference between a revision and a change request?
Define a revision as feedback within the approved scope and acceptance criteria. Treat a new page, feature, integration, platform change, or changed requirement as a proposed scope change that needs written pricing and schedule approval.
Does paying for a website automatically transfer copyright?
Do not assume payment or a work-made-for-hire label automatically determines ownership. Identify custom deliverables, pre-existing tools, open-source code, licensed assets, transfer or license timing, and source-file rights for qualified legal review.
How should accessibility be addressed?
Document a specific target, included pages and components, test methods, review responsibilities, remediation process, exclusions, and ongoing maintenance owner. Avoid an unsupported blanket promise of legal compliance.
What security details belong in the project record?
Record named accounts, least-privilege access, MFA, an approved credential channel, staging and production separation, backup and rollback ownership, incident contacts, access revocation, and data return or deletion.