What to Put in a Freelance Contract So You Own the Work (India-Specific Clauses)

Last updated: September 2026

A client says, “It’s just a freelance project.”

Three months later, they are using your work everywhere, asking for the source files, giving the work to another freelancer, and telling you they own everything because “that was part of the deal.”

The problem usually started much earlier: the contract never clearly said who owns what.

I’m Riten, founder of Fueler, a portfolio platform that helps professionals get hired through assignments, proof of work, and projects instead of just resumes.

For freelancers in India, a good contract should clearly cover copyright ownership, deliverables, payment, source files, revisions, pre-existing work, portfolio rights, confidentiality, termination, and what happens after the project ends.

This guide breaks down the clauses that matter, what they should say, and the mistakes freelancers should avoid before signing.

What Should a Freelance Contract Include in India?

A freelance contract should do more than record the project price. It should define the work, payment, responsibilities, intellectual property rights, deadlines, revisions, confidentiality, termination, and dispute process.

The most important part for ownership is making it clear whether the client receives a copyright assignment, a licence to use the work, or neither.

1. Names and details of both parties

Start with the full legal names and relevant contact details of the freelancer and client.

If the client is a company, identify the legal entity rather than only using the brand name. This becomes important if a payment or ownership dispute later arises.

2. Scope of work

Describe exactly what you are being hired to create.

For a graphic designer, this could mean:

• 10 social media creatives

• 2 logo concepts

• 1 final logo

• Editable source files

• Exported PNG and PDF files

For a content writer, it could specify the number of articles, word range, research requirements and deliverable format.

A portfolio such as Sarthak makes the difference between a designer's broader body of work and one specific contracted deliverable easy to understand. Your contract should make that same distinction.

3. Payment terms

State the total fee, currency, payment schedule, advance amount and payment deadline.

Do not rely on phrases such as “payment after completion.” Define what completion means and when the invoice becomes payable.

4. Deliverables

List what the client actually receives.

This matters because a final design, editable source file, unused concept, working file and underlying template are not necessarily the same thing.

5. Revision limits

Specify how many revision rounds are included.

For example:

“The project includes two rounds of reasonable revisions. Additional revisions will be billed separately at ₹X per hour or ₹X per revision.”

This prevents unlimited changes from quietly becoming part of the original fee.

6. Intellectual property ownership

This is the clause you should read twice.

It should explain:

• What intellectual property is being transferred

• What rights are being licensed

• Which work is excluded

• When ownership transfers

• Whether the transfer is exclusive

• The geographical scope

• The duration

Under Section 19 of India's Copyright Act, a copyright assignment must be in writing and signed by the assignor or their authorised agent. The assignment should identify the work, specify the rights assigned, duration and territorial extent, and state the royalty or other consideration payable where applicable.

How Does Copyright Ownership Work in a Freelance Contract in India?

Creating a piece of work and owning every right in that work are not questions you should leave to assumptions.

Indian copyright law treats copyright as a collection of rights. A contract can determine which rights are transferred or licensed and under what conditions.

1. Do not write “client owns everything”

That sentence looks convenient but creates ambiguity.

Instead, identify the actual work and rights being transferred.

For instance:

“Upon receipt of full payment, the Freelancer assigns to the Client the copyright in the final approved website copy delivered under this Agreement.”

That is much clearer than:

“All work created during the engagement belongs to the Client.”

2. Specify the rights being assigned

If copyright is being assigned, identify the rights instead of using unnecessarily broad language.

Depending on the work, this may involve rights relating to reproduction, publication, communication to the public, adaptation or other applicable copyright rights.

The Copyright Act specifically requires an assignment to specify the rights assigned.

3. Specify the duration

Do not automatically assume that every copyright assignment is unlimited.

Section 19 provides that if the duration of an assignment is not stated, it is deemed to be five years.

If the parties intend a different duration, the agreement should say so clearly.

4. Specify the territory

The same principle applies to territory.

Section 19 states that where the territorial extent is not specified, the assignment is presumed to extend within India.

If the intended rights cover worldwide use, the contract should expressly address that.

5. Do not confuse ownership with usage

A client may need broad permission to use your work without needing ownership of every underlying material you created.

That is where a licence can be useful.

For example, a freelancer might retain ownership while granting the client an exclusive or non-exclusive right to use the final work for specified purposes.

The appropriate structure depends on the project and negotiation.

What Intellectual Property Should a Freelancer Keep Out of the Contract?

One of the biggest freelance contract mistakes is transferring more than the freelancer actually intended.

Your contract should separate the client's final deliverables from materials, knowledge and assets you already owned before the project.

1. Pre-existing templates

If you already have a presentation template, design system, spreadsheet framework or writing framework, identify it as pre-existing material.

2. General skills and know-how

A client is paying for the project, not necessarily for your general professional knowledge.

A designer should not accidentally give away their general design methods. A developer should not unintentionally transfer general programming knowledge.

3. Reusable components

You may have reusable assets that appear across multiple projects.

If those components are not intended to become the client's exclusive property, the agreement should say so.

4. Unused concepts

A freelancer may create five concepts and the client chooses one.

The contract should clarify what happens to rejected concepts, drafts and unused materials.

5. Third-party materials

Stock assets, fonts, photographs, plugins, code libraries and other third-party materials can have their own licence restrictions.

Do not promise the client ownership of something you do not own.

For a developer, this distinction can become particularly important because a project may contain original code alongside third-party or open-source components. A developer portfolio such as Kartik Kochhar is a useful reminder that a professional portfolio can contain many different types of work, while a contract should identify the specific project assets being delivered.

Should a Freelance Contract Say That Ownership Transfers Only After Full Payment?

Yes, if that is what you and the client have agreed.

This is one of the most practical clauses a freelancer can include because it connects payment with the transfer of rights.

The exact wording should be reviewed for the specific transaction, but the commercial structure is straightforward: payment first, ownership transfer according to the agreed terms afterward.

1. Connect copyright transfer to payment

A contract could state that the assignment of rights becomes effective only after the freelancer receives the agreed full payment.

This avoids ambiguity about whether a client has received ownership before completing its payment obligation.

2. Separate delivery from ownership

You can define when files are delivered and when copyright transfers.

Those do not necessarily have to be the same event.

3. Define late-payment consequences

Include what happens if payment is late.

Possible contractual consequences can include suspension of further work, withholding final deliverables where commercially and legally appropriate, interest or late fees if agreed, and termination rights.

4. Avoid vague payment milestones

Instead of “50% upfront and 50% after completion,” define the milestones.

For example:

50% before work begins
25% after first approval
25% before final delivery and transfer of agreed rights

5. Put extra work outside the original fee

If the client requests work outside the agreed scope, explain how it will be priced.

This protects both the freelancer and client from disagreements about whether additional work is included.

For content professionals, the same principle applies. A portfolio such as Vikravardhan can represent a broad writing portfolio, but a freelance writing contract should still define exactly which articles, formats and rights are included in one paid engagement.

What Should a Freelance Contract Say About Source Files?

Source files deserve their own clause.

A client may assume that buying a finished deliverable automatically means receiving every editable file used to create it. A freelancer may see those files as separate deliverables.

Do not leave that disagreement for the end of the project.

1. Name the source files

Specify whether the client receives:

• PSD files

• AI files

• Figma files

• Premiere project files

• RAW photographs

• Editable documents

• Code repositories

• Working spreadsheets

Only include formats that actually apply.

2. State whether source files cost extra

If editable files are not part of the base package, say so before the project begins.

3. Define third-party assets

If source files contain licensed assets, explain any restrictions that continue to apply.

4. Clarify working files

Not every temporary file needs to be delivered.

The agreement can distinguish between final source files and temporary working material.

5. Connect source-file delivery to payment

If source files are included, specify whether they are delivered after the relevant payment milestone.

For a video project, this distinction can be substantial. Someone such as Prashast may have a portfolio that represents finished creative work, but a contract should separately define whether raw footage, project files and other production materials form part of the client's deliverables.

What Portfolio Rights Should Freelancers Include in Their Contracts?

Freelancers should think carefully before signing away the right to display completed work.

A portfolio is often how the next client evaluates your ability. If you cannot show previous work, the commercial value of that project to your career can be reduced.

1. Ask for portfolio permission

Include a clause allowing you to display the completed work in your portfolio after the client has publicly released it, if appropriate.

2. Respect confidential projects

Some projects cannot be publicly displayed.

The contract should allow confidential work to remain confidential.

3. Consider launch restrictions

For unreleased campaigns, products or brands, portfolio use may need to wait until public launch.

4. Define attribution if relevant

For some projects, the freelancer may want permission to identify themselves as the creator.

This should be negotiated rather than assumed.

5. Separate portfolio use from commercial ownership

A client can own the agreed copyright while the freelancer receives a limited contractual permission to display the completed work as professional work.

That arrangement should be written clearly.

The same thinking applies to social media work. A professional such as Sharvin may build a portfolio around different types of marketing work, but a client contract should determine whether completed campaign work can be publicly shown and under what conditions.

What Confidentiality Clause Should a Freelancer Use?

Confidentiality clauses protect information rather than transferring ownership.

A good freelance NDA or confidentiality section should identify what information is confidential and what the freelancer is expected to do with it.

1. Define confidential information

This could include unpublished campaigns, business plans, customer information, financial information, product plans and private documents.

2. Include reasonable exclusions

Information already public or independently developed may need to be excluded from the definition of confidential information.

3. Explain permitted use

The freelancer should use confidential information only for performing the agreed work.

4. Address subcontractors

If subcontractors or collaborators are allowed, explain whether they must follow equivalent confidentiality obligations.

5. Explain what happens after termination

Confidentiality obligations may continue after the freelance project ends.

The contract should state the intended duration rather than leaving this unclear.

How Should Revisions and Approval Be Written in a Freelance Contract?

Many freelance disputes are not really about copyright. They start because nobody agreed on what “finished” means.

Your contract should create a simple approval process.

1. Define revision rounds

State the number of included revisions.

2. Define a revision

A revision should generally mean changes to an agreed direction, not a completely new project.

3. Charge for scope changes

If the client changes the brief after approval, explain how the additional work will be priced.

4. Set an approval process

State how the client approves work, such as email confirmation or another agreed written method.

5. Address client delays

If the client does not provide feedback or materials on time, the project timeline may need to move.

For a UI/UX freelancer, the distinction can be especially useful because a project can involve multiple rounds of feedback. A portfolio such as Mehul Kundu represents a professional body of work, while the contract should define the actual number of screens, flows, revisions, and final assets included in a particular engagement.

What Should a Freelance Contract Say About Termination?

A freelance contract should explain how either party can end the relationship.

Without a termination clause, a client and freelancer may disagree about what happens to unfinished work, advance payments, outstanding invoices and intellectual property.

1. Define termination notice

State whether either party can terminate with written notice and how much notice is required.

2. Explain payment after termination

The agreement should explain what happens to fees for work already completed.

3. Address unfinished work

Specify whether unfinished work is delivered, abandoned, transferred or retained.

4. Address intellectual property after termination

If copyright transfer depends on payment, explain what happens when the project ends before full payment.

5. Include material breach provisions

Serious issues such as non-payment or misuse of confidential information may require separate termination rights.

What Dispute Resolution Clause Should Freelancers Include in India?

A contract should explain what happens if the freelancer and client disagree.

The goal is not to predict a dispute. It is to avoid deciding the procedure while everyone is already angry.

1. Identify the governing law

State which law governs the agreement.

For an India-specific freelance contract, this will commonly involve Indian law, but the precise wording should reflect the parties and transaction.

2. Choose jurisdiction carefully

Specify the courts or jurisdiction intended to handle disputes, subject to applicable law.

3. Consider arbitration

For suitable commercial arrangements, parties may agree to arbitration.

The clause should be drafted carefully rather than simply inserting the word “arbitration.”

4. Keep written records

Contracts, invoices, approvals, revisions and payment confirmations can become important evidence.

5. Keep the clause realistic

A ₹10,000 freelance project does not necessarily need the same dispute-resolution structure as a large commercial engagement.

The contract should match the size and complexity of the work.

Can Freelancers Sign Contracts Electronically in India?

Electronic contracting is possible in India. Section 10A of the Information Technology Act, 2000 recognises contracts formed through electronic records and states that a contract cannot be denied validity or enforceability solely because electronic records were used.

That means a freelance agreement does not automatically become invalid simply because the parties handle it electronically.

1. Keep the final version

Save the exact contract that was accepted.

2. Preserve acceptance

Keep the signed copy or other reliable record showing acceptance.

3. Avoid undocumented changes

If the scope changes, record the change in writing.

4. Keep invoices with the agreement

Payment records help establish what was actually agreed and paid.

5. Do not depend on WhatsApp alone

Messages can provide useful evidence, but important commercial terms should ideally be incorporated into the formal agreement or a written amendment.

The Indian Contract Act also sets out general requirements concerning free consent, competent parties, lawful consideration and lawful objects for agreements to qualify as contracts, subject to applicable exceptions.

What Are the Biggest Freelance Contract Mistakes to Avoid?

The most expensive contract mistakes are often only a few words long.

Freelancers usually do not need a 40-page agreement for every small project. They need a clear agreement that answers the questions most likely to cause conflict.

1. “Client owns all rights”

Replace this with a specific description of the work and rights being transferred.

2. “Unlimited revisions”

Define what revisions mean and where the original scope ends.

3. No payment-to-ownership connection

State when the agreed transfer of rights takes effect.

4. No pre-existing materials clause

Protect templates, frameworks, reusable components and other materials you already own.

5. No source-file clause

Say whether editable files are included and when they are delivered.

6. No portfolio permission

If displaying completed work matters to your career, address it before signing.

7. No termination process

Explain what happens to payment, unfinished work and rights when the project ends early.

How Can Freelancers Build a Contract Checklist Before Signing?

You do not need to memorise copyright law before accepting a project.

You do need a repeatable checklist that catches the important commercial and ownership questions before work begins.

1. Confirm the parties

Are the correct legal names and contact details included?

2. Confirm the scope

Can another person read the contract and understand exactly what you are delivering?

3. Confirm the money

Is the total fee, payment schedule and due date clear?

4. Confirm ownership

Does the contract clearly say what is assigned, licensed or retained?

5. Confirm timing

Are deadlines, approvals and client dependencies defined?

6. Confirm revisions

Is there a clear limit?

7. Confirm source files

Are editable files included?

8. Confirm pre-existing work

Are your existing assets and know-how protected?

9. Confirm portfolio rights

Can you show the completed work, and when?

10. Confirm termination

What happens if either party ends the project?

11. Confirm disputes

Where and how will disagreements be handled?

12. Keep the final signed version

Do not start a major project based only on a verbal promise.

How Does This Connect to Building a Strong Career or Portfolio?

Good contracts protect more than a single payment. They create clarity around the work you can claim, show and document later. When professionals clearly record what they delivered, what outcomes they contributed to and which work they can publicly display, their proof of work becomes easier to understand. That matters because modern hiring increasingly looks beyond resumes toward evidence of actual execution. Platforms such as Fueler can help professionals organise that evidence into a visible portfolio.

Final Thoughts

A freelance contract should not exist to make a project sound more complicated.

It should remove the questions that become expensive later: who owns the work, what exactly was delivered, when payment is due, which files are included, and what happens if the relationship ends.

In India, copyright assignment language deserves particular attention because Section 19 sets specific requirements around writing, signatures, rights, duration, territory, and consideration.

If the project has significant commercial value, have an Indian lawyer review the agreement before signing it.

A clear contract is not about distrusting a client. It is about making sure both sides mean the same thing before the work begins.

What Should a Freelance Contract Include in India?

A freelance contract should cover the parties, scope of work, deliverables, payment, deadlines, revisions, intellectual property ownership or licensing, source files, confidentiality, portfolio rights, termination, and dispute resolution.

How Do Freelancers Transfer Copyright Ownership in India?

A copyright assignment must be in writing and signed by the assignor or authorised agent. The agreement should identify the work and specify the rights assigned, duration, territorial extent, and applicable royalty or consideration.

Should Copyright Transfer Happen Before or After Full Payment?

The contract can make the transfer of agreed rights effective after full payment. This should be stated clearly rather than assumed. The agreement should also explain what happens if the client does not complete payment.

Can a Freelancer Keep the Right to Show Client Work in Their Portfolio?

Yes, this can be addressed contractually. A freelancer can negotiate permission to display completed work, subject to confidentiality, launch restrictions and any other agreed limitations.

Are Electronic Freelance Contracts Valid in India?

Electronic contracts can be valid in India. Section 10A of the Information Technology Act recognises contracts formed through electronic records and says they cannot be denied validity solely because electronic records were used.

Why 100,000+ professionals use Fueler

Fueler helps professionals showcase proof of work through projects, assignments, case studies, and achievements.

• Thousands of professionals use Fueler to create their digital portfolio

• Thousands of projects are published on Fueler. Check here

• Startups and Companies hire through proof of work on Fueler

• Used by freelancers, creators, marketers, video editors, writers, designers, and product managers

Our mission is to help the next 100 million professionals build a verified professional identity through proof of work