Guide · Planning a website
Website development contract checklist
Most disputes between businesses and developers are not about bad intentions but about things nobody wrote down: what exactly was included, what "done" means, who owns the domain, what happens with changes. A clear contract protects both sides. This checklist covers the technical and practical points to settle; the legal wording should be prepared or reviewed by your lawyer.
[ 01 ]
In short
In short
- 01
Attach a detailed scope: pages, functions, integrations, languages, deliverables.
- 02
Define acceptance: how the result is checked and when it counts as accepted.
- 03
Describe how changes are requested, estimated and approved.
- 04
Settle ownership of code, designs, content, domain, hosting and all accounts.
- 05
Include confidentiality, personal data processing and security obligations.
- 06
Separate development from support, with its own terms.
[ 02 ]
Guide
Scope
- A scope document or specification as an annex, listing pages and templates, functions, integrations, languages, content responsibilities and non-functional requirements (speed, accessibility, browsers and devices).
- What is explicitly excluded.
- Which third-party services are used, and who pays for them.
Stages and timeline
- Stages with deliverables and approval points.
- The client's obligations and deadlines — content, feedback, access — and how delays on either side affect the timeline.
Acceptance
- How each stage and the final result are checked: acceptance testing against the scope, on agreed devices and browsers.
- Time allowed for acceptance and for fixing defects.
- What counts as a defect versus a change request.
Changes
- How changes are requested and estimated.
- That no additional work is billed without written approval.
- How changes affect the timeline.
Payments
- Amounts and schedule, tied to stages or deliverables.
- What happens to payments if the project is paused or terminated.
Ownership and access
Clarify, in writing:
- who owns the source code, design files and documentation, and when rights transfer;
- the status of third-party components and open-source libraries, whose licences continue to apply;
- that the domain is registered in the client's name;
- whose accounts are used for hosting, analytics, ad platforms, email, app stores, payment providers, CRM — ideally the client's, with the developer given access;
- what is handed over at the end: repository access, credentials, documentation.
See what to get at website handover.
Confidentiality and data
- Confidentiality of business information exchanged during the project.
- If the developer processes personal data — customer databases, form submissions — terms for processing, security and deletion, in line with Azerbaijan's Law on Personal Data. See personal data law.
- Security requirements: access management, secure storage of credentials.
Warranty and support
- A warranty period for fixing defects after launch, if agreed.
- Support as a separate agreement: scope, response times by severity, monthly volume, pricing. See website maintenance.
Termination
- How either side can end the contract, notice periods, payment for work done.
- Handover of work in progress, code and access on termination.
Liability and disputes
- Limits of liability, force majeure, governing law and dispute resolution — for your lawyer to settle.
[ 03 ]
FAQ
Frequently asked questions
Is a contract necessary for a small website?
Yes, even a short one. A page with scope, price, timeline, acceptance and ownership prevents most disputes.
Can the developer keep the rights to the code?
Some agreements license the code to the client rather than transfer it, especially for platforms the developer reuses across clients. What matters is that the terms are clear and that you can keep using, changing and moving your website.
Who should draft the contract?
Many developers have a standard contract. Have your lawyer review it and add a scope annex specific to your project.