QScope

Reports

Is an email agreement legally binding on a building job?

The client never signed anything, but there is an email thread: your quote, some haggling, and “great, when can you start”. That thread is very probably a contract, and the practical question is not whether email binds, it does, but whether it bound the terms you wanted.

QScope Team·5 March 2026·4 min read

Start with the general law, because it is simpler than people expect: a contract needs offer, acceptance, consideration and intention, and for building work it does not need any particular form. Ink, email, text messages, a phone call, or starting work after a quote, all of it can make a contract. Email is not a lesser way of agreeing; it is agreeing, with a built-in record.

The good news half

Your quote sent by email, and the client’s “yes, go ahead”, generally makes your quote’s terms the contract, which is precisely why the quote deserves to be written properly: the nine things in it become binding through one cheerful reply. The same machinery works mid-job: an email varying the scope, confirming the small extra with a price, or recording what was agreed on site, binds too, with a timestamp neither side can argue with. And a point worth knowing since the law changed in 2011: the Construction Act’s machinery applies to construction contracts whether written, emailed or purely oral, so an email-formed contract on a business job carries the full payment regime, notified sums and all.

The bad news half, and it is the same half

Everything above cuts both ways. The reply dashed off from the van binds like the letter you drafted twice. The usual self-inflicted wounds:

  • Accepting a counter-offer without noticing. “Yes but £38k and done by August” followed by your “ok” is a contract at £38k and August, not at your quote. The last shot before acceptance usually wins, so read what you are saying ok to.
  • Agreeing scope in fragments. A contract assembled from forty messages has terms scattered across forty messages, findable, but arguably inconsistent. When a thread converges, one consolidating email, “so we are agreed: [scope], [price], [stages], [start]”, turns the archaeology into a page.
  • The accidental promise. “Should be done by end of June” in a chatty reply can be read as a term. If a date is an estimate, write the word estimate.
Treat every email to a client as being read aloud, later, to someone deciding who owes whom money, because that is one of its possible futures. The habit is not writing less, it is writing one degree more deliberately: numbers explicit, estimates labelled, agreements consolidated.

Subject to contract, letters of intent, and other half-measures

If you genuinely do not want the thread to bind yet, say so in it: “subject to contract” while the real terms are being drawn keeps negotiation from hardening early. And if the client wants you started before anything is settled, that is the neighbouring, messier situation, work started with nothing signed, which has its own page and its own risks. On a homeowner job everything here works identically, contract formation is general law, not Construction Act machinery, with one addition: against a consumer, ambiguity in terms you drafted is read against you, so the consolidating email matters most exactly there (section 106 having removed the statutory net underneath).

What to do this week

1. On the live job, find the thread that is the contract and save it somewhere findable, with the quote it accepted.

2. If the agreement lives in fragments, send the consolidating email now, framed as housekeeping: “pulling it into one place so we both have it”.

3. Add the two labels to your writing habits: “estimate” on dates and sums that are estimates, “subject to contract” on negotiations that should not bind yet.

Where the information stops

Whether a particular messy thread did form a contract, and on which terms, is exactly the kind of question that fills the first day of a hearing, and if serious money now turns on what a thread meant, that is a question to put to a professional with the whole thread in front of them, not one to answer from a page of principles.

Keep reading

Related