Essential Legal Rules Governing Acceptance in Contracts

Every contract you have ever signed, clicked “I agree” on, or shaken hands over rests on one quiet legal moment: acceptance. An offer by itself creates no obligation. It is only when the other party accepts it, in the right way, that a proposal turns into a binding promise. But Indian contract law does not treat every “yes” as valid. There are specific rules an acceptance must satisfy before courts will enforce it, and understanding these rules is essential for anyone studying business law or planning to run a business someday.

What counts as acceptance in the eyes of the law 🔗

The Indian Contract Act, 1872 defines acceptance under Section 2(b) as the moment when the person to whom a proposal is made signifies their assent to it. Once this happens, the proposal becomes a promise. This sounds simple, but the Act does not stop there. Section 7 lays down the actual conditions that this assent must meet for it to hold up as a valid, enforceable acceptance, and Section 8 adds a few situations where acceptance can be inferred even without a spoken or written “yes.”

Think of these rules as a checklist. An offeree’s response might feel like acceptance in everyday language, but unless it clears every item on this checklist, a court may treat it as something else entirely, such as a counter-offer or a mere expression of interest.

The core legal rules for a valid acceptance 🔗

It must be absolute and unqualified 🔗

An acceptance cannot pick and choose which parts of an offer it agrees to. Section 7 of the Act requires that acceptance mirror the offer exactly, without modifications, additions, or conditions attached. If the offeree changes even one term, such as the price, delivery date, or payment method, the response is legally treated as a counter-offer rather than acceptance. A counter-offer cancels the original offer, and the ball moves back to the first party’s court. They can accept, reject, or make a fresh counter-offer of their own.

This is exactly what happened in the classic English case Hyde v. Wrench (1840), where a seller offered his farm at a stated price, and the buyer replied with a lower figure. Courts have consistently applied this same logic in India: a qualified “yes” is not really a yes at all.

It must be communicated, not merely intended 🔗

Mentally deciding to accept an offer, or even writing “accepted” on a piece of paper and keeping it in a drawer, does not create a contract. The acceptance has to actually reach the offeror, or at least be put into a process that the law recognises as communication, such as posting a letter or sending a message through an agreed channel. Silence generally cannot be treated as acceptance either. The offeror cannot impose a contract on someone by saying “if I don’t hear from you, I’ll assume you agree.” According to a review of essential acceptance principles, this requirement traces back to older common law reasoning that an offeree should not be bound to an obligation without a clear, positive act of consent, a principle Indian courts have consistently followed while interpreting lawful acceptance under the 1872 Act.

It must follow the manner prescribed by the offeror 🔗

If an offer specifies exactly how it should be accepted, say by registered post, email, or a signed form, the offeree is expected to follow that method. Section 7(2) of the Act gives the offeror some flexibility here: if the offeree accepts in a different manner, the offeror can, within a reasonable time, insist that the prescribed method be followed. If the offeror stays silent instead of objecting, the acceptance is treated as valid despite the deviation. Where no particular method is prescribed, the acceptance simply needs to be communicated in a usual and reasonable way, an approach summarised well in this overview of offer and acceptance provisions.

It must be given within a reasonable time and before the offer lapses 🔗

Offers do not stay open forever. If a time limit is specified, acceptance must arrive within that window. If no deadline is mentioned, the acceptance still has to happen within what courts consider a “reasonable time,” a standard that depends on the nature of the transaction, industry practice, and the mode of communication used. A stock market offer, for example, may only be reasonable for a few hours, while an offer to sell a piece of land might allow a longer window. An offer also automatically comes to an end through revocation by the offeror, rejection by the offeree, the offeree’s death or incapacity (where relevant to the offer), or simply the passage of the deadline. Acceptance given after any of these events is legally worthless.

It must come from the person to whom the offer was made 🔗

Only the person the offer is addressed to, or their duly authorised agent, can accept it on their behalf. This rule was firmly established in Powell v. Lee (1908), where a school board unofficially decided to appoint a headmaster, and one board member personally informed the candidate. When the board later reversed its decision, the candidate sued for breach of contract. The court held that no binding contract existed because the communication of acceptance had come from an unauthorised individual rather than the board acting in its official capacity, a distinction explained in detail in this breakdown of acceptance rules under the Contract Act. The lesson translates directly into Indian business practice: acceptance conveyed by someone without authority to bind the company generally will not create an enforceable contract.

Acceptance can also be shown through actions, not just words 🔗

Section 8 of the Act recognises that a person can accept an offer by performing the conditions of the proposal or by accepting consideration for a reciprocal promise, even without saying a formal “yes.” This is significant because many everyday business dealings run on conduct rather than paperwork. If a supplier starts delivering goods on the terms of a proposed contract and the buyer starts paying for them, both parties may be treated as having accepted those terms, whether or not either side ever signed anything.

When conduct itself becomes acceptance: Brogden v. Metropolitan Railway Co. 🔗

Few cases illustrate the “acceptance by conduct” principle better than Brogden v. Metropolitan Railway Co. (1877). Brogden had supplied coal to the Metropolitan Railway Company informally for years, without any written contract. Eventually, the railway company drew up a formal draft agreement and sent it to Brogden for review. Brogden filled in a few blank details, wrote “approved” on the document, and returned it. Here is the twist: the railway company’s manager simply filed the document away and never sent back a formal acceptance. Yet both parties continued placing and fulfilling coal orders exactly as the draft described.

When a dispute arose later, Brogden argued that no binding contract existed because his amendments amounted to a counter-offer that was never formally accepted. The House of Lords disagreed. The court held that by ordering and accepting coal deliveries under the terms of the amended draft, the railway company had accepted Brogden’s counter-offer through its conduct, even though it never sent an explicit written or verbal acceptance.

The judgment is often cited for a broader lesson: where two parties act as though a contract exists and perform its terms consistently, courts can treat their conduct as forming a valid agreement, provided that conduct clearly communicates assent. This principle sits comfortably alongside Section 8 of the Indian Contract Act and remains highly relevant, since so many Indian business relationships, particularly with regular suppliers and vendors, run on informal, conduct-based dealings rather than freshly negotiated contracts each time.

Putting the rules together 🔗

These rules together protect both sides of a transaction. They stop offerors from being trapped into contracts they never truly agreed to, and they stop offerees from being bound by half-hearted or unauthorised responses. For anyone heading into business, whether managing procurement, sales, or vendor relationships, this checklist is not just exam material. It shapes how emails, purchase orders, and verbal confirmations should be handled in practice, since a poorly worded “acceptance” can either create an unintended contract or fail to create one you actually wanted.

What do you think? If your company routinely accepts orders through informal conduct, such as shipping goods after a verbal confirmation, does that create the same legal certainty as a signed contract? And where do you think the line should sit between reasonable flexibility in business dealings and the strict formality the law demands for a valid acceptance?

References

1. https://lddashboard.legislative.gov.in/actsofparliamentfromtheyear/indian-contract-act-1872
2. https://thelaw.institute/business-law-as-applicable-to-co-operative-i/essentials-lawful-acceptance-indian-contract-act/
3. https://www.drishtijudiciary.com/to-the-point/ttp-indian-contract-act/acceptance-under-indian-contract-act-1872
4. https://blog.ipleaders.in/acceptance-and-modes-of-acceptance-under-indian-contract-act-1872/
5. https://en.wikipedia.org/wiki/Brogden_v_Metropolitan_Rly_Co