10 examples of legal contracts, and the clause in each that bites

1. Service agreement

Use it when a client approves work that unfolds over time: an agency running social for a SaaS startup, a consultant doing a three-month review, a freelance designer producing mockups. Its job is to turn an informal promise into working instructions covering scope, deliverables, timelines, payment, termination and who's responsible for what.

The failure is vague scope. "Support with marketing" can mean campaign management, copywriting, ad setup and weekly reporting to the client, and content posting only to the agency. Name each output in plain language, then require written approval for additions. That change-order step protects the client from surprise charges and the provider from unpaid work.

The clauses to slow down on:

• Deliverables: number, format and deadline for each output.
• Acceptance: the sign-off method, the review period, and what happens when feedback is late.
• Ownership: who gets the intellectual property, and whether the provider can reuse their own tools and templates.
• Scope changes: written confirmation of added work, revised fees or new deadlines before the work starts.

how to share a contract securely

Before sharing the draft, test one example against it. Could both sides identify the requested output, the approval point, the price and the consequence of a delay without relying on a private conversation? If not, fix the wording before anyone signs.

2. Non-disclosure agreement

An NDA fits when the conversation has value but the information shouldn't travel: a startup sharing projections with investors, a software company showing proprietary logic to a possible acquirer, a founder handing a contractor the client list. If you want the plain-language definition first, what an NDA is covers the basics. It's narrower than most people assume. It governs disclosure, not competition.

The drafting trap is trying to guard every idea forever. That makes the document harder to use and easier to resist. A better version names the confidential material, excludes anything already public or independently known, and sets a term that matches the deal.

An NDA is a filter, not a fortress. If the real risk is someone taking your concept and building a rival, the NDA alone won't solve that.

How you send it matters too. If it's going to investors or a potential buyer, use a method that limits who can get at it.

sending signed documents via email

3. Employment contract

This is the document that turns a job offer into a working relationship with obligations on both sides. In the UK, contract terms can come from more than the signed paper: an offer letter, the staff handbook, verbal agreements, collective agreements and terms implied by law all count, according to the government's guidance on employment contracts. That's exactly why the written version matters. It pulls the moving parts into one place before work starts.

The failures show up later. Founders agree role and pay, then leave equity, confidentiality, remote work and notice in email threads. The hire starts, the team grows or someone leaves, and nobody can agree what was promised. Both sides have to stick to the contract until it ends, by notice or dismissal, as GOV.UK's overview of employment contracts puts it, which makes the termination wording more than admin.

Watch these closely: role and duties in practical terms rather than a title, compensation including bonus logic and any equity, notice periods and probation, confidentiality tied to actual company data, and device and data handling for anyone working remotely. Once it's signed, send the executed copy properly. Some jurisdictions make that a duty: in Hong Kong, for example, the Labour Department's guidance on written contracts says the employer must give the employee a copy immediately after it's signed. Wherever you are, the handling matters.

4. Independent contractor agreement

The independent contractor agreement keeps a freelance relationship from sliding into employment. An agency hiring a video editor for a campaign, a SaaS company bringing in a developer for a sprint, a firm engaging a researcher for a project. The contract should make one thing plain: the contractor controls how the work gets done, and the client controls the result.

That split is where it goes wrong. Spell out hours, methods and day-to-day supervision too tightly and the relationship starts to look like employment. Leave the deliverables vague and nobody can agree whether the work is finished.

Keep the scope tied to output, with acceptance criteria that say what counts as complete, a fixed fee or milestones rather than open-ended hourly drift, an IP assignment that confirms who owns the finished work, and a status clause that says the person is not an employee.

The status clause only holds if the workflow matches it. If the contract says contractor and the company manages the person like staff, the paper won't save you.

5. Purchase agreement

A purchase agreement turns a sale into a closing. A developer selling a commercial building with financing and inspection conditions, a manufacturer selling equipment on instalments, a founder selling a company with an earn-out. Its job is to lock down price, payment terms, delivery or closing mechanics, condition, warranties and contingencies.

The risk sits in the handoff. The buyer wants clean title, no liens and an asset that matches the description. The seller wants to know when the money arrives and what happens if the buyer misses closing. If the remedies are vague, both sides end up arguing over the gap.

Be explicit about condition and disclosed defects, the payment schedule (deposit, final payment, method), contingency deadlines for inspection or financing, title and the seller's right to sell, and what happens if either side fails to close. A purchase agreement should read like a closing checklist. If it reads like a brochure, it's leaving room for a dispute.

6. Lease agreement

A lease becomes an operating document the moment a business commits to premises. A startup in an office, a professional firm in a serviced suite and a retailer paying percentage rent face different risks under the same document title. Define the property, rent, term, maintenance, use restrictions, deposit and termination in terms that match the business.

The expensive disputes usually begin with one word: maintenance. If the lease doesn't separate structural repairs, building systems, fixtures and tenant damage, each side reads the allocation differently, and a repair argument can interrupt trading as well as cost money.

Before signing, check the repair split, the rent-increase method, the deposit deductions and what counts as wear and tear, the break clause and its notice period, and the end-of-lease obligations on fixtures and alterations. A practical lease answers who pays, who repairs, who can end it and what the tenant hands back. If it doesn't, it has postponed the negotiation rather than completed it.

7. Partnership agreement

collaboration agreement template

A partnership agreement matters the moment a business moves from loose collaboration to shared risk: two consultants forming a firm, three co-founders dividing equity, a senior hire buying into a practice. It should pin down capital contributions, profit and loss sharing, management duties, decision-making, dispute resolution and buy-sell rights.

The weak point is optimism. Partners assume trust will cover the hard parts, then discover they never agreed on cash calls, veto rights or what happens when one person wants out. A good draft answers those before money and control are on the line.

Contributions should cover time, equipment and client relationships as well as cash, and say whether later contributions change ownership. Decision thresholds need real boundaries: majority for most things, a higher bar for debt, hiring and admitting new partners. Exit terms need buyout formulas and what happens after a deadlock. If the group is still working out how it operates, a collaboration agreement can be the lighter document to start with.

8. Licensing agreement

A licensing agreement gives someone the right to use intellectual property on terms the owner controls. A software company licensing a platform to resellers in a territory, a patent holder licensing manufacturing rights for royalties, a brand licensing a trademark for a product line.

The deal lives or dies on scope, territory, exclusivity, royalties, duration and quality control. Get the scope wrong and the licensee uses more than you meant to allow. Make it too tight and they can't sell the product properly. Leave out quality standards and a trademark licence turns into brand damage.

One clause can shift the whole economics: exclusivity. The licensee usually wants it. The owner may need room to work with other channels or regions. Royalty language deserves the same attention, and if payment depends on usage, the agreement needs audit rights and a clear way to verify the numbers.

9. Investor term sheet

Founders treat the term sheet as a celebration document. It's really the blueprint for the financing negotiation. A seed convertible note, a Series A, a growth round with lead-investor governance rights: each sets expectations on investment amount, valuation, security type, governance and liquidation preference. Many provisions are non-binding. That doesn't make them harmless.

Start with the terms that can change control or future returns. A strong headline valuation can hide an aggressive preference stack, anti-dilution protection or investor approval rights, and those decide who controls key decisions, how exit proceeds are divided and how hard the next round will be.

Before signing, ask whether the valuation reflects the ownership actually being sold, how the liquidation preference changes everyone's exit proceeds, which control rights cover board seats and vetoes, how the terms affect future dilution, and which closing conditions have to be met before the money arrives. If a co-founder can't explain a term's practical effect in plain English, the term sheet isn't settled yet.

10. Non-compete and non-solicitation agreement

A departing salesperson taking key accounts, a partner approaching former clients, an engineer joining a direct competitor. These agreements limit competition or contact with named clients, prospects or employees for a defined period and area.

The two aren't equally practical. A targeted non-solicitation clause is usually easier to defend than a broad non-compete, because it protects identified relationships without stopping someone earning a living. The trade-off is narrower protection.

Test the clause against the actual departure scenario: the shortest duration that serves the purpose, geography limited to where the relationship exists, protected contacts defined precisely, the legitimate interest written down, and the governing law checked before relying on it. A clause that reads like punishment is probably too broad to survive. Enforceability varies a lot by jurisdiction, which is one of the places a lawyer earns their fee.

The ten side by side

Pick the document that fits the deal, then explain it

Work backwards from the relationship. Identify who's doing what, what's being exchanged, who owns the output and carries the risk, then set payment, duration and exit terms. If the relationship is simple, keep the contract simple. If it touches equity, IP, property, regulated data or another country, slow down and get proper advice before anyone signs.

The part I'd add from experience is that the other side rarely rejects the deal. They stall on one clause, one deadline or one consequence they didn't understand, and they don't always say which. That's why I'd send an agreement with a short walkthrough of the terms that matter rather than a bare PDF. LiveDocument lets you record that walkthrough over the contract, share it as one link, and see which pages held attention. It doesn't do e-signature, it's not a data room and there's no watermarking, so the signing still happens wherever it happens today.

If you do track a contract that way, treat the viewer data as personal data. Tell the recipient the link is tracked, keep the analytics inside the team that needs them, don't keep viewer records once the deal is decided, and check your own client agreements and privacy notice first. What document tracking can and can't tell you matters here too.

One final rule. If you can't explain the clauses that control scope, money, ownership and exit in plain language, the agreement isn't ready. The paper should make the deal easier to run, not harder to remember.

hire remote legal assistants

I built LiveDocument because I got tired of sending documents that mattered into inboxes and hearing nothing back. If that's a feeling you know, it's at livedocument.com.