Scope of Work and Deliverables Agreement

Scope of Work and Deliverables Agreement: complete guide

Introduction

A Scope of Work and Deliverables Agreement is a contract that describes, in precise terms, the work a service provider will carry out for a client, the outputs it will hand over, the timeline for doing so, how those outputs will be reviewed and accepted, and how payment is linked to them. It is often called a scope of work, SOW, statement of work or project agreement. It can be a standalone contract for a single project, or a project document that sits under a broader framework agreement such as a Master Service Agreement.

Most disputes between clients and service providers are not about whether a contract exists. They are about what was promised. The client believes a mobile app included an admin dashboard; the developer believes it did not. The client expected unlimited design revisions; the agency quoted for two rounds. The client wants to delay payment until a feature that was never agreed is added; the consultant says the work is complete. A clearly drafted scope of work prevents these disputes by recording, before work begins, exactly what is in scope, what is out of scope, what the client must provide, and what counts as completion.

In India, a scope of work agreement is governed by the Indian Contract Act, 1872, which deals with the formation of contracts, performance, reciprocal promises, breach and compensation. Sections 51 to 54 deal with reciprocal promises and the order of performance, which matters when the client's inputs are a precondition to the provider's work. The Copyright Act, 1957 governs ownership of software, designs, written content and other creative outputs, and requires assignments to be in writing. GST law applies to the fees, and tax deduction at source under the Income Tax Act may apply to payments for professional or technical services. Stamp duty under the state stamp law applies to the agreement.

Drafting a scope document well needs both legal and practical understanding. Deliverables must be described in measurable terms, assumptions and dependencies must be written down, the acceptance process must have a deadline, and a change request process must exist for new requirements. Our team works with you to translate the commercial and technical understanding into a document that both sides can follow day to day, while protecting your position if something goes wrong.

Who Needs It

A Scope of Work and Deliverables Agreement is suitable for:

• Software developers and IT agencies building websites, apps, integrations, dashboards or custom software for clients.
• Design and branding studios producing logos, brand guidelines, packaging, UI and UX designs or marketing creatives.
• Content creators and marketing agencies delivering content calendars, campaigns, videos, social media management or search optimisation work.
• Freelancers and independent professionals, such as writers, photographers, illustrators, translators and developers, taking on project work.
• Consultants delivering reports, assessments, market studies, process documentation or implementation support.
• Architects, interior designers and engineers delivering drawings, designs and project supervision.
• Event management and production companies delivering a defined event or production.
• Clients and businesses hiring vendors, who want clarity on what they are paying for and when.
• Startups outsourcing product development, where the product and its IP are central to the business.

If you have an ongoing relationship with the same client across many projects, a Master Service Agreement with individual statements of work under it is usually more efficient. If service performance needs to be measured continuously, a Service Level Agreement can be added.

Key Benefits

• Shared understanding of the work. Both parties know precisely what is to be delivered, which reduces disputes and rework.
• Protection against scope creep. A clear out-of-scope list and change request process ensure that additional work is paid for.
• Payment tied to milestones. Fees can be linked to deliverables, giving the provider regular cash flow and the client confidence that payment matches progress.
• Defined acceptance. Acceptance criteria and a deemed acceptance period prevent payments being held up indefinitely.
• Clear client responsibilities. The client's obligations, such as providing content, access, approvals and feedback within set times, are recorded, so delays caused by the client do not count against the provider.
• IP ownership settled. The agreement sets out when ownership of deliverables passes to the client and what the provider keeps.
• Easier project management. Timelines, communication channels, review cycles and points of contact are written down for both teams to follow.

What a well-drafted scope looks like in practice. A good scope section describes each deliverable in concrete terms, such as the number of screens, pages, features, formats or words, rather than general phrases like "complete website" or "full branding". It lists assumptions, such as the technology stack or the number of revision rounds, and dependencies, such as content or API access the client must provide by a set date. It also includes an exclusions list, for example hosting, third-party licence fees, data migration or post-launch maintenance, so there is no doubt about what is not included.

Fixed price, time and materials, and milestone-based models. Under a fixed price model, the fee is set for the defined scope, and any change requires a change request. Under time and materials, the client pays for hours or days spent at agreed rates, often with a cap or estimate. Under a milestone-based model, the fee is split into instalments linked to acceptance of specific deliverables. The scope document should reflect the model chosen, because acceptance, change and termination clauses work differently in each.

Eligibility and Legal Requirements

Any parties competent to contract can enter into a scope of work agreement, including individuals, freelancers, proprietors, firms, LLPs and companies. Legal points that shape the document include:

• Certainty. Under Section 29 of the Indian Contract Act, 1872, an agreement whose meaning is not certain or capable of being made certain is void. Vague scope descriptions undermine enforceability.
• Reciprocal promises. Where the provider cannot perform until the client gives inputs, the order of performance should be stated. Under Section 54 of the Indian Contract Act, 1872, if one party fails to perform a promise that must come first, it cannot claim performance of the other's promise and must compensate for any loss.
• Time for performance. Under Section 55, if time is of the essence and a party fails to perform in time, the other may avoid the contract. The agreement should say whether timelines are essential and how delays caused by the client affect them.
• Compensation and liquidated damages. Under Section 74, where a sum is named as payable for breach, the court awards reasonable compensation up to that amount. Delay penalties should be reasonable and linked to genuine loss.
• Intellectual property. Under the Copyright Act, 1957, a freelancer or independent contractor generally owns the copyright in work they create unless it is assigned in writing. Section 19 requires the assignment to identify the work, the rights assigned, the duration and the territory. Where duration and territory are not specified, the law presumes five years and India, which is rarely what the client wants.
• Moral rights. Authors retain certain moral rights under Section 57 of the Copyright Act, 1957, such as the right to be identified. The agreement can address how these will be exercised.
• Taxes. The agreement should state whether fees exclude GST and how TDS will be handled. Providers registered under GST must issue tax invoices.
• Payments to MSMEs. If the provider is a registered micro or small enterprise, the client must pay within the time limits of the Micro, Small and Medium Enterprises Development Act, 2006, failing which interest is payable.
• Data and confidentiality. Where personal data or confidential information is handled, the agreement should include appropriate protection, in line with the Digital Personal Data Protection Act, 2023 and its rules as they come into force.
• Stamp duty. The agreement should be stamped as per the state stamp law. Stamp duty is paid at actual.
• Electronic execution. The agreement can be signed electronically under the Information Technology Act, 2000.

Laws on data protection, tax and stamp duty change from time to time. We check the current requirements at the time of drafting.

Step-by-Step Guide

1. Initial consultation. We understand the project, the parties, the pricing model and whether the document will stand alone or sit under an existing master agreement.
2. Gather project inputs. You share the proposal, quotation, requirement documents, wireframes, briefs or email discussions that describe the work.
3. Break down deliverables. We work with you to list each deliverable in measurable terms, with formats, quantities and specifications.
4. Set milestones and timelines. We map deliverables to milestones with target dates, and link them to client inputs and review periods.
5. Define acceptance. We draft acceptance criteria, a review window for the client, a process for reporting defects, and a deemed acceptance rule.
6. Record assumptions, dependencies and exclusions. We list what the provider assumes, what the client must supply and what is not included.
7. Draft commercial and legal terms. We include fees, payment schedule, change requests, IP transfer on payment, confidentiality, warranties, liability limits, termination, payment for work done and dispute resolution.
8. Your review. You review the draft with your project team. We revise it based on your feedback.
9. Negotiation and finalisation. We respond to the other party's comments and prepare the final version for signature.
10. Execution and handover. We guide you on stamping and signing, and share a change request form and acceptance certificate template for use during the project.

Documents Checklist

For a company or LLP:

• Legal name, registered address, PAN and GSTIN
• Name and designation of the signatory, with board authority where needed

For a freelancer, proprietor or firm:

• Name, business address, PAN and GSTIN if registered
• MSME registration certificate, if applicable

Details of the other party:

• Legal name, address, GSTIN and signatory details

Project information:

• Proposal, quotation or estimate
• Requirement document, project brief, wireframes or design references
• List of deliverables and expected formats
• Proposed milestones and timelines
• Pricing model, fees and payment schedule
• Number of revision rounds included
• Client inputs needed, such as content, data, access credentials or approvals
• Any existing master agreement, NDA or purchase order
• Details of third-party tools, licences or platforms to be used

How Long It Takes

A Scope of Work and Deliverables Agreement is usually ready within 2 to 4 working days from the date we receive the project inputs. A typical timeline:

• Consultation and input review: same day or next working day.
• Deliverable breakdown and drafting: one to two working days.
• Your review and revisions: one working day, depending on your project team's feedback.
• Comments from the other party: depends on them, with our revisions usually within one to two working days.
• Stamping and signing: same day where e-stamping is available.

Large projects with many deliverables or technical specifications may need additional time to define the scope accurately.

Pricing

Our professional fee for a Scope of Work and Deliverables Agreement is ₹ 1,499.

This covers:

• Consultation on the project and pricing model
• Review of your proposal and project inputs
• Drafting of the agreement with deliverables, milestones and acceptance terms
• A change request form and acceptance certificate template
• One round of revisions
• Guidance on stamping and execution

Stamp duty is payable at actual as per the state law. Additional negotiation rounds, Master Service Agreements, Service Level Agreements, NDAs and support with disputes arising during the project are quoted separately.

Common Mistakes to Avoid

• Describing deliverables vaguely. Terms like "full website" or "complete branding" lead to disagreements. Be specific about quantities, features and formats.
• No exclusions list. Without one, clients may assume related work is included.
• No limit on revisions. Unlimited revisions can turn a profitable project into a loss.
• No deemed acceptance. If the client never signs off, payment may be delayed indefinitely.
• Ignoring client dependencies. If client inputs are late, the timeline should move. Record this in writing.
• Transferring IP before payment. Providers should transfer ownership only after full payment.
• Incomplete copyright assignment. An assignment without rights, duration and territory may be read narrowly.
• No change request process. Informal additions agreed over calls or messages often go unpaid.
• No termination payment clause. If the project ends early, the provider should be paid for work done.

What Happens After

Once the agreement is signed:

• Hold a kick-off meeting to walk both teams through the scope, milestones, dependencies and points of contact.
• Track client inputs against the agreed dates, and notify the client in writing if delays affect timelines.
• Use the change request form for every change in scope, with agreed fees and revised timelines before work starts.
• Submit deliverables formally and request acceptance within the agreed review period.
• Issue acceptance certificates or record deemed acceptance where the client does not respond.
• Invoice on milestones and follow up as per the payment terms.
• Transfer IP and hand over source files after full payment, as the agreement provides.
• Close the project with a final acceptance and, where relevant, a handover note and warranty start date.

Our team can help with change requests, payment follow-ups, legal notices for unpaid fees and a Master Service Agreement for ongoing work.

FAQs

What is the difference between a scope of work and a contract?

A scope of work can be a full contract in itself, or a project document that sits under a master agreement. Either way, it is legally binding if signed and it describes the work, deliverables and payment.

Do I need a separate scope of work if I have a Master Service Agreement?

Yes, usually. The master agreement sets the general terms, while a scope of work or statement of work describes each specific project.

How detailed should the deliverables be?

Detailed enough that an independent person could check whether each deliverable has been completed. Include quantities, features, formats and quality standards where possible.

What is deemed acceptance?

It is a clause stating that a deliverable is treated as accepted if the client does not report defects within a fixed review period. It prevents indefinite delays in sign-off and payment.

Who owns the work created under the agreement?

It depends on the agreement. Typically, ownership of final deliverables passes to the client on full payment, while the provider keeps its pre-existing tools, templates and know-how.

Can a freelancer use a scope of work agreement?

Yes. Freelancers benefit greatly from a clear scope, because it protects them against unpaid extra work and delayed payments.

What happens if the client wants additional work?

The change request process applies. The provider estimates the impact on fees and timelines, the client approves in writing, and the agreement is updated accordingly.

Can the client terminate the project midway?

If the agreement allows termination, the client can end the project with notice, but should pay for work completed and accepted, and for work in progress as the agreement provides.

Should I include penalties for delay?

Delay compensation can be included, but it should be reasonable, linked to genuine loss and excused where the delay is caused by the client or events outside the provider's control.

Is GST applicable on the fees?

If the provider is registered under GST, GST applies on the fees at the applicable rate. The agreement should state whether the quoted fees include or exclude GST.

Can the agreement be signed digitally?

Yes. Electronic signatures are recognised under the Information Technology Act, 2000. Stamp duty still applies, and e-stamping can be used where available.

What if the project scope is not fully known at the start?

The agreement can cover a discovery phase first, after which a detailed scope is agreed. Alternatively, a time and materials model with periodic estimates may be used.

Can you review a scope of work sent by our client?

Yes. We review it for unclear deliverables, unfair acceptance terms, IP transfer before payment and other risks, and suggest changes.

Related Documentation services

• Service Level Agreement
• Shareholders Agreement
• Terms of Service
• Vendor Agreement