Freelance Contract in India: What to Include and Why It Protects You (2026)
By TechnWaves Editorial Team · Published 2026-06-10 · Updated 2026-07-19
A freelance contract is a written agreement between a freelancer and a client. It explains the work, payment, timeline, revision limits, ownership.
Written by: TechnWaves Editorial Team Reviewed by: TechnWaves Editorial Review Team Last updated: 2026-06-26
A freelance contract is a written agreement between a freelancer and a client. It explains the work, payment, timeline, revision limits, ownership, confidentiality, and what happens if something changes.
Many freelancers start work after a WhatsApp confirmation or verbal approval. That may feel fast, but it can create problems later. If the client asks for extra work, delays payment, rejects delivery, or claims they own all source files, the freelancer may have no clear record to rely on.
A good freelance contract does not need to be complicated. It should clearly explain what both sides agreed before work begins.
Why Freelancers Need a Contract
A contract protects both the freelancer and the client.
It helps define:
- What work will be done
- What work is not included
- How much the client will pay
- When payment is due
- How many revisions are included
- When final files will be delivered
- Who owns the final work
- What happens if the project is delayed
- How either side can end the project
Without written terms, every disagreement becomes a memory battle.
Is a Contract Only for Big Projects?
No. Even small freelance projects should have written terms.
For small jobs, a simple written agreement, quotation approval, or email confirmation may be enough. For high-value work, software projects, brand identity, retainers, intellectual property, or confidential data, a detailed contract is safer.
The bigger the risk, the stronger the agreement should be.
1. Parties to the Contract
Start by identifying both sides clearly.
Include:
- Freelancer name or business name
- Client name or company name
- Address, if needed
- Email address
- Phone number
- GSTIN or business registration details, if applicable
- Authorized person signing or approving
Do not use only nicknames or informal names. If the client is a company, confirm the legal business name and the person authorized to approve the work.
2. Scope of Work
Scope is the most important part of a freelance contract.
It should explain exactly what you will deliver.
Example:
"This project includes design and development of a 5-page business website with home, about, services, gallery, and contact pages. It includes mobile responsive layout, contact form setup, and basic on-page content placement."
Good scope prevents confusion.
Avoid vague lines like:
"Website work as discussed."
That sentence does not protect you when the client later expects extra pages, logo design, content writing, SEO, hosting, or maintenance.
3. Exclusions
Exclusions explain what is not included.
Example exclusions for a website project:
- Domain purchase
- Hosting cost
- Logo design
- Copywriting
- Advanced SEO
- Payment gateway approval
- Monthly maintenance
- Product data entry
- Third-party plugin charges
Exclusions are important because clients often assume small extra tasks are included.
4. Deliverables
Deliverables are the final items the client will receive.
Examples:
- Final logo files
- Website access
- PDF brochure
- Social media creatives
- Source code
- Edited video
- Monthly report
- Strategy document
- Product photos
- Ad campaign setup
Be specific about file formats.
For example:
"Final logo will be delivered in PNG, JPG, PDF, and SVG format. Editable source file will be provided only after full payment."
This avoids arguments about source files later.
5. Timeline and Milestones
Mention the project timeline clearly.
Include:
- Start date
- Expected completion date
- Milestones
- Client feedback deadline
- Delay rules
- Final handover date
Example:
"First design draft will be shared within 5 working days after advance payment and receipt of required content from the client."
This protects you if the client delays content, approvals, or feedback.
6. Client Responsibilities
A freelance contract should not include only freelancer duties. The client also has responsibilities.
The client may need to provide:
- Brand logo
- Content
- Product photos
- Login details
- Feedback
- Approvals
- Payment
- Business information
- Legal or tax details
- Access to tools or accounts
Example:
"Project timeline depends on the client providing content, images, and required approvals on time."
This makes delays easier to handle professionally.
7. Payment Terms
Payment terms should be clear before work starts.
Mention:
- Total project amount
- Advance payment
- Milestone payments
- Final payment
- Due dates
- Payment method
- Late payment handling
- GST or tax details, if applicable
Example:
"Total project fee is Rs 40,000. The client will pay 50% advance before work starts and 50% before final handover."
For longer projects, milestone payments are safer than waiting until the end.
8. Revision Policy
Revision limits protect your time.
A revision policy should explain:
- Number of revision rounds included
- What counts as a revision
- How feedback should be shared
- Charges for extra revisions
- Deadline for feedback
Example:
"This project includes two revision rounds on the approved design direction. Major changes after approval or new requirements will be quoted separately."
Without revision limits, a fixed-price project can become unlimited work.
9. Change Requests and Extra Work
Clients often ask for changes after work starts. Some changes are small. Others are new work.
Your contract should explain how extra work will be handled.
Example:
"Any work outside the approved scope will be treated as a change request. Additional charges and timeline will be confirmed before starting extra work."
This keeps the conversation professional. You are not refusing the client; you are pricing new work separately.
10. Approval and Acceptance
Acceptance means the client agrees that a milestone or final work is approved.
Define how approval works.
Examples:
- Written approval by email
- WhatsApp confirmation
- Signed approval
- Approval after no feedback within a fixed period
- Milestone acceptance before next stage
Example:
"If the client does not share feedback within 7 working days of delivery, the submitted milestone may be treated as accepted for project scheduling purposes."
Use this carefully and get professional review for important contracts.
11. Final Handover
The contract should say when final files, access, or ownership will be handed over.
Example:
"Final files and website admin access will be shared after full payment is received."
This is important for designers, developers, writers, editors, photographers, consultants, and marketers.
Do not hand over everything before payment unless your agreement clearly allows it and you accept the risk.
12. Intellectual Property Ownership
IP ownership is one of the most important contract topics.
Your agreement should explain:
- Who owns drafts
- Who owns final approved work
- Whether ownership transfers after full payment
- Whether source files are included
- Whether portfolio use is allowed
- Whether third-party assets are included
- Whether licensed fonts, images, plugins, or templates are separate
Example:
"Ownership of final approved deliverables will transfer to the client after full payment, except third-party assets, licensed materials, tools, templates, or pre-existing freelancer materials."
For high-value creative, software, or brand work, get legal advice before using an IP clause.
13. Confidentiality
Freelancers may receive sensitive client information.
This can include:
- Business plans
- Customer lists
- Login credentials
- Financial data
- Marketing strategy
- Product details
- Internal documents
- Unpublished designs
- Source code
A confidentiality clause explains that such information should not be shared or misused.
Example:
"Both parties agree to keep confidential business information private and use it only for the project."
For serious confidential work, a separate NDA may be useful.
14. Portfolio Permission
Freelancers often want to show completed work in their portfolio.
The contract should clarify this.
Example:
"The freelancer may display final approved work in portfolio and social media after project completion, unless the client requests confidentiality in writing."
Some clients may not want public display, especially for confidential launches, internal tools, or white-label work.
Decide this before the project starts.
15. Termination Clause
A termination clause explains how the project can end early.
It should cover:
- Client cancellation
- Freelancer cancellation
- Payment for completed work
- Refund rules
- Notice period
- Handover of completed items
- Unpaid dues
Example:
"If the client cancels the project after work has started, advance payment may be adjusted against completed work and time spent. Any unpaid approved work will remain payable."
This avoids confusion when a project stops midway.
16. Delay Clause
Projects are often delayed because of missing content, late feedback, or payment delay.
Add a practical delay clause.
Example:
"Project timeline may be extended if required inputs, approvals, or payments are delayed by the client."
This protects you from being blamed for delays you did not cause.
17. Limitation of Liability
For some freelance work, you may want to limit responsibility for indirect losses, business losses, or third-party issues.
This is especially relevant for:
- Software development
- Websites
- Paid ads
- Marketing campaigns
- Payment gateway integration
- Consulting
- Automation
- Third-party tools
This clause should be drafted carefully by a professional. Do not copy it blindly from the internet.
18. Dispute Resolution and Jurisdiction
The contract should mention how disputes will be handled.
It may include:
- Discussion first
- Written notice
- Mediation or negotiation
- Arbitration, if suitable
- Governing law
- Jurisdiction
For Indian freelancers, this section should be reviewed carefully for higher-value contracts.
Example: Freelance Developer Contract
A freelance developer building a custom web application may include:
- Project scope
- Features included
- Features excluded
- Three milestones
- 40% advance payment
- 30% after demo
- 30% before final handover
- Client testing responsibility
- Source code handover after full payment
- Confidentiality clause
- Change request process
- Support period after delivery
This contract helps both sides understand the project before development begins.
Example: Graphic Designer Contract
A freelance designer creating a brand identity may include:
- Logo concepts included
- Number of revision rounds
- Final file formats
- Source file terms
- Timeline
- Payment schedule
- Portfolio permission
- Third-party font or image responsibility
- Ownership transfer after full payment
This prevents common disputes about unlimited changes and editable files.
Common Freelance Contract Mistakes
Avoid these mistakes:
- Starting work without written approval
- Writing vague scope
- Not mentioning exclusions
- Offering unlimited revisions
- Not defining payment milestones
- Giving final files before full payment
- Ignoring IP ownership
- Not explaining source file terms
- Forgetting confidentiality
- Not saving signed or approved versions
- Copying legal clauses without understanding them
A weak contract can create more confusion than no contract if it promises the wrong things.
How to Save Contract Records
Keep a clean project folder.
Save:
- Signed contract or approved terms
- Quotation
- Scope document
- Change requests
- Client approvals
- Invoice copies
- Payment proof
- Delivery proof
- Final handover record
- Important emails or WhatsApp messages
Use clear file names.
Example:
2026-07-ABC-Traders-Website-Contract-Signed.pdf
Good records help if the client later questions scope, payment, delivery, or ownership.
Related reading
For another angle, see Copyright and IP Rights for Indian Freelancers: What You...
Contract Scope Note
Note: This article is practical guidance, not legal advice. Contract wording, IP ownership, liability, tax treatment and dispute clauses can depend on the work and client relationship. For important projects, get qualified review, then keep matching records through the invoice generator or a written terms draft from the [terms generator](/terms-and-conditions-generator).
Sources checked
Checked on: 2026-07-19. Rules, rates, fees, eligibility and official pages can change. Use these links for the latest official position before filing, applying, buying or relying on a financial/legal decision.
- Indian Contract Act, 1872 (India Code): https://www.indiacode.nic.in/handle/123456789/2187
FAQs
Do freelancers in India need a contract?
Yes. A written contract or approved terms help define scope, payment, timeline, revisions, ownership, and responsibilities.
What should a freelance contract include?
It should include parties, scope, deliverables, exclusions, timeline, payment terms, revision policy, change requests, confidentiality, IP ownership, termination, and dispute handling.
Is WhatsApp approval enough?
WhatsApp approval can be useful proof, but for serious projects it is better to have a clear written contract or formal approved quotation.
Should final files be delivered before payment?
Usually, final files, source files, or access should be delivered after the agreed payment is received, unless your contract says otherwise.
Who owns the work created by a freelancer?
Ownership depends on the agreement, work type, payment, and applicable law. Freelancers and clients should clearly write IP transfer terms in the contract.
Simple Rule
A freelance contract is not about making the client uncomfortable. It is about making the work, payment, revisions, ownership, and responsibilities clear before problems happen. When the agreement is written properly and records are saved carefully, freelancers can work with more confidence and fewer avoidable disputes.