What is a service agreement?
A service agreement records what one party will do for another and the terms on which that work will be paid for and managed. It can be used between businesses, a business and a freelancer, an agency and a client, a consultant and a customer, or many other service relationships.
It is useful because it turns expectations into something both sides can check: what success looks like, who supplies what, and what happens if the project changes. Calling a document a service agreement does not by itself determine whether a relationship is employment, contracting, or something else; that can depend on the actual arrangement and applicable law.
What should a service agreement include?
The following parts do different jobs. A short agreement may combine some of them, but each should be clear enough to answer a practical question.
Parties
Identify who is signing and in what legal capacity.
Scope of services
State the work the provider is expected to perform.
Deliverables and timeline
Define outputs, milestones, deadlines and dependencies.
Payment
Cover fees, invoices, expenses, taxes where relevant, and late payment.
Changes
Set a process for extra work, revisions and changed deadlines.
IP and confidentiality
Address ownership, pre-existing materials and sensitive information.
Liability and disputes
Allocate risk and explain how disputes are expected to be handled.
Termination
Explain how the work can end and what follows.
Scope of work: the section that prevents most disputes
A vague scope lets each side imagine a different job. A useful scope names tasks, deliverables, quantities, formats, exclusions, client dependencies, deadlines and acceptance criteria. It also helps control scope creep: work that appears during a project but was not part of the original deal.
Vague
“Provider will provide marketing services.”
More specific
“Provider will deliver four written articles per month, each 800–1,000 words, on topics approved by the client.”
- Tasks and outputs, not only a broad service label
- Quantity, format and quality or acceptance criteria
- What is expressly outside the agreed price
- Information, access and approvals the client must provide
- Dependencies that may move a delivery date
The second example is fictional. More detail is not always better, but the agreement should leave as little room as possible for avoidable assumptions.
Deliverables and acceptance
Doing work, handing it over, and having it accepted are related but different milestones. The agreement can make each one visible.
Review period
How long does the client have to review a deliverable?
Revision rounds
How many revisions are included, and what counts as a new request?
Acceptance criteria
What objective standard or specification is used to decide whether work is complete?
No response or rejection
Does the contract describe deemed acceptance, feedback deadlines, or the process for resolving a rejected deliverable?
Payment terms
Price is only one part of payment. A practical agreement often uses a fixed fee, hourly or daily rate, milestone payments, a monthly retainer, or a deposit followed by a final payment.
Common structures
- Fixed fee for a defined project
- Hourly or daily rate with reporting expectations
- Milestone payments tied to stated stages
- Monthly retainer for ongoing availability or work
- Deposit plus final payment
What to clarify
- When invoices are issued and when payment is due
- Which expenses need approval and how they are documented
- How disputed invoices are handled
- Late payment provisions, taxes and deposits
- Whether refunds apply in a stated circumstance
Scope changes and additional work
A change process protects both sides when a client asks for work outside the original scope. It should establish the impact before the provider starts the extra work.
Change request
Impact on price and time
Written approval
Additional work begins
Informal messages can be useful evidence, but relying on an unclear thread of messages can leave price, timing and approval open to dispute. A contract can specify which written approval is enough.
Intellectual property: who owns the work?
Paying for services does not necessarily answer every ownership question. Read the IP wording alongside the description of the deliverables and any licences. The contractual effect and legal rules can vary by jurisdiction.
- Does ownership of final deliverables transfer, and when?
- Is transfer conditional on full payment?
- Does the provider keep reusable tools, templates or know-how?
- Are software, library components or third-party assets included?
- Does the client receive ownership, a licence, or both?
Client responsibilities
A service agreement is not only a list of provider obligations. The client may need to supply information, materials, access, approvals and feedback, and to pay invoices on time.
- Provide accurate information and needed access
- Give feedback and approvals by stated dates
- Supply client-owned content or materials
- Meet its own dependencies and payment obligations
- Understand how a delay on its side affects the timeline when the agreement says so
Confidentiality and data
Check what information is confidential, the permitted uses, who may receive it (such as employees or subcontractors), how long duties last, and whether information must be returned or deleted. Data protection obligations may also need separate treatment depending on the data and jurisdictions involved.
- Definition and exclusions
- Permitted disclosure and subcontractors
- Duration and return or deletion
- Handling of client or personal data
For a closer look at this type of wording, see the confidentiality clause explainer.
Liability and indemnity
These provisions decide how the contract allocates certain financial risks. They deserve a slow read, especially where a project could affect customers, data, revenue or third parties.
Limitation of liability
A contractual attempt to limit the amount or types of loss one party may be responsible for.
Indemnity
An obligation to cover specified losses, claims or costs in stated situations.
- Whether limits apply equally to both parties
- The amount of a liability cap and exclusions from it
- Broad indemnities and third-party claims
- Whether indirect or consequential losses are addressed
Whether a limitation or indemnity is enforceable depends on the wording, circumstances and applicable law.
How the agreement can end
Look for the contract term, renewal mechanics, termination for convenience, termination for breach, notice periods and any cure period. The end of the relationship can also trigger practical questions about outstanding invoices, final deliverables, return of materials, confidentiality, IP and transition work.
- Fixed term and renewal
- Termination for convenience
- Termination for breach and cure periods
- Notice method and timing
- What happens to work and payments already in progress
Our termination clause explainer covers these exit provisions in more detail.
Service agreement red flags
Vague scope or unlimited revisions
It can turn a fixed project into an open-ended obligation.
No process for additional work
Price and deadlines may become difficult to prove.
Unclear ownership
The parties may disagree about rights in final work, tools or third-party materials.
One-sided risk allocation
Unlimited liability or a very broad indemnity may expose one side to unexpected claims.
Difficult exit
Automatic renewal or unilateral termination rights can make the relationship harder to manage.
No payment schedule
The agreement may not say when cash is due or what happens when an invoice is disputed.
Client vs service provider: what each side should check
If you are the client
- Clear deliverables and realistic deadlines
- Quality and acceptance process
- Ownership and confidentiality
- Remedies if work is not performed
If you are the service provider
- Defined scope and revision limits
- Payment timing and client dependencies
- Pricing and approval for additional work
- Liability limits, non-payment and termination rights
Example service agreement scenario
A small business hires a design studio to redesign its website for a fixed fee. The agreement defines deliverables, two revision rounds, milestone payments, approval deadlines, separately priced additional work, and transfer of final deliverables after payment.
The client requests an extra feature
The studio identifies the extra time and price, gets written approval, then adds the work to the project.
The client provides content late
If the agreement ties the schedule to timely client materials, the delivery date can be adjusted under that process.
The project ends before completion
The termination terms should address completed work, amounts due, return of materials and what rights each side has in unfinished work.
Before signing: service agreement checklist
- Are services and deliverables clearly defined?
- Are deadlines realistic, including client dependencies?
- How many revisions are included?
- How is extra work approved and priced?
- When are invoices due, and what happens if payment is late?
- Who owns the final work and what rights remain with the provider?
- Are confidentiality obligations clear?
- Is liability capped, and are indemnities unusually broad?
- Can both parties terminate, with what notice?
- What happens to unfinished work after termination?
Example clause breakdown
Fictional educational example, not a template or a recommended clause for every agreement.
Defined work
The schedule, rather than a broad label, sets the baseline for the price.
Change control
Extra work needs an agreed price and timing before it starts.
Payment stages
The parties can see when each part of the fee becomes due.
Exit route
It distinguishes breach from a no-fault termination and addresses payment for work completed.
Frequently asked questions
What is a service agreement?+
It is a contract that records the services, payment, responsibilities and other rules for a relationship between a provider and a client.
What should a service agreement include?+
At minimum, look for clear parties, scope, deliverables, timing, payment, change control, ownership, confidentiality, liability and termination provisions.
Is a service agreement the same as a contract?+
A service agreement is a type of contract. Its label is less important than the terms and the relationship it actually describes.
How is it different from an employment contract?+
A service agreement commonly describes services supplied to a client, but classification depends on the actual arrangement and applicable law—not simply the document title.
Who owns work created under a service agreement?+
The agreement should say. Ownership of final deliverables, reusable materials and third-party assets can be treated differently, and applicable legal rules may matter.
Can a service agreement end early?+
It depends on its termination terms. Check the stated notice, breach and cure process, fees, and consequences for work already completed.
What happens when work falls outside the agreed scope?+
A well-defined change process can require the parties to agree the new price and timeline before additional work begins.
Does a service agreement need to be in writing?+
Formal requirements vary by agreement type and jurisdiction. Written terms generally provide clearer evidence of what the parties agreed.
Review your service agreement
Lawyerless can help surface the scope, payment terms, termination provisions, liability and clauses worth reviewing. It offers a plain-language first pass, not legal advice or a decision on enforceability.
Analyze my agreement