Learning purpose

This lesson examines how an offer becomes a contract through acceptance under English law, with particular attention to construction transactions in which the parties exchange purchase orders and acknowledgements, commence performance, issue design information and make payments before a formal subcontract is signed. The purpose is to develop a disciplined method for identifying the words or conduct said to constitute acceptance and for determining whether that response assented to the offer as made.

Successful completion requires the learner to distinguish an effective acceptance from a counter-offer, request for information or provisional approval; explain when acceptance must be communicated and why silence will not ordinarily suffice; analyse the effect of a prescribed method, signature condition or electronic message; determine whether performance objectively refers to a particular offer; apply the traditional offer-and-acceptance analysis to competing standard terms; and prepare a reasoned opinion from a construction procurement record in which work and payment precede formal execution.

1. The legal character and function of acceptance

Acceptance is the final and unqualified expression of assent to the terms of an offer, made while that offer remains capable of acceptance and in a manner which objectively communicates agreement. Its legal function is exacting because acceptance converts the proposal into a contract, subject to the other requirements of contractual formation. The response must therefore correspond with the offer rather than express general commercial approval, announce a future intention to agree, or propose a different bargain. A claims specialist must identify the particular offer, its incorporated documents and its conditions before deciding whether any later communication accepted it.

The objective principle governs this inquiry in the same way that it governs identification of the offer. English law is concerned with the meaning conveyed by the recipient's words and conduct to a reasonable person in the position of the offeror, not with an undisclosed intention to accept or an internal belief that the contract had already been made. A contractor may privately decide to accept a purchase order, allocate labour and open a project cost code without communicating assent through words or conduct known to the employer. Those internal acts do not ordinarily conclude the contract because they give the offeror no objective indication that the proposal has been accepted.

The requirement of correspondence between offer and acceptance is sometimes described as the mirror-image principle. That description is useful if it directs the analyst to compare the proposed terms with the response, although it should not replace the comparison itself. A response that accepts the scope and price but changes the completion date, design standard, payment period or liability cap does not ordinarily assent to the offer as made. It proposes a different bargain and is therefore capable of constituting a counter-offer. The heading "Acceptance", a signature beneath an order acknowledgement, or language stating that the order is accepted will not cure the introduction of different terms.

Construction correspondence frequently obscures this distinction because the parties may agree the commercial core while continuing to dispute their allocation of risk. An email may confirm price and programme "subject to agreement of the subcontract conditions", or a contractor may return a purchase order after writing that its tender qualifications remain applicable. Such a response may demonstrate a strong intention to proceed, but it does not necessarily accept the terms proposed by the other party. If the reservation concerns provisions that the parties treat as conditions of commitment, the exchange remains in negotiation until the counter-offer is accepted, the reservation is withdrawn, or the subsequent conduct objectively establishes a contract on identifiable terms.

Acceptance must be absolute in relation to the offer, but it need not repeat every term or employ any prescribed legal formula unless the offer requires one. A short email stating "We accept your offer dated 4 May, including the documents listed in Appendix 1" may provide clearer assent than a lengthy letter which restates the price while introducing qualifications elsewhere. The entire communication must be read, including attachments, footers and incorporated standard terms. Selective reading is especially dangerous where an acknowledgement form contains an apparently unqualified signature block on its first page and limitations or exclusions on a later page.

A request for information differs from a counter-offer because it seeks clarification without making assent conditional upon a changed term. In Gibson v Manchester City Council [1979] UKHL 6, Lord Edmund-Davies treated Mr Gibson's enquiry about a possible price reduction as exploratory rather than as a counter-offer, although the appeal succeeded because the council had made no offer capable of acceptance. Applied to procurement, an email asking whether payment can be made in forty-five days may leave an existing offer available if the sender does not make agreement conditional upon that change. A response stating that the sender will contract only if the revised period is agreed has a different objective effect and proposes a different bargain.

Where acceptance is alleged through conduct, the analysis must connect that conduct to the proposal said to have been accepted. That connection may be difficult to prove where several versions of a purchase order circulated, an employee acted upon an oral instruction without seeing the attached conditions, or a portal replaced one order with another. The question remains objective: did the words and conduct, considered within the complete communication record, establish agreement upon the identified terms? Accordingly, the claims analysis should prove which version reached the relevant participant before attributing the later conduct to that version.

Separately, the role and mandate of the person whose conduct is relied upon present an evidential question distinct from the existence and objective meaning of the alleged assent. A claims opinion should not assume that responsibility for rates, technical coordination or work release also carried power to conclude the proposed subcontract or settle disputed liability terms. The reviewer should examine the relevant retainer, appointment, delegated authority matrix, internal approval record, previous communications and any representation made to the other party. Until that material has been examined, the opinion should identify the authority issue as unresolved and avoid attributing contractual assent to the company through that individual.

The time of acceptance determines the formation date and requires the reviewer to establish which proposal was then under consideration. If a contractor signs and returns a tender acceptance after the stated validity period, the reviewer should not assume that the original offer remained open. The later communication and any subsequent performance must be analysed on their own terms to determine whether they objectively established an agreement. That disciplined chronology prevents an opinion from assigning the contract to a proposal which the parties were no longer treating as available.

The content of the resulting contract follows from the offer accepted, together with any terms incorporated through the accepted proposal and any later agreed variation. A conclusion that conduct constituted acceptance must therefore identify the terms to which that conduct referred. It is insufficient to say that both parties performed and therefore "a contract" existed. Any resulting opinion must state which offer was accepted, whether the conduct was consistent only with that offer, when acceptance occurred, and which conditions governed the subsequent work.

2. Communication, prescribed methods and silence

The general rule requires acceptance to be communicated to the offeror because the offeror should not ordinarily become bound through an assent that remains unknown and inaccessible. Communication may occur through spoken words, signed correspondence, email, a procurement portal or conduct which objectively conveys assent. The rule is concerned with receipt and objective accessibility rather than proof that a director personally read the message at the moment of arrival. A communication received through the channel designated by the organisation may bind even though internal administration delayed its review.

In Schuldenfrei v Hilton (Inspector of Taxes) [1998] STC 404, Neuberger J rejected an argument that an agreement arose when a taxpayer remained inactive after receiving an amended assessment. Even assuming that the assessment could constitute an offer, the taxpayer had made no communication capable of accepting it. The judge treated mutual communication as ordinarily required for contractual agreement and referred to an earlier authority as the familiar illustration that an offeror cannot obtain assent by telling the recipient that no response is required. This decision supports a narrow proposition: inactivity alone does not communicate acceptance merely because the offeror seeks to give it that effect.

Silence must nevertheless be distinguished from conduct and from an agreed course of dealing. A party which receives a counter-offer, knowingly requests and accepts performance referable to it, and pays under its machinery has not remained legally silent in the relevant sense. That combination of communicated instructions, accepted performance and payment may objectively communicate acceptance of the counter-offer. There may also be an established relationship in which orders are regularly accepted through dispatch or performance without a separate acknowledgement. Ultimately, the conclusion depends upon the objective meaning of the conduct, not upon an exception permitting the offeror to prescribe silence as assent.

An offeror may prescribe a method by which acceptance is to be communicated. Construction of the relevant wording must determine whether that method is a condition of contractual commitment or merely identifies the procedure which the offeror expects the recipient to follow. Language stating that no contract will arise unless a signed original reaches a named director presents a condition which a request to "please sign and return" does not necessarily impose. The opinion must construe the provision within the complete offer before deciding whether another communicated response could conclude the proposed bargain.

Construction documents often use signature clauses for more than one purpose, and those purposes must be separated. A signature block may provide convenient evidence of assent without making signature a condition of formation. Another clause may state that the subcontract will not become effective until both parties execute and exchange counterparts, in which case execution is objectively presented as a condition of legal commitment. A third provision may require signature before mobilisation for administrative control, while the operative order separately authorises immediate work. The effect depends upon the document as a whole and the parties' later communications and conduct.

Where a mandatory method has not been followed, the offeror may waive compliance through words or unequivocal conduct. The conclusion must identify conduct which is inconsistent with continued reliance upon the prescribed method. Permitting limited early works may be consistent with a separate interim contract and therefore insufficient to waive the signature condition attached to the main subcontract. By contrast, directing full performance, administering payment and invoking the unsigned subcontract's variation machinery may support an inference that the parties elected to proceed without formal execution. RTS Flexible Systems demonstrates why the factual and contractual setting controls that conclusion.

The time and place of acceptance require particular care where messages are transmitted electronically. In Entores Ltd v Miles Far East Corporation [1955] EWCA Civ 3; [1955] 2 QB 327, the Court of Appeal treated acceptance by telex as effective when received by the offeror, rather than when sent. The decision distinguished instantaneous communication from the exceptional rule applicable to some postal acceptances. Its reasoning also examined failed transmissions and explained why the sender may need to repeat an acceptance which the offeror has not received.

In turn, the reasoning in Entores does not permit a purely mechanical inquiry which ignores the parties' conduct or responsibility for a failed transmission. Denning LJ distinguished a sender who knows that the message has failed from a sender who reasonably believes it arrived, and he addressed the position where the offeror's own fault prevents receipt. A modern analysis should therefore identify the adopted communication channel, determine whether the message reached that channel and examine any failure at either end before selecting the time and place of acceptance.

The postal rule should not be assumed merely because a signed acceptance was placed in the post. Its application depends upon whether postal acceptance was contemplated or reasonable, and it may be displaced by express wording requiring receipt. Many construction procurements use electronic portals, email or document-management systems that record transmission and receipt, leaving little reason to rely upon postal analysis. The opinion should examine the contractual notice provisions and actual communication method rather than begin with a presumed exception.

Electronic systems create evidential questions which should not be mistaken for different rules of formation. A portal audit may establish the time of upload, the document version and the user account employed. Email headers may show delivery to the employer's server, while access logs may show when the recipient opened an attachment. Automated acknowledgements may prove that a message was received without proving that its contents communicated substantive acceptance. The claims specialist should preserve these records and distinguish delivery evidence from the legal meaning of the message delivered.

An acknowledgement of receipt does not ordinarily communicate assent merely because it uses the word "acknowledge". A document may confirm that an order has been received, reserve review of its conditions and promise a later response. Conversely, an "order acknowledgement" may accept the order while substituting the supplier's own terms, making it a counter-offer. The complete text, incorporated conditions and transmitted attachments determine the objective legal effect of the communication. Internal labels generated by procurement software do not replace objective construction of the communication.

The analysis of communication should therefore record the channel, time of receipt, prescribed method, identity and authority of the recipient, and any evidence of system failure or absence. It should then address whether the message communicated final assent, a conditional response, or receipt alone. A finding that the communication was delivered answers only the evidential question of receipt; it does not establish that its content accepted the offer.

3. Acceptance by conduct and competing standard terms

Acceptance may be inferred from conduct where the conduct, assessed objectively and in context, communicates assent to the offer. Construction contracts make this route commercially important because parties often commence design, order materials, grant access or make payment before completing their intended documentation. Performance does not remove the continuing legal requirement to identify an objectively manifested contractual agreement. Any conduct relied upon must be sufficiently connected with the offer alleged and must occur while the offer remains available, with knowledge of its terms.

The Supreme Court's reasoning in RTS Flexible Systems supplies a modern illustration of agreement established through conduct after an incomplete documentary exchange. Although the parties did not execute the contemplated formal contract, they settled the price and most terms, performed and paid, and agreed a change to the delivery sequence. Their words and conduct established a wider contract and waived the execution condition. That conclusion did not rest upon performance alone: it depended upon the terms settled, the later variation and contractual administration which objectively referred to the wider agreement identified by the court.

Conduct may remain equivocal where another contractual or non-contractual explanation exists for the performance relied upon as acceptance. A contractor performing limited investigations under a letter of intent does not necessarily accept the full building contract under negotiation. Equally, a subcontractor delivering one urgent component in response to a separate site instruction may not accept a purchase order covering a much wider package. Payment of an invoice may discharge an admitted value without accepting exclusions printed on the invoice. Every suggested basis must be tested against the record before the conduct is characterised as acceptance.

Proof of the necessary connection may include evidence that the party received and reviewed the offer before commencing performance, or that its authorised representative acted upon the offer's instructions. It becomes more difficult where standard conditions were attached after mobilisation, hidden behind an inaccessible link or sent to a department unconnected with the work. Conduct which began before particular conditions were communicated cannot, without more, demonstrate assent to those conditions. Accordingly, the formation chronology must identify precisely when each set of terms arrived.

Competing standard terms produce the problem commonly called the battle of forms. A supplier issues a quotation on its conditions, the buyer sends a purchase order on different conditions, and the supplier returns an acknowledgement referring again to its own conditions. Goods or services are then supplied without an express reconciliation of the documents. A court must determine whether a contract arose and which set of terms was accepted. This exercise remains one of objective offer and acceptance, applied to the actual sequence.

In Tekdata, the Court of Appeal examined a sequence in which the buyer issued purchase orders on its own conditions, the seller returned acknowledgements on different conditions, and delivery followed. That sequence required each document to be assigned its contractual function before the later conduct could be characterised. The court held that the seller's acknowledgement constituted a counter-offer and that the buyer accepted it by taking delivery, so the seller's conditions governed the transaction.

That result demonstrates the danger of assuming that the first quotation, the buyer's usual conditions or the last general reference automatically governs. Longmore LJ stated that traditional offer-and-acceptance analysis should ordinarily be applied, while recognising that the documents and conduct may disclose a different objective intention in a particular relationship. Accordingly, the required method begins with the transaction's documentary sequence and permits a course-of-dealing argument only where the evidence proves a consistent and known practice.

The Court of Appeal returned to the subject in Tekdata Interconnections Ltd v Amphenol Ltd [2009] EWCA Civ 1209. In that transaction, the buyer issued purchase orders on its conditions, while the seller acknowledged them on different conditions and supplied the goods. Longmore LJ held that the traditional offer-and-acceptance analysis should ordinarily be applied, although a different objective intention may emerge from the documents and conduct in a particular relationship. On the facts, the seller's acknowledgement was a counter-offer accepted when the buyer received delivery, so the seller's terms governed.

Tekdata prevents an analyst from replacing the documentary sequence with an impression that the parties generally expected the buyer's conditions to apply. A settled course of dealing may affect the objective meaning of later exchanges, but it must be proved through consistent transactions and knowledge of the relevant terms. Commercial familiarity alone does not displace a counter-offer communicated in the transaction under review. Each purchase order may form a separate contract, and the applicable terms may require transaction-specific analysis.

Construction supply chains frequently add further complexity because performance occurs in stages. Design work may begin after the purchase order, manufacturing may follow an acknowledgement, and delivery may occur after revised terms are exchanged. A contract may arise at the first conduct objectively accepting a subsisting offer, leaving later documents ineffective unless they constitute an agreed variation. Consequently, the analyst must avoid treating later performance as a fresh acceptance every time a project stage begins.

Payment conduct also requires careful treatment within the wider chronology of communications, performance and contractual administration. A main contractor may certify and pay a subcontractor's first application using the valuation dates in its purchase order, which supports acceptance of that machinery. The same payment may provide little evidence concerning an unrelated liability cap or design warranty. Conduct can establish the contract without proving incorporation of every disputed condition, especially where the parties' documents did not identify a single coherent offer. Term-by-term evidence should be considered where the global formation analysis leaves a genuine conflict.

A contract arising by conduct can include an earlier period of performance where the objective agreement and commercial context support that result, as recognised in the authorities considered in RTS Flexible Systems. That retrospective conclusion should not be assumed merely to avoid an inconvenient gap in the contractual analysis. A court will not impose a contract which the parties did not make, particularly where competing standard terms allocate liability for delay or defects in opposite ways. Accordingly, the formation opinion must preserve the distinction between finding a workable bargain and constructing one after the dispute has arisen.

4. Judicial analysis

4.1 Wells v Devani: objective agreement expressed through words and conduct

In Wells v Devani [2019] UKSC 4, an estate agent claimed commission following the sale of flats. Mr Devani and Mr Wells had spoken by telephone, after which Mr Devani introduced a purchaser that completed the transaction. The trial judge found that Mr Devani had explained his commission rate of two per cent plus VAT, although the parties had not expressly discussed the event which would trigger payment. Mr Devani supplied his written business terms only after he had already introduced the eventual purchaser.

The Supreme Court held that a binding contract had been made during the telephone conversation. At paragraph 17, Lord Kitchin stated that the court must consider what the parties communicated through words and conduct and determine objectively whether they intended legal relations and agreed the terms required for a binding contract. The inquiry concerned the bargain objectively made, rather than the private understanding of either participant or the later written terms.

At paragraph 19, the court accepted the trial judge's finding that Mr Devani had stated his commission rate of two per cent plus VAT and that Mr Wells had agreed to that rate, while the event which would trigger payment had not been discussed. Paragraph 23 records Lord Kitchin's conclusion that the natural meaning of their bargain made commission payable upon completion from the proceeds of sale. His conclusion was therefore a completion trigger derived from the objective meaning of the telephone agreement, not an agreement that payment became due merely upon identifying or introducing a prospective purchaser.

This decision requires a distinction between interpreting the parties' words and conduct and implying a term into an agreement which already exists. Lord Kitchin held that interpretation established the payment trigger and explained, in the alternative, why the same trigger could have been implied if implication had been necessary. In his additional observations, Lord Briggs agreed with the proposed disposal and the reasons given, while adding that the context and conduct revealed a sufficiently certain bargain. Neither route permits a court to manufacture agreement where the communications fail to disclose contractual assent. Paragraph 18 preserves that boundary by recognising that words and conduct may be too vague to reveal either terms or contractual intention.

For construction claims, Wells v Devani supports examination of the entire exchange rather than a search for an instrument bearing a signature. It does not establish that mobilisation invariably accepts a purchase order or that every omitted term can be supplied by law. The party asserting acceptance must still identify a sufficiently certain proposal and conduct which objectively expresses assent to it.

4.2 RTS Flexible Systems v Muller: qualified assent, performance and waived execution

In RTS Flexible Systems Ltd v Molkerei Alois Muller GmbH & Co KG [2010] UKSC 14, work commenced under a letter of intent while the parties negotiated a detailed contract for automated production equipment. Muller's letter proposed commencement of the project upon the expressly stated price, programme and interim contractual conditions. RTS responded that it had commenced work subject to two identified points, and Muller subsequently accepted both points. The limited interim agreement therefore arose from proposal, qualification and assent rather than from unqualified acceptance of the first letter alone.

After the interim arrangement expired, negotiations and performance continued without execution of the intended formal contract. By then, the parties had settled the price and most conditions, performed and paid, and agreed a later change to the delivery sequence. On that record, the Supreme Court found that a wider contract had arisen by approximately 25 August 2005, incorporating the provisions settled by 5 July together with the parties' later variation.

An unfulfilled execution clause presented a direct question concerning prescribed formality and the possibility of later waiver by conduct. Under the draft wording, legal effectiveness depended upon execution and exchange of contractual counterparts. The court held that the parties' unequivocal conduct demonstrated waiver of that requirement. Their agreed variation, performance under the settled terms and payment were inconsistent with the proposition that no wider contract existed until signature.

The court did not hold that work alone accepted every term in the draft. Paragraphs 47 to 54 stress that performance is relevant but the result depends upon the circumstances, and the court must not impose a contract which the parties never reached. In discussing an earlier decision at paragraphs 52 to 54, the Supreme Court contrasted a transaction in which work proceeded at the buyer's request while the parties remained in continuing disagreement about liability for late delivery. Where material liability terms remain in active dispute, performance may therefore be referable to a request to proceed without establishing the proposed wider contract.

RTS Flexible Systems therefore supplies two acceptance lessons which must be applied separately to the interim and wider agreements. A qualified response requires assent to the qualifications before it can conclude the proposed bargain, while later conduct may both communicate agreement and waive a formal execution condition. Each conclusion requires close identification of the offer, the qualification, the responding conduct and the terms objectively implemented.

4.3 Schuldenfrei v Hilton: silence does not communicate assent

In Schuldenfrei v Hilton (Inspector of Taxes) [1998] STC 404, the taxpayer relied upon an amended assessment showing no tax payable and contended that his failure to object contributed to an agreement under section 54 of the Taxes Management Act 1970. The Special Commissioners rejected that contention, and Neuberger J dismissed the taxpayer's appeal. His alleged acceptance consisted of inactivity rather than any communicated response or conduct directed towards the proposal.

Neuberger J reasoned that an agreement ordinarily requires mutual communication and that inactivity could not establish the alleged agreement on the facts. He referred to an earlier silence authority as an illustration within that reasoning, but the present lesson relies upon Neuberger J's own treatment and result rather than upon an unexamined account of that report. His judgment also distinguished a unilateral offer accepted through performance because the taxpayer had done nothing capable of constituting acceptance by conduct.

That reasoning does not prevent acceptance by conduct or invalidate an established order-and-performance procedure. It prevents the offeror from converting the recipient's inactivity into assent merely by declaring that silence will count. In construction procurement, an unanswered purchase order does not become a contract solely because it states that failure to object within three days constitutes acceptance. Subsequent mobilisation, design submission or delivery may alter the position if that conduct objectively refers to the order and communicates assent.

4.4 Entores: receipt of instantaneous acceptance

Entores Ltd v Miles Far East Corporation [1955] EWCA Civ 3; [1955] 2 QB 327 concerned acceptance sent by telex from Amsterdam and received in London. The Court of Appeal held that the contract was made when and where the acceptance was received. Denning LJ explained the practical distinction between a posted letter and an instantaneous exchange in which a failed or incomplete transmission can ordinarily be detected and corrected.

All three members of the Court of Appeal agreed that the ordinary rule required notification of acceptance to the offeror and that the contract was made in London when the telex acceptance was received there. Their reasoning also recognised that responsibility for a failed transmission may matter, including the position where the offeror's own fault prevents effective receipt. Applied by analogy to modern project communications, the inquiry requires proof that the acceptance reached the channel adopted by the parties and attention to any transmission failure for which one side was responsible.

4.5 Tekdata: acceptance in a battle of forms

In Tekdata Interconnections Ltd v Amphenol Ltd [2009] EWCA Civ 1209, the Court of Appeal confirmed that the traditional analysis ordinarily governs a battle of forms. Purchase orders on the buyer's conditions were followed by acknowledgements on the seller's conditions and then delivery. The seller's acknowledgement constituted a counter-offer which the buyer accepted by receiving the goods, and the seller's conditions therefore applied.

Longmore LJ recognised that the documents or conduct may disclose a different objective intention in a particular case, especially within an established relationship, but the evidence must justify departure from the conventional sequence. A claims specialist should therefore begin with offer, counter-offer and acceptance, then test whether the proven course of dealing changes the objective meaning of the transaction. An assertion that one party's terms "always applied" requires documentary proof from the preceding contracts.

5. Method of analysis for a construction claim

The review should begin with a chronological acceptance schedule linked to the offer schedule prepared under Lesson 2. Each entry should identify the subsisting offer, the response or conduct relied upon, the sender and recipient, the time of receipt, the authority of the participants, and the legal effect advanced. Every qualification and incorporated document must be preserved because a response cannot be classified without comparison against the offer as a whole.

At the first stage, precise identification is required of the communication or conduct alleged to constitute the operative expression of assent. A reviewer should quote the operative words or describe the conduct precisely, rather than state that the parties "agreed" or "proceeded". Depending upon context, a signed return, an email confirmation, a portal approval, commencement of identified work, delivery of goods or payment under a stated mechanism may each communicate assent. Any opinion should explain why the act refers to the offer alleged and why any competing explanation is less persuasive.

Secondly, the reviewer requires a term-by-term comparison between the subsisting offer and the response alleged to accept it. Price, scope, programme, payment, design responsibility, insurance, indemnity, delay liability and caps should be mapped where either response differs from the offer. A response which introduces a materially different term should be classified as a counter-offer, even if the parties agreed most of the transaction. Later assent to that counter-offer should then be located rather than continuing to describe the original proposal as accepted.

Thirdly, the inquiry concerns the communication, receipt and contractual accessibility of the response alleged to constitute acceptance. Any opinion should establish when the acceptance reached the offeror through the agreed or authorised channel and whether any prescribed method was exclusive. Portal records, email headers, acknowledgement receipts and document registers may be required. If acceptance was allegedly communicated through an agent, the evidence should establish the agent's authority to receive it on the offeror's behalf.

The fourth stage concerns the distinction between legally ineffective silence and conduct which objectively communicates contractual assent. Silence should not be treated as assent merely because the offer stated that objection was required. The reviewer should identify any positive conduct following receipt, determine who knew of the offer, and connect the conduct with the work or machinery proposed. If performance is equally referable to a letter of intent, emergency instruction or existing framework agreement, that alternative must be addressed.

The fifth stage concerns formal execution and the effect of any unsatisfied condition governing contractual effectiveness. Any clause making signature, exchange or approval a condition of effectiveness should be extracted verbatim into the working note. The opinion must distinguish actual compliance, later waiver and the possible formation of a separate interim contract. Full performance and contractual administration may support waiver, whereas limited work within an early-works cap may leave the main-contract signature condition untouched.

At the sixth stage, the analysis addresses competing forms and the objective legal effect of each document within their chronological sequence. That sequence should begin with the quotation and continue through every purchase order, acknowledgement, revised order, delivery and payment. Traditional offer-and-acceptance analysis should be applied before any course-of-dealing argument is considered. If a party relies upon prior transactions, the reviewer should obtain their complete orders and acknowledgements to determine whether they establish a consistent and known practice.

Finally, the seventh stage fixes the contractual formation date and identifies the terms governing performance from that particular point onwards. Any opinion should identify the earliest communication or conduct which objectively accepted a subsisting offer and state the resulting documents in their order of precedence. Later documents should be tested as proposed variations rather than folded retrospectively into the original contract. Where no single offer can be identified, the opinion should explain whether the entire words-and-conduct analysis nevertheless establishes a contract under Wells v Devani and RTS Flexible Systems.

The final conclusion should present the strongest competing contractual route before selecting the analysis best supported by the evidence. One analysis may place formation upon return of an acknowledgement under the buyer's terms; another may place it upon delivery under the seller's last counter-offer; a third may find only a limited interim contract while liability conditions remained unsettled. The conclusion should state the evidence required to choose between those routes and the practical consequence for the disputed term.

For clarity and auditability, the resulting analysis can be organised through the following acceptance schedule:

6. Applied tutorial: purchase order, acknowledgement and mobilisation

6.1 Project record

Stonebridge Construction Ltd sought a specialist subcontractor to design, manufacture and install the glazed facade for a commercial development. On 2 March, FacadeWorks Ltd submitted a quotation for £1.18 million with a thirty-six-week programme. The quotation incorporated FacadeWorks' standard conditions, including an aggregate liability cap equal to the subcontract price, exclusion of liability for delay beyond ten per cent of that price, and payment within thirty days of application.

On 8 March, Stonebridge issued purchase order SB-417 for £1.20 million. The order incorporated Stonebridge's subcontract conditions, required completion within thirty-four weeks, imposed uncapped liability for specified design losses and provided payment within forty-five days. Its front page stated: "This order may be accepted only by signing and returning the attached acknowledgement without amendment." A later clause stated that no subcontract would become effective until the acknowledgement had been signed by both parties.

FacadeWorks received the purchase order through Stonebridge's designated electronic procurement portal during business hours on 8 March. On 9 March, its commercial manager uploaded a document headed "Order acknowledgement". The document confirmed the £1.20 million price and thirty-four-week programme but stated that acceptance was subject to FacadeWorks' quotation and standard conditions, including its liability cap and thirty-day payment period. FacadeWorks signed and uploaded its own qualified acknowledgement without signing or returning the acknowledgement form supplied by Stonebridge.

On 10 March, Stonebridge's quantity surveyor emailed that price and programme were agreed, that legal advisers were reviewing the liability position, and that FacadeWorks should begin design coordination immediately to protect the project programme. FacadeWorks replied that it would commence design "strictly on the basis of our order acknowledgement dated 9 March". Stonebridge gave FacadeWorks access to the common data environment and issued the structural model that afternoon.

FacadeWorks commenced design on 11 March and submitted its first coordination drawings on 18 March. Stonebridge's design manager reviewed the drawings, issued comments and instructed two revisions. Neither participant referred to the liability cap or payment period in the design correspondence. The design manager's appointment permitted technical coordination but excluded authority to agree price or contractual conditions.

On 22 March, a commercial meeting record stated that price, scope and programme were agreed, while liability and payment remained for director-level resolution. The record also stated that the parties intended to execute Stonebridge's subcontract. FacadeWorks corrected two technical entries in the record but did not challenge the statement that liability and payment remained unresolved.

On 31 March, FacadeWorks submitted an application for £86,000 under the thirty-day timetable in its acknowledgement. Stonebridge assessed the work at £80,000 and paid that amount thirty-eight days later. Stonebridge's payment notice expressly referred to SB-417 and the forty-five-day payment mechanism contained in its conditions. FacadeWorks accepted the payment without abandoning its contention that the thirty-day period applied.

On 12 April, Stonebridge issued a revised purchase order for the same price and programme. The revision introduced a liability cap of twice the subcontract price, retained the forty-five-day payment period and repeated the signed-acknowledgement condition. FacadeWorks replied on 14 April that it accepted the revised price and programme but could not accept liability above the subcontract price or payment later than thirty days.

Manufacture began on 20 April after Stonebridge's project director instructed FacadeWorks to release the framing package. The director wrote that the project could not wait for the lawyers and that the commercial teams would complete the subcontract later. FacadeWorks confirmed that manufacture would be released "under our quotation and acknowledgement dated 9 March". Deliveries commenced in May, Stonebridge accepted the units, and three further payments were assessed under SB-417. Neither company executed the formal subcontract or signed Stonebridge's prescribed acknowledgement at any later stage.

A subsequent delay to the manufacture and installation activities affected the contractual date stated for completion of the facade package. Stonebridge alleged that FacadeWorks accepted SB-417 through design, manufacture and payment, including Stonebridge's delay and liability provisions. FacadeWorks contended that Stonebridge accepted its 9 March counter-offer through access, instructions and payment, or alternatively that no wider subcontract arose because liability and payment remained expressly unresolved.

6.2 Assignment

Advise FacadeWorks' commercial director in a reasoned opinion containing between 1,500 and 2,000 words. Within that opinion, the following ten issues must each receive an express and reasoned answer:

1. whether FacadeWorks' 9 March acknowledgement accepted SB-417 or constituted a counter-offer;
2. the legal effect of Stonebridge's 10 March instruction and FacadeWorks' qualified reply;
3. whether design commencement, access and technical review communicated acceptance of either party's terms;
4. the effect of the signature and dual-execution provisions in SB-417;
5. whether the 22 March meeting record preserved unresolved conditions of formation;
6. the evidential value of the first application, assessment and payment;
7. whether the 12 and 14 April communications produced agreement or another counter-offer;
8. the contractual effect of the manufacture instruction, delivery and subsequent payment;
9. the authority of the quantity surveyor, design manager and project director; and
10. the date and terms of any subcontract, limited interim agreement or contract arising through conduct.

The opinion should apply Wells v Devani, RTS Flexible Systems, Gibson v Manchester City Council, Schuldenfrei v Hilton, Entores and Tekdata. It should distinguish silence from conduct and should not assume that performance establishes either party's complete set of standard terms.

6.3 Acceptance chronology

Before drafting the opinion, complete every entry in the following chronological acceptance schedule:

7. Tutor's commentary

FacadeWorks' 2 March quotation is the first apparent offer because it identifies the package, price, programme and its proposed conditions. SB-417 does not accept that offer because it changes the price, programme, payment period and liability allocation. Under the conventional analysis applied in Tekdata, SB-417 is a counter-offer on Stonebridge's conditions, subject to its express requirements concerning acknowledgement and execution.

The 9 March acknowledgement does not constitute an unqualified acceptance of SB-417 upon the terms proposed by Stonebridge. Although it confirms Stonebridge's price and programme, it reinstates FacadeWorks' liability cap and payment terms, then makes its assent conditional upon those provisions. The response therefore constitutes a further counter-offer containing the commercial terms upon which FacadeWorks was willing to proceed. Its objective effect is not altered by the heading "Order acknowledgement" or the signature placed upon FacadeWorks' own form.

Stonebridge's 10 March email provides the first substantial argument for acceptance by conduct, but the words point in competing directions. The quantity surveyor directs immediate design work and provides the information required for performance, while expressly recording that liability remains under legal review. FacadeWorks answers that it will proceed only upon the contractual basis stated in its 9 March acknowledgement. Stonebridge's subsequent access and technical coordination may therefore constitute acceptance of a limited design arrangement on FacadeWorks' stated basis, or may represent an interim request to preserve the programme pending agreement of the wider subcontract.

The signature provisions strengthen Stonebridge's argument that neither full set of terms became binding without execution. Its front-page requirement identifies an exclusive method and prohibits amendment, while the later clause requires both parties to sign. FacadeWorks did not comply with either the prescribed form or the later requirement for execution by both proposed contracting parties. Under RTS Flexible Systems, however, the parties could waive that condition through unequivocal communications and conduct. What remains is whether their conduct establishes waiver of execution for the wider subcontract or only a confined agreement covering work requested before the conditions were resolved.

In turn, the 22 March record is powerful evidence against a concluded wider subcontract at that date because it states that liability and payment remained for director-level resolution. FacadeWorks' failure to challenge that entry supports its evidential weight, although silence does not by itself accept new contractual terms under Schuldenfrei v Hilton. That record indicates that both parties continued to treat the disputed provisions as open, which makes it difficult to attribute all design performance to unconditional acceptance of either standard form.

By contrast, the first application, responsive assessment and eventual payment provide mixed evidence concerning both formation and the applicable payment machinery. FacadeWorks applies under its thirty-day timetable, Stonebridge assesses under SB-417, and payment occurs after thirty-eight days. The amount paid may establish remuneration for design work and support the existence of some contractual relationship, but it does not identify a shared payment term. Neither party's conduct unequivocally adopts the payment machinery proposed in the other party's contractual document. That payment also supplies little evidence concerning liability for design loss or delay.

Stonebridge's 12 April revision is a new counter-offer because it changes the earlier liability position while preserving the signature condition. FacadeWorks' 14 April response accepts price and programme but rejects the revised cap and payment period. That qualified response constitutes another counter-offer rather than an acceptance corresponding with the revised purchase order. At that point, the documentary exchange still contains no matched assent on liability, payment or prescribed execution.

The 20 April manufacture instruction materially changes the evidential position because Stonebridge's project director authorises a major stage of performance with knowledge that FacadeWorks relies upon its own terms. Before release, FacadeWorks repeats that reservation, after which Stonebridge accepts deliveries and administers further payments. On that basis, FacadeWorks can argue that Stonebridge accepted its counter-offer by conduct, applying Tekdata. Stonebridge will answer that the director expressly contemplated later completion of the subcontract and that the conduct was undertaken pending agreement rather than under FacadeWorks' conditions.

The contrast drawn by the Supreme Court at paragraphs 52 to 54 of RTS Flexible Systems assists Stonebridge on the no-wider-contract alternative because liability provisions remained expressly disputed while work proceeded. Conversely, the wider reasoning in RTS Flexible Systems assists FacadeWorks if the complete record shows that price, scope and programme were settled, performance became extensive, and both parties administered the transaction as contractual despite unsigned documentation. Resolution will depend upon whether liability and payment were conditions of formation or unresolved terms which the parties did not intend to prevent immediate commitment.

On the stated record, the strongest preliminary view is that the parties formed at least a limited contract for requested design work by 11 March, although its conditions require further evidence. A wider subcontract may have arisen no later than the manufacture and delivery stage, but the applicable standard terms remain contestable. FacadeWorks has a substantial last-counter-offer argument; Stonebridge has a substantial response based upon the execution condition, the 22 March record and the project director's stated expectation of later agreement.

The final opinion requires the complete portal audit, authority matrix, unredacted correspondence, meeting attendance and approval records, all payment documents, the common data environment log and evidence of previous transactions between the parties. Without those records, a categorical conclusion concerning the liability cap would exceed the evidence supplied.

8. Tutorial questions

1. Why does FacadeWorks' signed acknowledgement fail to accept SB-417 upon the terms originally issued?
2. Which communication constitutes the last documentary counter-offer before FacadeWorks commenced its design activities?
3. Can Stonebridge accept a limited design arrangement while withholding assent to the wider subcontract?
4. What wording makes the signature provisions more than a request directed towards administrative convenience?
5. Why does the 22 March meeting record carry greater weight than silence alone?
6. Which party's proposed payment machinery was objectively implemented by the first assessed payment?
7. Did the project director possess authority to waive execution or agree liability terms?
8. At what point did performance cease to be reasonably referable to a limited interim arrangement?
9. How would three previous subcontracts concluded on Stonebridge's conditions affect the Tekdata analysis?
10. Which further evidence would permit a properly concluded opinion concerning the applicable liability cap?

9. Assessment standard

An elite answer will identify the offer available at each stage, compare every purported acceptance against the complete proposed terms, distinguish silence from communicated conduct, and address the effect of prescribed execution. It will apply the battle-of-forms authorities to the actual sequence rather than assuming that the first or last document automatically prevails. Each conclusion must specify the particular project evidence which supports its stated contractual analysis.

For the formal assessment, the available marks should be allocated between the following analytical areas:

10. Authorities

1. Wells v Devani [2019] UKSC 4, particularly paragraphs 14 to 29 and 55 to 63.
2. RTS Flexible Systems Ltd v Molkerei Alois Muller GmbH & Co KG [2010] UKSC 14, particularly paragraphs 6 to 8, 45 to 56 and 81 to 89.
3. Gibson v Manchester City Council [1979] UKHL 6, particularly Lord Diplock's treatment of the alleged offer and Lord Edmund-Davies's treatment of the exploratory enquiry and absence of acceptance.
4. Schuldenfrei v Hilton (Inspector of Taxes) [1998] STC 404, particularly Neuberger J's treatment of communication and inactivity.
5. Entores Ltd v Miles Far East Corporation [1955] EWCA Civ 3; [1955] 2 QB 327, particularly pages 332 to 335.
6. Tekdata Interconnections Ltd v Amphenol Ltd [2009] EWCA Civ 1209, particularly paragraphs 14 to 32.

11. Suggested answers to the tutorial questions

These outline answers identify the legal reasoning and evidential discipline expected of an elite response. They are not model paragraphs to be reproduced, and each depends upon the facts stated in the applied tutorial at section 6.

Question 1: Why does FacadeWorks' signed acknowledgement fail to accept SB-417 upon the terms originally issued?

The 9 March document confirms Stonebridge's price of £1.20 million and its thirty-four-week programme, but it makes assent subject to FacadeWorks' quotation and standard conditions, reinstating the liability cap at the subcontract price and the thirty-day payment period. Those provisions differ from the uncapped design liability and forty-five-day payment period in SB-417, so the response does not correspond with the order as issued and proposes a different allocation of risk. On the conventional analysis applied in Tekdata, it is a further counter-offer. The prescribed method was also disregarded: SB-417 permitted acceptance only by signing and returning the attached acknowledgement without amendment, and FacadeWorks signed and uploaded its own qualified document instead. Neither the heading "Order acknowledgement" nor the signature upon it alters that objective effect.

Question 2: Which communication constitutes the last documentary counter-offer before FacadeWorks commenced its design activities?

The last documentary counter-offer was the 9 March acknowledgement, because the 10 March email from Stonebridge's quantity surveyor records agreement upon price and programme, states that legal advisers were reviewing the liability position and requests immediate design coordination without proposing revised terms. FacadeWorks' reply that it would commence design "strictly on the basis of our order acknowledgement dated 9 March" restates the existing proposal rather than advancing a new one. When Stonebridge granted access to the common data environment and issued the structural model on 10 March, FacadeWorks' 9 March acknowledgement therefore remained the subsisting counter-offer, and that access and information supply are the conduct upon which FacadeWorks relies as acceptance of it.

Question 3: Can Stonebridge accept a limited design arrangement while withholding assent to the wider subcontract?

Stonebridge can in principle accept a limited design arrangement while withholding assent to the wider subcontract. RTS Flexible Systems treats the interim arrangement and the wider contract as separate questions, each requiring its own offer, assent and identified terms. The design coordination requested on 10 March had its own confined subject matter and commercial purpose, namely protection of the project programme while liability remained under legal review. Conduct evidences agreement only to the proposal which it objectively implements, so instructing and receiving design work does not commit Stonebridge to the facade package upon FacadeWorks' conditions. Paragraphs 52 to 54 of RTS Flexible Systems supply the contrasting position where liability terms stay in dispute while requested work proceeds. FacadeWorks may contend that its express reservation supplied the terms of any limited arrangement, while Stonebridge may answer that liability remained under review and that only the immediate design instruction was agreed. The conditions of any limited contract therefore require the same objective comparison and cannot be assumed from performance alone.

Question 4: What wording makes the signature provisions more than a request directed towards administrative convenience?

Two features of the stated wording present signature as a contractual condition rather than administrative convenience. The front page states that the order "may be accepted only by signing and returning the attached acknowledgement without amendment", which identifies an exclusive route, a particular form and a prohibition upon alteration. A later clause states that no subcontract will become effective until the acknowledgement has been signed by both parties, which presents execution as a condition of legal effectiveness rather than a step in project administration. Wording of that kind is to be distinguished from an instruction to sign and return a copy for the file, which regulates procedure without withholding commitment. Under RTS Flexible Systems, even a condition expressed in those terms may afterwards be waived by unequivocal conduct, so the provisions are a starting point for the analysis rather than its conclusion.

Question 5: Why does the 22 March meeting record carry greater weight than silence alone?

The record is a contemporaneous document of the parties' dealings which states that price, scope and programme were agreed while liability and payment remained for director-level resolution, and that the parties intended to execute Stonebridge's subcontract. FacadeWorks corrected two technical entries, which proves that it read the record and gives the uncorrected entries evidential weight, although the legal effect remains open to argument. That engagement differs from the inactivity considered in Schuldenfrei v Hilton, where the taxpayer relied upon his failure to respond as part of an alleged agreement. The distinction must be preserved: the record is evidence of the state of negotiations at that date, but neither the document nor the failure to correct every entry constitutes acceptance of a disputed term.

Question 6: Which party's proposed payment machinery was objectively implemented by the first assessed payment?

Neither party's proposed payment machinery was objectively implemented by the first assessed payment. FacadeWorks applied for £86,000 under the thirty-day timetable in its acknowledgement, Stonebridge assessed £80,000 and issued a payment notice referring to SB-417 and its forty-five-day mechanism, and payment followed after thirty-eight days, which matches no proposed period. The transaction supports the existence of some contractual relationship covering the design work and fixes the value assessed for it, but the conduct of each party remains referable to its own document, so no shared payment term can be extracted from it. FacadeWorks' receipt of the money while maintaining its contention upon the thirty-day period keeps that position open. The payment provides no evidence at all upon the liability cap, which is a separate term requiring its own analysis.

Question 7: Did the project director possess authority to waive execution or agree liability terms?

The record does not answer the question, and the opinion should say so. Workshop facts state the design manager's limits, namely technical coordination without authority upon price or contractual conditions, and show the quantity surveyor communicating upon price and programme, but they state nothing about the project director's mandate. Authority to release a manufacturing package is not the same as authority to waive a dual-execution condition or to settle the cap, and the two should be addressed separately. His written explanation that the project could not wait for the lawyers and that the commercial teams would complete the subcontract later suggests he was not purporting to conclude the disputed terms. The delegated authority matrix, his appointment terms, any board resolution and the parties' previous dealings would be required, together with every representation concerning his contractual mandate which Stonebridge communicated to FacadeWorks.

Question 8: At what point did performance cease to be reasonably referable to a limited interim arrangement?

The strongest candidate is 20 April, when the project director instructed release of the framing package. Until then the performance was design coordination requested on 10 March for a stated programme purpose, which an interim arrangement explains. Manufacture of the framing package, the May deliveries, Stonebridge's acceptance of the units and three further assessments under SB-417 amount to performance of the package itself, and RTS Flexible Systems shows that performance and contractual administration on that scale may establish a wider contract and waive an execution condition. Two matters pull against fixing the date there: the director expressly contemplated later completion of the subcontract, and the liability position remained disputed after the exchanges of 12 and 14 April, which resembles the contrast drawn at paragraphs 52 to 54 of RTS Flexible Systems. The date cannot be settled without the complete correspondence and payment record.

Question 9: How would three previous subcontracts concluded on Stonebridge's conditions affect the Tekdata analysis?

They would support a course-of-dealing argument of the kind considered in Tekdata, but the documents and conduct must prove a different objective intention from the conventional sequence. Stonebridge would have to produce the complete orders, acknowledgements and correspondence for all three transactions and show that FacadeWorks knew the conditions and contracted upon them consistently, since commercial familiarity proves nothing by itself. Any established practice must then be weighed against the communications in this transaction, including FacadeWorks' repeated reservation of its own conditions on 9 March, 10 March, 14 April and release of manufacture. The three earlier subcontracts would therefore form part of the objective factual inquiry without deciding whether the 9 March counter-offer governed this transaction.

Question 10: Which further evidence would permit a properly concluded opinion concerning the applicable liability cap?

The portal audit showing each document uploaded, its version, the time of receipt and the user account employed; the common data environment log recording access and issue of the structural model; the delegated authority matrix and appointment terms for the quantity surveyor, the design manager and the project director, with any board resolution relied upon; the unredacted correspondence, including internal instructions upon the liability review; the attendance list, circulation and approval record for the 22 March meeting; every application, payment notice, assessment and remittance advice; the complete orders and acknowledgements for any earlier subcontracts between the parties; and the records connecting the delay to the contractual date for completion of the facade package. Until those records are examined, a categorical opinion upon the cap would exceed the evidence available.

Scope of the lesson

This lesson addresses contractual acceptance under English law in the particular settings of construction procurement, electronic messages, early performance and competing forms. Its analytical method is intended for education and should not be treated as advice upon an existing dispute. Any such advice requires examination of the complete contractual record, the applicable law, the parties' authority arrangements and the evidence surrounding performance.