Simple Service Agreement: 10 Things Every Contract Should Cover

A friendly email and a good feeling can start a project, but they cannot settle what happens when an invoice ages, a client goes quiet, or the scope quietly doubles. That is the job of a simple service agreement: one short document, signed before work begins, written in plain language rather than law-school vocabulary.

The ten things it should cover: named parties and dates, a real services description, client responsibilities, a payment amount and schedule, a late fee, revision rounds, intellectual property terms, confidentiality, a termination notice with a kill fee, and a liability cap plus a governing state. Each one answers a question that eventually gets asked out loud.

This guide walks through those ten items section by section, and each one maps to a field or section in the free business contract template generator on Toolfyra, so you can turn the checklist into a signing-ready draft the same afternoon.

CHAPTER 01Start With Parties, Dates and a Real Services Description

Every agreement opens with names, and the wording matters more than it looks. Use each side's full legal identity: the name on your invoice and the name on their checks, not the brand on a business card. A studio that trades as Bright Pixel but files taxes as Bright Pixel Studio LLC should be named the second way, because that is the entity that can enforce the contract and receive payment. Add addresses and a line confirming who is authorized to sign for a company client.

Dates come next: a start date and either an end date or the word ongoing. A fixed term gives both sides a natural checkpoint to renew, renegotiate or part ways, while an ongoing arrangement suits retainers and support work. The template generator accepts either, and the choice affects nothing else in the document, which is exactly how flexible this section should be. Whatever you pick, avoid a contract with no stated term at all.

The services description is where most disputes are born, so write it as deliverables with limits and exclusions: design and build a five-page marketing website, including copy polish, responsive layout and a launch checklist, excluding paid advertising, copywriting from scratch and post-launch maintenance. That single sentence, lifted from the generator's own example field, tells the client what they get and, just as usefully, what they do not. Two minutes of exclusion-writing here prevents two months of unpaid extra work later.

CHAPTER 02Client Responsibilities: The Section Everyone Skips

A project is a two-person sport, and the second section worth adding says so. List what the client must supply and by when: final copy, product photos, brand files, access to a hosting account, a named approver who can actually make decisions. When the deliverable depends on inputs you do not control, the contract should say the timeline pauses while you wait. Without that line, a three-week silence on the client's side still shows up as a delay on yours.

This section also quietly protects the relationship. Instead of an awkward email explaining that the missed deadline was their fault, you point to a clause both parties signed: materials were due on the tenth, they arrived on the twenty-fourth, so the launch moves with them. Clients accept this framing easily because it applies to them the same courtesy it applies to you, and projects run better when waiting is nobody's fault.

CHAPTER 03Payment: Amount, Schedule and the Late Fee Behind It

State the fee as a number, then attach a schedule. The common patterns are payment on completion, a 50-50 split with half due to start and half on delivery, or a monthly retainer for ongoing work. On-completion suits short jobs with trusting repeat clients; milestones suit anything longer than a few weeks; retainers suit steady monthly capacity. The template generator offers all three as a dropdown, because the right answer depends on the deal, not on a rule.

Whatever schedule you choose, connect it to acceptance. Delivery and acceptance are different events: you deliver the website, the client reviews it within a stated window, and payment follows acceptance or the window's end, whichever comes first. This stops the review period from becoming a payment period, a trick that has stretched many freelancer invoices from weeks into quarters. The acceptance window should be short and stated in days, so silence after delivery cannot quietly become a reason to delay. Two dates, two events, one clear line between them.

Then add the late fee. A charge of 1 to 1.5 percent per month on overdue balances is the range commonly cited in freelancer and small-business circles, and it appears in the generator as an editable percentage with 1.5 as the default. The point is less the money than the incentive: a late fee named in advance turns collections from a negotiation into arithmetic. Enforcement details are governed by local law, which a later guide in this series covers in depth.

CHAPTER 04Revision Rounds: Deciding in Advance What 'Done' Means

A revision round is a batch of changes reviewed together, not a license to send one tweak every morning for a month. Strong agreements state how many rounds the fee includes, usually one or two, what counts as a round, and what happens when the count runs out: further rounds bill at an hourly rate written into the contract. The generator ships with editable example language so you can set the number that fits your craft and your pricing.

Clients benefit too. A cap signals that you take feedback seriously and organize it, rather than reacting to whatever arrives whenever it arrives. It also gives the client's team a reason to gather comments internally before sending them, which is a gift to everyone's calendar. Clear rounds turn endless edits into a finite, scheduled phase with a finish line both sides can see.

CHAPTER 05Ownership, Confidentiality and Contractor Status

The intellectual property section answers one question: who owns the deliverables. The common answer is the client, upon full payment, which links the transfer of ownership to the arrival of your money and is the generator's first IP option. The second option flips it: you retain ownership and grant the client a license to use the work, which suits studios that reuse frameworks or sell template-based products. Either choice is legitimate; what is not legitimate is silence, because ownership questions outlive projects.

Confidentiality comes next, and light mutual language is enough for most engagements: each side keeps the other's nonpublic business information private during and after the project. You protect their customer lists and roadmaps; they protect your pricing and client roster. For heavier secrets, a dedicated agreement is the better tool, and the free NDA template generator builds one in minutes.

Finish the cluster with independent-contractor status: you control how and when the work gets done, you bring your own tools, and you may serve other clients. This section keeps the working relationship described accurately for both sides' bookkeeping. The sentence exists so that neither side drifts into describing the arrangement as employment when the reality is a project-based engagement, which matters for how each party reports the money. Keep the wording simple, keep it factual, and keep it consistent with how you actually work.

CHAPTER 06Exits and Safety Nets: Termination, Kill Fee, Liability Cap, Governing Law

Every agreement needs a documented way out. Termination for cause covers serious breaches, like nonpayment or abandoned cooperation; termination for convenience lets either side end the relationship without a scandal, given written notice, with fourteen days as a workable default. Pair the notice with a kill fee written pro-rata: the client pays for the portion of services completed through termination, so capacity you already scheduled and delivered is compensated even if the project dies mid-flight.

The liability cap is the clause nobody reads until the worst week of the year. Capping each side's total liability at the fees paid under the agreement means a failed project costs what it cost, not the client's whole quarter. Clients accept caps because the protection runs both ways. The generator includes cap language at fees paid as an editable example, ready to adjust for riskier work.

Finally, name the governing state and leave space for signatures. The governing-state line tells everyone which state's contract principles interpret the document, which matters because rules vary by jurisdiction; the signature block records who agreed and when. One honest note belongs here too: this guide is general information, not legal advice, so have an attorney review any contract that matters before signing. When you are ready to draft, the free service agreement template generator turns these ten sections into a complete plain-text document.

🔑 Key takeaways

• A simple service agreement needs ten parts: parties and dates, services description, client responsibilities, payment amount and schedule, late fee, revision rounds, IP terms, confidentiality, termination with kill fee, and liability cap with governing law.
• Describe services as deliverables with scope limits and exclusions; one sentence of 'not included' prevents a month of free work.
• Tie intellectual property transfer to full payment so ownership and cash arrive together.
• A fourteen-day termination notice with a pro-rata kill fee lets either side exit without abandoning work already done.
• A liability cap at fees paid keeps a bad project from becoming a business-ending event for either side.

❓ Frequently asked questions

📚 More in the Toolfyra blog · or browse all free online tools.