Agreed the deal by email? Turn the thread into a contract
Pull every agreed point out of the email thread, map each one to a clause, fill the gaps emails leave, and send one document to sign.
Read the thread from first email to last, list every point you both agreed, and keep only the latest version of each. Put each point in the clause it belongs in, then fill the gaps emails leave, such as late payment, ownership and how the deal ends. Send one document for both sides to sign, with a note listing what the thread never covered.
Is the email thread already a contract?
An email thread can sometimes be a binding contract, but don't rely on it. Whether it is depends on the law that applies and on the usual rules for forming a contract.
In the US, the federal ESIGN Act covers transactions in or affecting interstate or foreign commerce. For those, a contract can't be denied legal effect solely because an electronic record was used to form it. That removes one objection only. The Act has exceptions, such as wills and family law. It doesn't require anyone to use electronic records.
In England and Wales, the Law Commission's 2019 report describes Green v Ireland, a 2011 case about a land deal. The court held a chain of emails wasn't a contract. They set no binding terms, and suggested a formal contract would follow. The same report notes that a name typed at the end of an email can count as a signature where the law requires one. The sender must mean it to authenticate the document.
Even when a thread does count, its terms may sit across many emails and can be read more than one way. A clear document both sides sign cuts that risk.
What do you actually have in the thread?
A deal agreed by email usually arrives as a thread, not a list of terms, with three kinds of point mixed together:
- Agreed: "Yes, $8,400 works."
- Half-agreed: "Should be fine," "let me check with finance."
- Changed later: the price in the second email, replaced by a new one in the ninth.
Replies quote earlier emails, so the old price can sit right below the new one. Drafting is the first stage in how a contract deal runs; here, most of it is already in the thread.
How do you turn the thread into a contract?
To turn an email thread into a contract, work through it in this order:
- Gather everything. Include side threads, forwarded emails, any quote you sent and notes from calls. Sort it oldest first.
- List every point. Copy each one into a document or spreadsheet, with the date and who said it.
- Keep the latest version. Where a point changed, the last message both sides accepted usually governs. Strike out the earlier versions.
- Flag the half-agreed points. "Should be fine" is unclear, so ask for a plain yes. Put these in [brackets] meanwhile.
- Place each point in its clause. Use the table below, and start from your usual contract if you have one.
- Fill the gaps. Add the terms the thread never covered, written as proposals.
- Swap vague words for numbers. "Roughly," "ASAP" and "when it's done" become dates, amounts and named events. Anything firmer than the thread is a proposal too.
- Send one document, with a short email that lists what you added or firmed up.
Which clause does each email line belong in?
Most lines in a deal thread map to one clause. The right-hand column is what the email usually leaves open.
| What the email says | Clause | What to pin down |
|---|---|---|
| "$8,400 for the seven pages" | Fees | Fixed fee or estimate; what it covers; whether tax and expenses are extra |
| "Half up front, the rest when it's done" | Payment | Each amount, the event that triggers it, and how many days they have to pay |
| "Live by the end of April" | Timeline | A date, and what it depends on, such as content or feedback from them |
| "Two rounds of changes" | Revisions | What counts as a round, whether it's per page or for the whole job, and the price of a third |
| "Once we're happy with it" | Approval | Who approves, how, and how long they have to reply |
| "You'll hand over all the files" | Ownership | What transfers and when, such as on full payment; what you keep, such as your own tools |
| "Can you also do the newsletter?" | Changes to the work | A price and a written yes from both sides before work starts |
Australia's business.gov.au gives the same advice for changes: both sides agree, in writing.
What does the thread usually leave out?
Deal emails often focus on the price, the work and the date, and skip what happens when something goes wrong. Check for these six:
- When payment is due. "The rest when it's done" leaves "done" and the payment period unclear. Name the event and a number of days after the invoice, such as 14.
- What happens if they pay late. Decide whether you pause work, charge a late fee where the law allows one, or both.
- What extra revisions cost. "Two rounds" says nothing about round three. Set a rate, and say you'll confirm before starting.
- When ownership passes. Handing over files isn't the same as transferring copyright, which in the US takes a signed writing. Say what rights transfer, and when, for example once they've paid in full.
- Who signs off the work. Name the person who approves, and say what happens if they don't reply.
- How either side can end it. Australia's business.gov.au suggests covering when it applies, the notice each side gives, and what money is payable.
Flag each new term when you send the draft, so nothing looks slipped in:
“Hi [Name], Attached is the draft agreement for [project]. It follows what we agreed by email, including the changes from [date]: [seven pages, $8,400, launch on April 24]. Our emails didn't cover a few points, so I've proposed terms for them: 1. Payment: I invoice the balance when the site is ready to launch, due within [14] days. 2. Late payment: if an invoice is more than [15] days overdue, work pauses until it's paid. 3. Extra revisions: rounds beyond the two included are billed at $[95] an hour. 4. Ownership: copyright in the original designs I create for the site is assigned to you once the fee is paid in full. I keep my own tools and templates, and you may use any that are in the site. 5. Ending early: either of us can end the agreement with [10] days' written notice, and work done to that date is paid. 6. Firmer terms: first designs within 14 days of the deposit; work counts as approved if no comments arrive within [3] business days; April 24 holds if you sign and pay the deposit by [March 13], and any delay on your side moves it by the same number of days. Could you confirm each of these, or mark up any that don't work? Best, [Your name]”
What does a thread look like once it's written as clauses?
Here is a made-up thread between Quillmere Studio, a web designer, and its client Vantelle Ceramics:
- March 2, Noor Aldaine at Vantelle: "We'd love the new site live by roughly the end of April. Budget is $7,200 for the six pages. Can we do half up front and the rest when it's done?"
- March 3, you: "That works. The price includes two rounds of changes, and I'll try to get first designs to you within two weeks of the deposit."
- March 9, Noor: "Could we add a stockists page? And we'd like to launch on April 24 for our spring sale."
- March 10, you: "Yes to both. Seven pages comes to $8,400. For the 24th, I'll need your photos and copy by March 27."
- March 10, Noor: "Perfect, go ahead."
Drafting from the March 2 email would give the wrong fee, page count and date. The clauses below use the latest version of each point. Bracketed text is new or firmer than the thread, so list it in your cover email as a proposal.
“Fees and payment. Client will pay Provider a fixed fee of $8,400 for the seven pages listed in Schedule A. Client will pay 50% ($4,200) on signing, and work starts when that payment arrives. Provider will invoice the remaining $4,200 when the site is ready to launch, and Client will pay it within [14] days of the invoice date.”
“Timeline. Provider will deliver first designs [within 14 days] after receiving the deposit. Client will provide all photos and copy by March 27. Provider will have the site ready to launch on April 24, provided Client signs and pays the deposit by [March 13], supplies that material on time and returns feedback on each round within [3] business days. [Any delay by Client moves the launch date by the same number of days.]”
“Revisions and approval. The fee includes two rounds of changes to the designs. A round is one set of written comments from Client, sent together. Further rounds are billed at $[95] per hour, and Provider will confirm the estimate in writing before starting. Noor Aldaine approves the work for Client. [Work counts as approved if Client sends no written comments within 3 business days of receiving it.]”
What mistakes happen when you draft from email?
Three mistakes are easy to make when you draft from email.
| Mistake | What happens | How to avoid it |
|---|---|---|
| Drafting from the first email | The fee, pages or dates are ones the client already changed | Read to the last email first. For each point, use the latest message both sides accepted |
| Copying vague words | "Roughly the end of April" and "we'll try" become terms nobody can measure | Replace each with a date, a number or a named event, such as "at launch" |
| Writing "as agreed in our emails" | The contract points back to the thread, and the two can conflict | Put every term in the document. Name any attachment by title and date |
When should you get a lawyer?
A short, clear thread for routine work usually doesn't need a lawyer. Get one when:
- The other side says the emails already bind you, on terms you don't accept.
- The thread includes terms you don't fully understand, such as exclusivity, a non-compete, or how rights in your work are assigned or licensed.
- The deal is large for your business, such as several months of revenue.
- The other side is in another country, or wants its own law to apply.
When does drafting from a thread by hand stop working?
Working through a thread by hand is fine for a few weeks of emails between two people. It starts to slip when the thread runs long and several people chime in. It also slips when the deal changed across many emails, or when you draft for several clients a month. Past that point, it's worth handing the first draft to a tool, so your time goes on checking it.
DealMate is an AI contract assistant that takes a deal from first draft to final: describe the deal in a sentence and get a draft built from your templates and clauses; when they send their template, review it from your side and see what's risky; when their redlines come back, compare the versions and see every change and the risk it carries.
Sources
- 15 U.S.C. §7001 (ESIGN Act): General rule of validity — US Government Publishing Office
- 15 U.S.C. §7003: Specific exceptions (ESIGN Act) — US Government Publishing Office
- Electronic execution of documents (Law Com No 386) — Law Commission (England and Wales)
- Prepare a contract — business.gov.au (Australian Government)
- 17 U.S.C. Chapter 2: Copyright ownership and transfer (§§201–205) — US Copyright Office
This is general information, not legal advice. For high-stakes or unusual terms, talk to a lawyer.
Need to send the first draft? Describe the deal in a sentence or paste the email thread, and DealMate drafts a contract from your templates and clauses, ready to edit and send.
Try it on your next contractFree trial · no card needed