Website Development Contract Checklist: Acceptance, Copyright, and Final Payment

Most website building disputes aren't about poor quality—they're about unclear contracts. The three areas most likely to cause issues are acceptance criteria, c…

Insights:Website Development Contract Checklist: Acceptance, Copyright, and Final Payment

Article 1: Scope Should Be Written as a Checklist

  • Number of pages and page types (homepage, category page, detail page, functional page).
  • Whether mobile responsiveness is included.
  • Whether an admin panel is included (who can edit what).
  • Whether basic SEO items are included (titles, descriptions, sitemap, structured data).
  • Whether content entry is included (up to how many articles/posts).

Warning: Contracts that only say "one corporate website" will likely treat each subsequent item as an "additional requirement."

Article 2: Change Mechanism

  • How change requests are priced (per person-day or per item).
  • Number of revision rounds: how many design revisions are included and how overages are charged.
  • Changes must be confirmed in writing to avoid relying on verbal promises.

Article 3: Acceptance Criteria Must Be Actionable

Saying "meets design requirements" is not enough; write it as verifiable items:

Acceptance Item Standard
Page completeness All pages in the checklist are accessible and return HTTP 200
Mobile No horizontal scrolling on mainstream devices; buttons are clickable
Admin panel Can publish content, edit categories, replace images
Performance Homepage first-screen load within the agreed time
Compatibility Consistent display across mainstream browsers
SEO basics Titles, descriptions, sitemap, and robots.txt all present

Acceptance must be confirmed in writing and serve as the basis for payment.

Article 4: Source Code and Copyright

  • Whether all source code is delivered (including templates, scripts, configuration files).
  • Who owns the database structure and data.
  • Whether fonts, images, and plugins have valid licensing.
  • Whether you are allowed to modify and customize it yourself.
  • Whether it is locked into the vendor's proprietary platform (non-migratable = vendor-locked).

Key takeaway: It only counts as real delivery if it can run independently on your own server.

Clause 5: Launch Support

  • Who handles the domain, ICP filing, and certificates—and under whose name they are registered.
  • Who provides the server and who bears the cost.
  • Division of labor for the launch timeline and content preparation.
  • A bug-fixing period of 1–3 months after launch.

Clause 6: Final Payment & After-Sales

  • Payment milestones: contract signing, design approval, and launch acceptance.
  • The balance ratio and its trigger conditions must be clearly stated.
  • After-sales response SLA (e.g., within 4 business hours).
  • Scope of free maintenance and the unit rate for work beyond it.

Pitfalls to Avoid

  • Paying the final installment upon "launch" when the acceptance criteria are vague, leading to endless disputes.
  • Source code "delivered" but dependent on the vendor's proprietary components, making it impossible to run independently.
  • After-sales limited to a generic customer-service line with no designated responsible person.
  • No change-order pricing in the contract, so every subsequent modification triggers a new quote.

Bonudaries

A contract can reduce the likelihood of disputes, but it cannot guarantee delivery quality. Choosing the right vendor comes first; a contract merely acts as a safeguard for the partnership, not a substitute for due diligence.

Related reading: