Service Agreements: What They Must Include

A service agreement is the contract between someone providing work and someone paying for it. At minimum it must say what work is being done, what it costs and when payment is due, how long the arrangement lasts and how either side ends it, and who carries which risk when something goes wrong. Everything else is refinement of those four answers.

It is the most-signed business contract there is, and the most casually signed. Most service disputes are not about bad faith — they are about two people who each believed a different thing was included, and a document too vague to settle it.

What a service agreement has to cover

• The parties — the actual legal entities, not trading names. If you contract through a company, sign as the company.
• The services — what is being delivered, in enough detail that a stranger could tell whether it was done.
• The price and what triggers it — a fixed fee, a rate, a milestone schedule. Say what is included and what is billed separately.
• Payment terms — when invoices go out, how many days to pay, what happens when payment is late.
• Term and termination — how long it runs, whether it renews, and how either side can end it.
• Client responsibilities — the access, information, approvals or materials the provider needs, and what happens when they are late.
• Change process — how extra work gets agreed and priced before it is done.
• Ownership — who owns the work product, and when ownership transfers.
• Liability and indemnity — the ceiling on what each side can owe, and who defends whom.
• Insurance, confidentiality, and how disputes get resolved.

What to look for before you sign

• Is the scope specific enough to prove? "Marketing support" is not a scope. "Two blog posts and one email campaign per month" is.
• Are payment days counted from the invoice date or from the client's approval? Approval-triggered clocks can run indefinitely.
• Is there a cap on liability, and does the cap have exceptions that swallow it?
• Does termination for convenience exist, and does the party terminating owe anything for work already done?
• Who owns the work if the client stops paying part-way through?
• Does the change-order process require writing? If so, actually follow it — an email trail that matches the contract is worth more than a good memory.
• Where would a dispute be heard, and under whose law?
• Are there auto-renewal terms with a notice window you would have to diary now?

The four clauses that cause disputes

Scope, and what counts as extra

Almost every service argument starts here. The provider believes a request is new work; the client believes it was always implied. The fix is not longer scope language — it is a named change process: any work outside the written scope gets a written change order with its own price and time impact, agreed before the work starts. Then the argument becomes a question of fact rather than a question of memory.

Payment timing and late payment

Payment terms decide who is financing the work. Net-30 means the provider carries a month of cost. Terms that begin on "acceptance" rather than on invoice hand the client control of the clock. Look for a defined acceptance window — if the client does not object within a set number of days, the work is accepted — plus a stated remedy for late payment, such as interest and the right to pause work. A remedy nobody wants to use still changes behavior.

Limitation of liability

This clause caps what one side can be made to pay if things go badly, often at the fees paid under the agreement, and usually excludes indirect losses like lost profits. It is not sharp practice — it is how a small provider takes on a large client without betting the business on one job. Read what the cap excludes. A cap of fees paid "except for breaches of confidentiality, indemnity obligations, and gross negligence" can leave more uncapped than capped, depending on the work.

Indemnification

An indemnity is a promise to cover someone else's losses, and typically to defend them against a third-party claim. In a fair service agreement it is mutual and tied to fault: each side covers claims arising from its own work, its own materials, or its own breach. The version to slow down on is a broad one-way indemnity that makes the provider responsible for any claim "arising out of or relating to" the services regardless of who caused it. That is a much larger promise than it looks, and it usually sits outside the liability cap.

A practical way to work

1. Negotiate the legal terms once, in a service agreement you reuse.
2. Attach a short statement of work per job, with deliverables, dates and price.
3. Handle every change as a written change order, however small.
4. Keep the signed versions where you can find them — the version that matters in a dispute is the one you can produce.

None of this requires a long contract. A clear four-page service agreement beats a twenty-page one nobody read. The test is simple: could someone who was not in the room read this and tell what was promised, what it costs, and who carries the risk? If yes, the document is doing its job. This guide is general information, not legal advice, and specifics vary by state and situation.