How to Write a Service Agreement: A One-Page Structure That Covers You

A service agreement is a contract between someone providing services and the client buying them. It needs nine things: the parties, the services, deliverables and acceptance, price and payment, timeline, revisions and changes, intellectual property, liability and termination, and signatures.

The good news is that seven of those nine are stable. Write them once, reuse them forever. Only the scope, the price, and the timeline change between clients — which is why a service agreement should take five minutes to produce, not an afternoon.

1. The parties and the relationship

Full legal names and addresses for both sides. If you trade through an LLC or corporation, the contracting party is the entity, and you sign in your capacity as its officer — not personally.

Then state the relationship explicitly:

This clause is not decorative. Misclassification is a live issue for both sides, and while a contract clause does not by itself determine status, its absence is conspicuous. What determines status is the substance of the arrangement — who controls how, when, and where the work is done, who supplies the tools, and whether the worker is free to serve other clients — not the label the contract uses.

2. Scope of services

The section that prevents the most disputes, written badly more often than any other. Two rules: be specific, and list exclusions.

3. Deliverables and acceptance

Say what the client receives, in what format, and how it gets approved. Acceptance criteria are how projects end.

• The specific deliverables and their file formats
• How they are delivered — shared drive, file transfer, printed
• A review window: the client has n business days to accept or request revisions
• Deemed acceptance: if no response within the window, the deliverable is accepted

That last item is what stops a project hanging open indefinitely because a client went quiet. Without it, "not yet approved" can persist for months and the final invoice never becomes due.

4. Price and payment

State the fee and the model — fixed, hourly, day rate, retainer, or per deliverable. Then the mechanics:

• Deposit required before work begins, and whether it is non-refundable
• Milestone or monthly payment points
• Payment window — net 7 or net 14 is entirely normal for services
• Late fee, expressed as a monthly rate, with the "or the maximum permitted by law" qualifier
• The right to suspend work on non-payment after written notice
• Whether expenses are included, and how any pass-through costs are approved

For retainers, be explicit about what happens to unused hours. "Unused hours do not roll over" is a legitimate term — but it must be written, or the client will reasonably assume they do.

5. Timeline and client responsibilities

Give dates, then protect them. Most service projects run late because the client is late — with content, feedback, access, or decisions.

The second sentence protects your calendar. The third protects your cash flow — without it, a stalled project means work delivered and no invoice due.

List client responsibilities explicitly: brand assets, copy, site access, logins, a named decision-maker, and timely feedback.

6. Revisions and changes

The single most valuable clause for creative and design work.

The definition of "a round" matters as much as the number. Without it, five separate emails over three days count as one round in the client's mind and five in yours.

For anything with a project structure — a build, a multi-phase engagement — use the same discipline contractors use for change orders: price it, put it in writing, get it agreed before starting.

7. Intellectual property

The clause creative freelancers most often get wrong, in a way that only surfaces when a client stops paying.

Three distinct protections there:

• Transfer on payment, not delivery. If they do not pay, they do not own it — and using it becomes infringement, which is a much stronger position than a debt claim.
• Pre-existing materials stay yours. Your templates, presets, code libraries, and frameworks should not transfer with every project.
• Portfolio rights. Easy to forget, painful to lose. Without it, your best work may be unusable in your own marketing.

8. Liability, warranties, and termination

Three things belong here.

Limitation of liability

Cap your total liability at the fees paid under the agreement, and exclude indirect and consequential losses — lost profits, lost data, business interruption. Courts do not enforce every limitation, and some cannot be limited at all, but an uncapped exposure on a $3,000 project is not a risk worth carrying.

Warranties

Warrant that you will perform with reasonable skill and care. Do not warrant outcomes you cannot control — rankings, sales, engagement, or approval by a third party.

Termination and the kill fee

That final clause — a kill fee — reflects a real cost. When you block out three weeks for a project, you turn down other work. Cancellation on day two does not give those weeks back.

9. The boilerplate

Short, standard, and worth having:

• Governing law and venue — your state and county where you can negotiate it
• Entire agreement — this document supersedes prior discussions
• Amendments in writing — no verbal variations
• Confidentiality — mutual, with a defined duration
• Force majeure — events genuinely outside either party's control
• Assignment — neither party assigns without consent
• Severability — one unenforceable clause does not void the rest
• Notices — how formal notice is given, and to which address

The one-page version

For small engagements, all of this compresses. A genuinely useful one-page agreement contains:

That fits on one page and covers the situations that actually arise. Everything beyond it is refinement, and refinement can wait until a project justifies it.